You can subscribe to this list here.
2002 |
Jan
(2) |
Feb
(157) |
Mar
(111) |
Apr
(61) |
May
(68) |
Jun
(45) |
Jul
(101) |
Aug
(132) |
Sep
(148) |
Oct
(227) |
Nov
(141) |
Dec
(285) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(518) |
Feb
(462) |
Mar
(390) |
Apr
(488) |
May
(321) |
Jun
(336) |
Jul
(268) |
Aug
(374) |
Sep
(211) |
Oct
(246) |
Nov
(239) |
Dec
(173) |
2004 |
Jan
(110) |
Feb
(131) |
Mar
(85) |
Apr
(120) |
May
(82) |
Jun
(101) |
Jul
(54) |
Aug
(65) |
Sep
(94) |
Oct
(51) |
Nov
(56) |
Dec
(168) |
2005 |
Jan
(146) |
Feb
(98) |
Mar
(75) |
Apr
(118) |
May
(85) |
Jun
(75) |
Jul
(44) |
Aug
(94) |
Sep
(70) |
Oct
(84) |
Nov
(115) |
Dec
(52) |
2006 |
Jan
(113) |
Feb
(83) |
Mar
(217) |
Apr
(158) |
May
(219) |
Jun
(218) |
Jul
(189) |
Aug
(39) |
Sep
(3) |
Oct
(7) |
Nov
(4) |
Dec
(2) |
2007 |
Jan
|
Feb
(2) |
Mar
(7) |
Apr
(3) |
May
(3) |
Jun
(8) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(4) |
Nov
(7) |
Dec
|
2008 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
(4) |
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
2009 |
Jan
(6) |
Feb
|
Mar
(1) |
Apr
(2) |
May
(1) |
Jun
(1) |
Jul
(10) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(3) |
2010 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2012 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Christoph S. <ch...@sc...> - 2003-01-02 11:09:28
|
hey all and happy new year Gavin King wrote: > Well, I imported the Hibernate2 sourcetree last night. Its in > its own module which means that for the next couple of months > we need to be *very* careful about handling patches. Bugfixes > and minor improvements must be applied against *both* trees. > (New features need only go into the Hibernate2 module.) As > promised, the following changes were made: > > * packages are now net.sf.hibernate.* > * project structure is changed; all java is now in src dir > * code and tests relating to toplevel collections and subcollections > was removed > > I have created a new hibernate-mapping-2.0.dtd, since we no > longer need the <collection>, <subcollection>, <generated-key> > elements and since collections may no longer appear beneath > the root element. > > In the new DTD, I have also renamed the 'readonly' attribute to > 'inverse', since its name was causing all kinds of confusion for new > (and not-so-new) users. > > Please vote on the following proposals: > > * Rename the 'role' attribute to 'name' in all collection > elements in the new DTD, for consistency with <many-to-one>, <id> > and <property> elements. The role attribute no longer > has any extra semantics beyond being a simple property > name. > > I am +1 > +1 > > * Change the default for unsaved-value to "null" in the new DTD. The > current default is surprising to new users. > > I am +1 > +1 > > * Change the default for default-cascade to "save-update" > in the new DTD. > > I am undecided ... interested to hear the views of others. > +0 > > * Remove the exception that occurs if you save an object > that is already associated with the session. This > makes save() consistent with saveOrUpdate(). > > I am probably a +1 on this > +1 > > * Remove the exception that occurs if you delete an object > that is already deleted in that session. > I am undecided. The current behaviour forces people to > think about who "owns" an object, who is responsible for > deleting it. However, it *can* be a pain in the ass. > In particular it means that: > > session.delete("from o in class java.lang.Object"); > +1 > > > |
From: Konstantin P. <kpr...@ya...> - 2003-01-02 09:06:36
|
> Please vote on the following proposals: > > * Rename the 'role' attribute to 'name' in all > collection > elements in the new DTD, for consistency with > <many-to-one>, > <id> and <property> elements. The role attribute > no longer > has any extra semantics beyond being a simple > property > name. > > I am +1 +1 > * Change the default for unsaved-value to "null" in > the new > DTD. The current default is surprising to new > users. > > I am +1 +1000 > * Change the default for default-cascade to > "save-update" > in the new DTD. > > I am undecided ... interested to hear the views of > others. From my point of view, some 50% I need save-update, sometimes none... regards, ===== Konstantin Priblouda ( ko5tik ) Freelance Software developer < http://www.pribluda.de > < play java games -> http://www.yook.de > < render charts online -> http://www.pribluda.de/povray/ > __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com |
From: Christian B. <chr...@bl...> - 2003-01-02 08:39:11
|
On 02 Jan (10:20), Gavin King wrote: > In the new DTD, I have also renamed the 'readonly' attribute > to 'inverse', since its name was causing all kinds of confusion > for new (and not-so-new) users. +1 :) > * Rename the 'role' attribute to 'name' in all collection > elements in the new DTD, for consistency with <many-to-one>, > <id> and <property> elements. The role attribute no longer > has any extra semantics beyond being a simple property > name. ++ > * Change the default for unsaved-value to "null" in the new > DTD. The current default is surprising to new users. ++ > * Change the default for default-cascade to "save-update" > in the new DTD. > > I am undecided ... interested to hear the views of others. This would be too much like "persistence by reachability" by default. This should be optional. -- Christian Bauer tu...@in... |
From: max <ma...@ac...> - 2003-01-02 07:31:43
|
Gavin King wrote: >Max, it would happen whenever you have a column name that approaches >the limit for the database. Hibernate needs to add an _0, etc at >the end when rendering aiases. > I know, would just be easier if he got a clean example :) But Ok - I've fought with these kind of troubles before and at that time we just limited our selfes to use shorter column names :) (the easy solution - and is "ok" as long as we are using the column names and not the propertynames in the SQL generated by HQL) Another one is to rewrite the code that produces those aliases (and as I remember - the logic are well-defined but unfortunatly not in a single method). That alias generation should of course use the Dialect class which would have an getMaxColumnNameLength and getMaxTableNameLength. If the aliases generated exceeds that amount "do something" :) Maybe we should just postfix the names with 0_ instead of prefixing them with _0 (and then chop them of with the dialects max lengths..) - that would make them unique ....and avoid name colisions (as long as the max lenght is not near 3-4 chars ....) Just some thoughts.... /max > > |
From: Gavin K. <Gav...@ex...> - 2003-01-02 07:18:03
|
Max, it would happen whenever you have a column name that approaches the limit for the database. Hibernate needs to add an _0, etc at the end when rendering aiases. > -----Original Message----- > From: max [mailto:ma...@ac...]=20 > Sent: Thursday, 2 January 2003 6:11 PM > To: Hibernate Mailing List > Subject: Re: [Hibernate] Length of Hibernate-generated aliases in SQL >=20 >=20 > Could you give an hbm.xml and query example that gives that=20 > error ? (it=20 > would be nice to have some test scenario :) > (especially, since it would be nice to know what one could do=20 > to avoid=20 > such a thing....- it would also be a problem on db2 since it also has=20 > some "weird" low limitations) >=20 > /max >=20 > >Yick. The biggest design problem with Hibernate at present=20 > is the fact=20 > >that we have no single class responsible for rendering SQL.=20 > (As I have=20 > >mentioned before, Hibernate models SQL statements using=20 > >StringBuffer...) So little things like this that should be=20 > *very* easy=20 > >turn out to be way more tricky than you expect. However there are a=20 > >couple of methods that are responsible for dealing with SQL quoted=20 > >identifiers so you may be able to hook in there. > > > >We *do* need to fix this problem of StringBuffer being used=20 > everywhere. > > > > =20 > > > >>-----Original Message----- > >>From: Mark Woon [mailto:mor...@SM...] > >>Sent: Wednesday, 1 January 2003 10:33 AM > >>To: Hibernate Mailing List > >>Subject: [Hibernate] Length of Hibernate-generated aliases in SQL > >> > >> > >> > >>Does Hibernate do any checking on the length of the aliases > >>it generates=20 > >>when it creates it's SQL queries? I'm getting "identifier is=20 > >>too long"=20 > >>errors against Oracle 9.2 at the moment because Hibernate=20 > >>tacks on some=20 > >>extra text to some column names. > >> > >>If not, would it be terribly difficult to add this > >>functionality? Which=20 > >>classes should I be looking at to figure this out? > >> > >>Thanks, > >>-Mark > >> > >> > >> > >>------------------------------------------------------- > >>This sf.net email is sponsored by:ThinkGeek > >>Welcome to geek heaven. > >>http://thinkgeek.com/sf > >>_______________________________________________ > >>hibernate-devel mailing list hib...@li... > >>https://lists.sourceforge.net/lists/listinfo/hibernate-devel > >> > >> =20 > >> >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf=20 > _______________________________________________ > hibernate-devel mailing list hib...@li... > https://lists.sourceforge.net/lists/listinfo/hibernate-devel >=20 ********** CAUTION - Disclaimer ********** This message may contain privileged and confidential information. If you are not the intended recipient of this message (or responsible for delivery of the message to such person) you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error, you should destroy it and kindly notify the sender by reply e-mail. Please advise immediately if you or your employer do not consent to Internet e-mail for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of Expert Information Services Pty Ltd ("The Company") shall be understood as neither given nor endorsed by it. The Company advises that this e-mail and any attached files should be scanned to detect viruses. The Company accepts no liability for loss or damage (whether caused by negligence or not) resulting from the use of any attached files. **EIS******** End of Disclaimer ********** |
From: max <ma...@ac...> - 2003-01-02 07:11:06
|
Could you give an hbm.xml and query example that gives that error ? (it would be nice to have some test scenario :) (especially, since it would be nice to know what one could do to avoid such a thing....- it would also be a problem on db2 since it also has some "weird" low limitations) /max >Yick. The biggest design problem with Hibernate at present is >the fact that we have no single class responsible for rendering >SQL. (As I have mentioned before, Hibernate models SQL >statements using StringBuffer...) So little things like this >that should be *very* easy turn out to be way more tricky >than you expect. However there are a couple of methods that >are responsible for dealing with SQL quoted identifiers so >you may be able to hook in there. > >We *do* need to fix this problem of StringBuffer being used >everywhere. > > > >>-----Original Message----- >>From: Mark Woon [mailto:mor...@SM...] >>Sent: Wednesday, 1 January 2003 10:33 AM >>To: Hibernate Mailing List >>Subject: [Hibernate] Length of Hibernate-generated aliases in SQL >> >> >> >>Does Hibernate do any checking on the length of the aliases >>it generates >>when it creates it's SQL queries? I'm getting "identifier is >>too long" >>errors against Oracle 9.2 at the moment because Hibernate >>tacks on some >>extra text to some column names. >> >>If not, would it be terribly difficult to add this >>functionality? Which >>classes should I be looking at to figure this out? >> >>Thanks, >>-Mark >> >> >> >>------------------------------------------------------- >>This sf.net email is sponsored by:ThinkGeek >>Welcome to geek heaven. >>http://thinkgeek.com/sf >>_______________________________________________ >>hibernate-devel mailing list hib...@li... >>https://lists.sourceforge.net/lists/listinfo/hibernate-devel >> >> >> |
From: Gavin K. <Gav...@ex...> - 2003-01-01 23:44:42
|
Yick. The biggest design problem with Hibernate at present is the fact that we have no single class responsible for rendering SQL. (As I have mentioned before, Hibernate models SQL=20 statements using StringBuffer...) So little things like this=20 that should be *very* easy turn out to be way more tricky than you expect. However there are a couple of methods that are responsible for dealing with SQL quoted identifiers so you may be able to hook in there. We *do* need to fix this problem of StringBuffer being used everywhere. > -----Original Message----- > From: Mark Woon [mailto:mor...@SM...]=20 > Sent: Wednesday, 1 January 2003 10:33 AM > To: Hibernate Mailing List > Subject: [Hibernate] Length of Hibernate-generated aliases in SQL >=20 >=20 >=20 > Does Hibernate do any checking on the length of the aliases=20 > it generates=20 > when it creates it's SQL queries? I'm getting "identifier is=20 > too long"=20 > errors against Oracle 9.2 at the moment because Hibernate=20 > tacks on some=20 > extra text to some column names. >=20 > If not, would it be terribly difficult to add this=20 > functionality? Which=20 > classes should I be looking at to figure this out? >=20 > Thanks, > -Mark >=20 >=20 >=20 > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf=20 > _______________________________________________ > hibernate-devel mailing list hib...@li... > https://lists.sourceforge.net/lists/listinfo/hibernate-devel >=20 ********** CAUTION - Disclaimer ********** This message may contain privileged and confidential information. If you are not the intended recipient of this message (or responsible for delivery of the message to such person) you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error, you should destroy it and kindly notify the sender by reply e-mail. Please advise immediately if you or your employer do not consent to Internet e-mail for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of Expert Information Services Pty Ltd ("The Company") shall be understood as neither given nor endorsed by it. The Company advises that this e-mail and any attached files should be scanned to detect viruses. The Company accepts no liability for loss or damage (whether caused by negligence or not) resulting from the use of any attached files. **EIS******** End of Disclaimer ********** |
From: Gavin K. <Gav...@ex...> - 2003-01-01 23:20:57
|
Well, I imported the Hibernate2 sourcetree last night. Its in its own module which means that for the next couple of months we need to be *very* careful about handling patches. Bugfixes and minor improvements must be applied against *both* trees. (New features need only go into the Hibernate2 module.) As promised, the following changes were made: * packages are now net.sf.hibernate.* * project structure is changed; all java is now in src dir * code and tests relating to toplevel collections and=20 subcollections was removed I have created a new hibernate-mapping-2.0.dtd, since we no longer need the <collection>, <subcollection>, <generated-key> elements and since collections may no longer appear beneath the root element. In the new DTD, I have also renamed the 'readonly' attribute=20 to 'inverse', since its name was causing all kinds of confusion=20 for new (and not-so-new) users. Please vote on the following proposals: * Rename the 'role' attribute to 'name' in all collection elements in the new DTD, for consistency with <many-to-one>,=20 <id> and <property> elements. The role attribute no longer has any extra semantics beyond being a simple property name. I am +1 * Change the default for unsaved-value to "null" in the new=20 DTD. The current default is surprising to new users. I am +1 * Change the default for default-cascade to "save-update" in the new DTD. I am undecided ... interested to hear the views of others. * Remove the exception that occurs if you save an object that is already associated with the session. This makes save() consistent with saveOrUpdate(). I am probably a +1 on this * Remove the exception that occurs if you delete an object that is already deleted in that session.=20 I am undecided. The current behaviour forces people to think about who "owns" an object, who is responsible for deleting it. However, it *can* be a pain in the ass. In particular it means that: session.delete("from o in class java.lang.Object"); never has any possibility of success if you use cascade delete anywhere. None of the above proposals would break existing code that uses the old mapping DTDs. The actual changes to default values can be made just in the DTD. Gavin. ********** CAUTION - Disclaimer ********** This message may contain privileged and confidential information. If you are not the intended recipient of this message (or responsible for delivery of the message to such person) you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error, you should destroy it and kindly notify the sender by reply e-mail. Please advise immediately if you or your employer do not consent to Internet e-mail for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of Expert Information Services Pty Ltd ("The Company") shall be understood as neither given nor endorsed by it. The Company advises that this e-mail and any attached files should be scanned to detect viruses. The Company accepts no liability for loss or damage (whether caused by negligence or not) resulting from the use of any attached files. **EIS******** End of Disclaimer ********** |
From: Gavin K. <Gav...@ex...> - 2003-01-01 22:55:47
|
Ahhhh the > 4000 characters bit is where you start to need the "for update" clause. We were wondering about that earlier. I think you *could* make it work like this: s =3D sf.openSession(); tx =3D s.beginTransaction(); foo =3D new Foo(); foo.setClob( Hibernate.createClob("") ); s.save(foo); tx.commit(); s.close(); s =3D sf.openSession(); tx =3D s.beginTransaction(); foo =3D (Foo) s.load( Foo.class, foo.getId(), LockMode.UPGRADE ); oracle.sql.CLOB clob =3D (oracle.sql.CLOB) foo.getClob(); java.io.Writer pw =3D clob.getCharacterOutputStream(); pw.write(content); pw.close(); tx.commit(); s.close(); Would you try that for me, please? Gavin > -----Original Message----- > From: Ugo Cei [mailto:u....@cb...]=20 > Sent: Wednesday, 1 January 2003 3:22 AM > To: hib...@li... > Subject: Re: [Hibernate] Using CLOBs >=20 >=20 > Gavin King wrote: > > The name of the type is "clob", and the expected property type is=20 > > java.sql.Clob. Note that there are restrictions upon what=20 > you can do=20 > > with Clobs (they can't be used outside of transaction, for example). > >=20 > > You should also take notice of Hibernate.createClob(). >=20 > Thanks. Everything works fine ... at least in theory ... >=20 > If you use Oracle 8i and try to store more than 4000=20 > characters, this is=20 > what you get: >=20 > java.sql.SQLException: Data size bigger than max size for=20 > this type: 7894 > at=20 > oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134) > at=20 > oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179) > at oracle.jdbc.ttc7.TTCItem.setArrayData(TTCItem.java:147) > at=20 > oracle.jdbc.dbaccess.DBDataSetImpl.setBytesBindItem(DBDataSetI > mpl.java:2461) > at=20 > oracle.jdbc.driver.OraclePreparedStatement.setItem(OraclePrepa > redStatement.java:1155) > at=20 > oracle.jdbc.driver.OraclePreparedStatement.setString(OraclePre > paredStatement.java:1572) > at=20 > org.apache.commons.dbcp.DelegatingPreparedStatement.setString( DelegatingPreparedStatement.java:217) > at=20 > org.apache.commons.dbcp.DelegatingPreparedStatement.setString( DelegatingPreparedStatement.java:217) > at cirrus.hibernate.type.ClobType.set(ClobType.java:14) >=20 > Actually, having already been through the nightmare that CLOB=20 > support in=20 > Oracle is, I expected nothing more and nothing less. >=20 > AFAIK there is just one way to store more than 4000 characters in an=20 > Oracle CLOB via JDBC: >=20 > - start a transaction > - insert into tablename(id, clob_field) values('X', empty_clob()) > - select clob_field from tablename where id =3D 'X' for update=20 > of clob_field > - ResultSet rs =3D (oracle.jdbc.driver.OracleResultSet)=20 > ps.executeQuery(); > if (rs.next()) { > oracle.sql.CLOB clob =3D rs.getCLOB(1); > java.io.Writer pw =3D clob.getCharacterOutputStream(); > pw.write(content); > pw.close(); > } > - commit >=20 > If this isn't a PITA, I don't know what is :-( >=20 > Do you think it's going to be difficult to implement this=20 > rigamarole in=20 > Hibernate? >=20 > Ugo >=20 > --=20 > Ugo Cei - http://www.beblogging.com/blog/ >=20 >=20 >=20 > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf=20 > _______________________________________________ > hibernate-devel mailing list hib...@li... > https://lists.sourceforge.net/lists/listinfo/hibernate-devel >=20 ********** CAUTION - Disclaimer ********** This message may contain privileged and confidential information. If you are not the intended recipient of this message (or responsible for delivery of the message to such person) you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error, you should destroy it and kindly notify the sender by reply e-mail. Please advise immediately if you or your employer do not consent to Internet e-mail for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of Expert Information Services Pty Ltd ("The Company") shall be understood as neither given nor endorsed by it. The Company advises that this e-mail and any attached files should be scanned to detect viruses. The Company accepts no liability for loss or damage (whether caused by negligence or not) resulting from the use of any attached files. **EIS******** End of Disclaimer ********** |
From: Gavin K. <Gav...@ex...> - 2003-01-01 22:47:18
|
I agree with all this. Writing get/set pairs is not that painful. > -----Original Message----- > From: Konstantin Priblouda [mailto:kpr...@ya...]=20 > Sent: Wednesday, 1 January 2003 12:36 AM > To: Max Rydahl Andersen > Cc: hibernate-devel > Subject: Re: [Hibernate] Hibernate XDoclet Task >=20 >=20 >=20 > > Just corius, why does generating add, set, get for > > the hibernate beans makes > > you loose any advantage ? (Where is there created a > > prallel class > > hierarchy?) >=20 > XDoclet works like this: > - grab source class tagged with tags > - generate something out of it.=20 >=20 > So, say you have base class without getters etc, > but with properties. You can {theoretically,=20 > since no tags or templates exists for this puprose } > tag properties appropriately. Then you can generate > source for real one class with getters / setters > ( derived from base one ) -> you got 2 classes & > you have to work with new one.=20 >=20 > What I like inhibernate is the ability just > write my persistent classes , and work wit them.=20 > Not like entity beans with all those interfaces > & utility stuff. Though we might be generation some > utility stuff by xdoclet - like remote facades & crud > adapetrs for going to hibernate through session bean. >=20 > It simply does not pays to use xdoclet for generation > of getters/setters. Every decent IDE will yllow > you to do this.=20 >=20 > But when it comes to generation of shitload of XML > descriptors - xdoclet comes to full strength... >=20 > regards, >=20 > =3D=3D=3D=3D=3D > Konstantin Priblouda ( ko5tik ) Freelance Software developer > < http://www.pribluda.de > < play java games ->=20 http://www.yook.de > < render charts online -> http://www.pribluda.de/povray/ > __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ hibernate-devel mailing list hib...@li... https://lists.sourceforge.net/lists/listinfo/hibernate-devel ********** CAUTION - Disclaimer ********** This message may contain privileged and confidential information. If you are not the intended recipient of this message (or responsible for delivery of the message to such person) you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error, you should destroy it and kindly notify the sender by reply e-mail. Please advise immediately if you or your employer do not consent to Internet e-mail for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of Expert Information Services Pty Ltd ("The Company") shall be understood as neither given nor endorsed by it. The Company advises that this e-mail and any attached files should be scanned to detect viruses. The Company accepts no liability for loss or damage (whether caused by negligence or not) resulting from the use of any attached files. **EIS******** End of Disclaimer ********** |
From: Gavin K. <Gav...@ex...> - 2003-01-01 22:45:27
|
> Its it the actual field, the getX() or the setX() that should=20 > be modified ? (The same actually goes for the "description" tag...) I meant the get/set pair. Fields should always be private. perhaps it makes more sense to have getter-scope and setter-scope. > How about having "description-get", "description-set" and=20 > just "description" for the actual field ? (or should it be=20 > "description-field" I suppose....but isn't that a bit much?? I had intended that the description would go onto the getter method. =20 > And then similarily "scope-get", "scope-set" and=20 > "scope"/"scope-field" for the actual field ? >=20 > Maybe "scope" and "description" should just apply for both=20 > set, get and field if nothing else is specified ? I'd rather not grow a whole menagerie of these metas.... ********** CAUTION - Disclaimer ********** This message may contain privileged and confidential information. If you are not the intended recipient of this message (or responsible for delivery of the message to such person) you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error, you should destroy it and kindly notify the sender by reply e-mail. Please advise immediately if you or your employer do not consent to Internet e-mail for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of Expert Information Services Pty Ltd ("The Company") shall be understood as neither given nor endorsed by it. The Company advises that this e-mail and any attached files should be scanned to detect viruses. The Company accepts no liability for loss or damage (whether caused by negligence or not) resulting from the use of any attached files. **EIS******** End of Disclaimer ********** |
From: Gavin K. <Gav...@ex...> - 2003-01-01 22:41:45
|
Its not essential to support identity columns. If you can't seem to get it working, just ignore it for now. (And don't worry about the test suites=20 that require it.) See if you can get FooBarTest working (you might need to skip all the subquery tests..... > -----Original Message----- > From: Pietro Polsinelli [mailto:de...@op...]=20 > Sent: Tuesday, 31 December 2002 9:53 PM > To: hib...@li... > Subject: [Hibernate] ms access dialect problem >=20 >=20 > well g., >=20 > thanks for support, but I'm getting nowhere. I finally=20 > found the keyword=20 > for generating autoincrement column via JDBC for access,=20 > "counter", but still does not seem to work in this context. >=20 > public String getIdentityColumnString() { > return " counter "; > } >=20 > I tried all versions from other dialects in vain. >=20 > moreover, passing to 1.2.1, updates of schema do not work=20 > any more (it=20 > works fine in 1.2): >=20 > 11:22:09,773 DEBUG DriverManagerConnectionProvider:89 - > Created connection to:=20 > jdbc:izmado:IzmDllPath=3DK:\cvs_out\teamwork\html\WEB-INF\lib\Iz mJniAdo.dll;IzmRoyaltyFree=3D*****;Provider=3DMSDASQ> L; > Driver=3D{Microsoft Access Driver=20 > (*.mdb)};Dbq=3Dk:\cvs_out\teamwork\data\teamwork_ol.mdb,=20 > Isolation Level: 2 > com.inzoom.adojni.ComException: Object or provider is not capable of=20 > performing requested operation. in ADODB.Connection code=3D0 Type=3D1 > at com.inzoom.ado.Connection.jniOpenSchema(Native Method) > at com.inzoom.ado.Connection.openSchema(Connection.java:154) > at=20 > com.inzoom.jdbcado.DatabaseMetaData.openAdoSchema(DatabaseMeta > Data.java:124) > at=20 > com.inzoom.jdbcado.DatabaseMetaData.getFKs(DatabaseMetaData.java:1243) > at=20 > com.inzoom.jdbcado.DatabaseMetaData.getImportedKeys(DatabaseMe > taData.java:1301) > at=20 > cirrus.hibernate.tools.updater.JdbcTableInfo.initForeignKeys(J > dbcTableInfo.java:29) > at=20 > cirrus.hibernate.tools.updater.JdbcDatabaseInfo.initForeignKey > s(JdbcDatabaseInfo.java:84) > at=20 > cirrus.hibernate.tools.updater.JdbcDatabaseInfo.<init>(JdbcDat > abaseInfo.java:20) > at=20 > cirrus.hibernate.tools.SchemaUpdater.execute(SchemaUpdater.java:83) > at=20 > com.twproject.persistence.GenerateUpdateScript.main(GenerateUp > dateScript.java:25) > =09 > this (and all the rest) works fine on e.g. mysql. Maybe I am=20 > hitting on=20 > intrinsic limitations, of the driver and/or the db :-( > =09 > bye >=20 >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf=20 > _______________________________________________ > hibernate-devel mailing list hib...@li... > https://lists.sourceforge.net/lists/listinfo/hibernate-devel >=20 ********** CAUTION - Disclaimer ********** This message may contain privileged and confidential information. If you are not the intended recipient of this message (or responsible for delivery of the message to such person) you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error, you should destroy it and kindly notify the sender by reply e-mail. Please advise immediately if you or your employer do not consent to Internet e-mail for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of Expert Information Services Pty Ltd ("The Company") shall be understood as neither given nor endorsed by it. The Company advises that this e-mail and any attached files should be scanned to detect viruses. The Company accepts no liability for loss or damage (whether caused by negligence or not) resulting from the use of any attached files. **EIS******** End of Disclaimer ********** |
From: Max R. A. <ma...@eo...> - 2003-01-01 19:45:08
|
Gavin, I've just discovered your introduction of src :) I like the tools naming, they make more sense now .... Just wanna know if it is "safe" to start developing/patching on hbm2java now, or do you have more tricks up your "sleefes" :) /max |
From: Mark W. <mor...@SM...> - 2002-12-31 23:33:13
|
Does Hibernate do any checking on the length of the aliases it generates when it creates it's SQL queries? I'm getting "identifier is too long" errors against Oracle 9.2 at the moment because Hibernate tacks on some extra text to some column names. If not, would it be terribly difficult to add this functionality? Which classes should I be looking at to figure this out? Thanks, -Mark |
From: Konstantin P. <kpr...@ya...> - 2002-12-31 16:49:02
|
--- "Raible, Matt" <Mat...@ca...> wrote: > I have to rows in my "user" table and I expect to > get two rows of data back. > However, the following query returns two items in > the list, but they're the > same: > > List users = (List) ses.find("from cct_user in class > com.cable.comcast.dmc.itd.cct.persistence.User where > cct_user.userId=?", > userId, Hibernate.STRING); > > Is this because userId is the named in User.hbm.xml > as the primary key? I > tried to create a composite-id element, which is > what it is in the database, > but XDoclet doesn't seem to let me. I added two > @hibernate.id tags to two > different getters, but that just generated two > different id elements in my > xml mapping file. Matt, file issue in JIRA and assign it to me ( or it will be lost ) I will look at it. regards, ===== Konstantin Priblouda ( ko5tik ) Freelance Software developer < http://www.pribluda.de > < play java games -> http://www.yook.de > < render charts online -> http://www.pribluda.de/povray/ > __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com |
From: Raible, M. <Mat...@ca...> - 2002-12-31 16:36:44
|
I have to rows in my "user" table and I expect to get two rows of data back. However, the following query returns two items in the list, but they're the same: List users = (List) ses.find("from cct_user in class com.cable.comcast.dmc.itd.cct.persistence.User where cct_user.userId=?", userId, Hibernate.STRING); Is this because userId is the named in User.hbm.xml as the primary key? I tried to create a composite-id element, which is what it is in the database, but XDoclet doesn't seem to let me. I added two @hibernate.id tags to two different getters, but that just generated two different id elements in my xml mapping file. Thanks, Matt |
From: Ugo C. <u....@cb...> - 2002-12-31 16:21:43
|
Gavin King wrote: > The name of the type is "clob", and the expected property type > is java.sql.Clob. Note that there are restrictions upon what > you can do with Clobs (they can't be used outside of transaction, > for example). > > You should also take notice of Hibernate.createClob(). Thanks. Everything works fine ... at least in theory ... If you use Oracle 8i and try to store more than 4000 characters, this is what you get: java.sql.SQLException: Data size bigger than max size for this type: 7894 at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179) at oracle.jdbc.ttc7.TTCItem.setArrayData(TTCItem.java:147) at oracle.jdbc.dbaccess.DBDataSetImpl.setBytesBindItem(DBDataSetImpl.java:2461) at oracle.jdbc.driver.OraclePreparedStatement.setItem(OraclePreparedStatement.java:1155) at oracle.jdbc.driver.OraclePreparedStatement.setString(OraclePreparedStatement.java:1572) at org.apache.commons.dbcp.DelegatingPreparedStatement.setString(DelegatingPreparedStatement.java:217) at org.apache.commons.dbcp.DelegatingPreparedStatement.setString(DelegatingPreparedStatement.java:217) at cirrus.hibernate.type.ClobType.set(ClobType.java:14) Actually, having already been through the nightmare that CLOB support in Oracle is, I expected nothing more and nothing less. AFAIK there is just one way to store more than 4000 characters in an Oracle CLOB via JDBC: - start a transaction - insert into tablename(id, clob_field) values('X', empty_clob()) - select clob_field from tablename where id = 'X' for update of clob_field - ResultSet rs = (oracle.jdbc.driver.OracleResultSet) ps.executeQuery(); if (rs.next()) { oracle.sql.CLOB clob = rs.getCLOB(1); java.io.Writer pw = clob.getCharacterOutputStream(); pw.write(content); pw.close(); } - commit If this isn't a PITA, I don't know what is :-( Do you think it's going to be difficult to implement this rigamarole in Hibernate? Ugo -- Ugo Cei - http://www.beblogging.com/blog/ |
From: Konstantin P. <kpr...@ya...> - 2002-12-31 15:42:01
|
> I've long sought for an example where BeanInfo > classes could > be used for something usefull (and Visual Age is not > one of them)... > Do you have an example of this ? Is it some kind of > databinding you > are doing or ? Well, Say I have ejb backend with shitload of entities, and swing client for doing just CRUD ( create customer, worker, transportation means, payment modalities or whatever ) I have a lot of properties and a lot of editors panels to develop. This suks. So what I'm doing: 1. Tag my entity beans that xdoclet generates beaninfo for data objects, also specify custom editors ( and write them ) for all usefull data types I have - monetary amount, selection fo ejb entity or whatever. 2. Write generic bean editor class, which can be fed with object and beaninfo for this ( or can resolve beaninfo itself ), and does reflection to update all the fields from propertyx editors. It also produces proper property editor on request. 3. Then not so generic editor panel, which setup this beaneditor, feeds it with beaninfo, and then pulls all the property editors from there, get their swing components and rigs up interface ( only custom step for entity ) It listens on changes of bean editor, activates buttons for save/update/delete etc. > > - generate smart remote proxies for hibernated > > classes, for example something like home > interfaces of > > entities > > - generate all the stuff that makes going to > > datastore through session bean transparent... > > Is this reality now or "just thoughts" ? (I would > really like to work with > this one (and we are about to hit a point where the > codegenerator and > XDoclet module may possible overlap :) Well, this is reality for EJB stuff. Though not completely adopet by xdoclet :) ( even commiter can not do everything he likes :) ) I developed following: 1. Facade session bean for entity, which provides access to finders, but returns collections of data/value objects instead of remote interfaces. 2. Static remote facade class for this session, which isolates you from such nice tasks like jndi lookups or whatever. 3. Observable collections transparently proxying methods on session facade, which are observiong CRUD adapters. In my swing app I just hook up to those collections with my data models ( tree, combo , table ), and route entity creation/remova/update through designated CRUD adapter which signals collections that they shall reload changes. > What is that compared to e.g. > http://sourceforge.net/projects/axgen (which > our old OJB friends has support for ..) must look at it. now I'm fighting with inheriting ID properties ( look in forum :) ), and damn things are just not loaded, though found... regards, ===== Konstantin Priblouda ( ko5tik ) Freelance Software developer < http://www.pribluda.de > < play java games -> http://www.yook.de > < render charts online -> http://www.pribluda.de/povray/ > __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com |
From: Max R. A. <ma...@eo...> - 2002-12-31 14:49:27
|
> > Anyway, using xdoclet for generating getters/setters > is an overkill. Roger :) > In Hibernate context follwing parts of xdoclet would > be usefull: > - java bean module -> generate your beaninfo > for hibernated classes ( in EJB scenario it has to be > tweaked for value/data objects -> stinks ). > This way you get instantly swing/webwork support I've long sought for an example where BeanInfo classes could be used for something usefull (and Visual Age is not one of them)... Do you have an example of this ? Is it some kind of databinding you are doing or ? > - generate smart remote proxies for hibernated > classes, for example something like home interfaces of > entities > - generate all the stuff that makes going to > datastore through session bean transparent... Is this reality now or "just thoughts" ? (I would really like to work with this one (and we are about to hit a point where the codegenerator and XDoclet module may possible overlap :) > > Yes - the work with XDoclet and the maturing of the > > CodeGenerator makes > > Hibernate's surrounding tools very worth while :) > > One can either go from source to descriptor or from > > descriptor to source > > depending on which scenario you got - and via > > XDocLet, CodeGenerator (and > > possible MiddleGen) we could same some very precious > > developer time :) > > There is another tool I would like to play with: > UML2EJB ( also from xdoclet neighbourhood ) - > get you .xmi and produce xdoclet-marked ejb sources. > Matthias asked me to write templates for hibernated > classes ( also xdoclet marked ) > What is that compared to e.g. http://sourceforge.net/projects/axgen (which our old OJB friends has support for ..) > regards, > > ===== > Konstantin Priblouda ( ko5tik ) Freelance Software developer > < http://www.pribluda.de > < play java games -> http://www.yook.de > > < render charts online -> http://www.pribluda.de/povray/ > > > __________________________________________________ > Do you Yahoo!? > Yahoo! Mail Plus - Powerful. Affordable. Sign up now. > http://mailplus.yahoo.com > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > hibernate-devel mailing list > hib...@li... > https://lists.sourceforge.net/lists/listinfo/hibernate-devel > |
From: Konstantin P. <kpr...@ya...> - 2002-12-31 14:25:33
|
> Of course - I momentarily forgot that XDoclet > augments the > actually used class... sorry .) (the reason it put > me of is that > you said parallel hierachies, as if the two classes > was not related - they > are, the one is Base and the other is Concrete, that > is not parallel - just > 2 times the classes you probably need .) Anyway, using xdoclet for generating getters/setters is an overkill. In Hibernate context follwing parts of xdoclet would be usefull: - java bean module -> generate your beaninfo for hibernated classes ( in EJB scenario it has to be tweaked for value/data objects -> stinks ). This way you get instantly swing/webwork support - generate smart remote proxies for hibernated classes, for example something like home interfaces of entities - generate all the stuff that makes going to datastore through session bean transparent... > Yes - the work with XDoclet and the maturing of the > CodeGenerator makes > Hibernate's surrounding tools very worth while :) > One can either go from source to descriptor or from > descriptor to source > depending on which scenario you got - and via > XDocLet, CodeGenerator (and > possible MiddleGen) we could same some very precious > developer time :) There is another tool I would like to play with: UML2EJB ( also from xdoclet neighbourhood ) - get you .xmi and produce xdoclet-marked ejb sources. Matthias asked me to write templates for hibernated classes ( also xdoclet marked ) regards, ===== Konstantin Priblouda ( ko5tik ) Freelance Software developer < http://www.pribluda.de > < play java games -> http://www.yook.de > < render charts online -> http://www.pribluda.de/povray/ > __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com |
From: Konstantin P. <kpr...@ya...> - 2002-12-31 13:35:57
|
> Just corius, why does generating add, set, get for > the hibernate beans makes > you loose any advantage ? (Where is there created a > prallel class > hierarchy?) XDoclet works like this: - grab source class tagged with tags - generate something out of it. So, say you have base class without getters etc, but with properties. You can {theoretically, since no tags or templates exists for this puprose } tag properties appropriately. Then you can generate source for real one class with getters / setters ( derived from base one ) -> you got 2 classes & you have to work with new one. What I like inhibernate is the ability just write my persistent classes , and work wit them. Not like entity beans with all those interfaces & utility stuff. Though we might be generation some utility stuff by xdoclet - like remote facades & crud adapetrs for going to hibernate through session bean. It simply does not pays to use xdoclet for generation of getters/setters. Every decent IDE will yllow you to do this. But when it comes to generation of shitload of XML descriptors - xdoclet comes to full strength... regards, ===== Konstantin Priblouda ( ko5tik ) Freelance Software developer < http://www.pribluda.de > < play java games -> http://www.yook.de > < render charts online -> http://www.pribluda.de/povray/ > __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com |
From: Max R. A. <ma...@eo...> - 2002-12-31 13:21:30
|
And I've added some replies there also :) (look for "- Max") /max ----- Original Message ----- From: "Gavin King" <Gav...@ex...> To: "Max Rydahl Andersen" <ma...@eo...>; <hib...@li...> Sent: Tuesday, December 31, 2002 7:09 AM Subject: RE: [Hibernate] Tools road map My comments are now added in /italics/ on the page itself... > -----Original Message----- > From: Max Rydahl Andersen [mailto:ma...@eo...] > Sent: Tuesday, 31 December 2002 7:16 AM > To: hib...@li... > Subject: [Hibernate] Tools road map > > > I've been so "insane" to plot down a "road-map" for the Tools > in Hibernate...it actually turned out to include more than an > road-map... So please take a look at > http://hibernate.bluemars.net/52.html > > And please provide any comment you see fit :) > > /max > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > hibernate-devel mailing list hib...@li... > https://lists.sourceforge.net/lists/listinfo/hibernate-devel > ********** CAUTION - Disclaimer ********** This message may contain privileged and confidential information. If you are not the intended recipient of this message (or responsible for delivery of the message to such person) you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error, you should destroy it and kindly notify the sender by reply e-mail. Please advise immediately if you or your employer do not consent to Internet e-mail for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of Expert Information Services Pty Ltd ("The Company") shall be understood as neither given nor endorsed by it. The Company advises that this e-mail and any attached files should be scanned to detect viruses. The Company accepts no liability for loss or damage (whether caused by negligence or not) resulting from the use of any attached files. **EIS******** End of Disclaimer ********** ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ hibernate-devel mailing list hib...@li... https://lists.sourceforge.net/lists/listinfo/hibernate-devel |
From: Max R. A. <ma...@eo...> - 2002-12-31 13:20:40
|
> > > * Is there any chance to add predefined queries > > to the > > > generated mapping? > > > > Ummm, I thought theres was a @hibernate.query tag > > > > > * Is there any chance to generate the > > bean-pattern > > > (setXXX(), getXXX() > > > and especially the > > addXXX(Child)/setXXX(Parent)) methods of the > > > java-bean class? I really do not like to write > > them down... > > Yes, xdoclet can be tricked to do this. But this > feature is not implemented - though nobody prevents > you from hacking templates. > But it seems to be not very usefull for me. > XDoclet can generate derived class for you, and > all kinds of methods in this class. But this way you > would lose main advantage of using hibernate vs entity > beans - to get rid of paralel class hierarchies... Just corius, why does generating add, set, get for the hibernate beans makes you loose any advantage ? (Where is there created a prallel class hierarchy?) /max |
From: Max R. A. <ma...@eo...> - 2002-12-31 13:17:06
|
> > <property name="bar" type="serializable" ....> > > <meta attribute="description"> > > JavaDoc comment for getBar() > > </meta> > > <meta attribute="java-type">java.lang.Object</meta> > > </property> > > ..... > > But this one ? Isn't this a bit "cloudy".... > If I understand this correctly you want that if "java-type" > is provided the codegenerator should use that type instead of > the type specified in the property....Just curious, when is > that usefull ? >For example: ><property name="date" type="date"/> >currently generates: >public java.sql.Date getDate(); >what if you wanted >public java.util.Date getDate(); hmm - ok, I see your point...will look into it... >Hey, I just thought of another <meta> that would be *very* useful: ><property name="bar" type="String" ....> ><meta name="scope">protected</meta> ><meta attribute="description"> >JavaDoc comment for getBar() ></meta> ></property> >surprised I didn't think of that before.... I actually think about this before, but could not come to term with me in what the scope should mean... Its it the actual field, the getX() or the setX() that should be modified ? (The same actually goes for the "description" tag...) How about having "description-get", "description-set" and just "description" for the actual field ? (or should it be "description-field" And then similarily "scope-get", "scope-set" and "scope"/"scope-field" for the actual field ? Maybe "scope" and "description" should just apply for both set, get and field if nothing else is specified ? Any thoughts ? /max |
From: Konstantin P. <kpr...@ya...> - 2002-12-31 11:01:56
|
--- Gavin King <Gav...@ex...> wrote: > > > * Is there any chance to add predefined queries > to the > > generated mapping? > > Ummm, I thought theres was a @hibernate.query tag > > > * Is there any chance to generate the > bean-pattern > > (setXXX(), getXXX() > > and especially the > addXXX(Child)/setXXX(Parent)) methods of the > > java-bean class? I really do not like to write > them down... Yes, xdoclet can be tricked to do this. But this feature is not implemented - though nobody prevents you from hacking templates. But it seems to be not very usefull for me. XDoclet can generate derived class for you, and all kinds of methods in this class. But this way you would lose main advantage of using hibernate vs entity beans - to get rid of paralel class hierarchies... > (Anyway, I just let Eclipse generate my get/set > pair.) I do this with jEdit. Just wrote small velocity template... regards, ===== Konstantin Priblouda ( ko5tik ) Freelance Software developer < http://www.pribluda.de > < play java games -> http://www.yook.de > < render charts online -> http://www.pribluda.de/povray/ > __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com |