[Hibernate] R: Hibernate Persistent Enum

he comminity. In the meantime, you can apply the PersistentStringEnum patch with the file attached in JIRA. stefano -Messaggio originale- Da: Anurag Goel [mailto:[EMAIL PROTECTED] Inviato: mercoledì 22 ottobre 2003 20.24 A: Travelli Stefano Oggetto: Hibernate Persistent Enum Stefano,

R: [Hibernate] [OT] bulk importing ideas

This is much easier. Next step is to verify if one of the dialect works with this driver, otherwise you have to write another dialect, but this should be simple. -Messaggio originale- Da: Butt, Dudley [mailto:[EMAIL PROTECTED] Inviato: mercoledì 15 ottobre 2003 20.25 A: Travelli Stefano

R: [Hibernate] [OT] bulk importing ideas

> can hibernate map persist to a csv file, not even persist, just read a csv into an > object? Indeed, it seems you could: "persister" attribute let you specify a custom persister for the class. Then you should build you own persister extending EntityPersister and, just for reading, overrid

R: [Hibernate] problem in using JTA datasources

te explain this topic far better than me. good luck stefano -Messaggio originale- Da: dosapati [mailto:[EMAIL PROTECTED] Inviato: giovedì 25 settembre 2003 12.48 A: Travelli Stefano; [EMAIL PROTECTED] Oggetto: Re: [Hibernate] problem in using JTA datasources Stefano, thanks for your res

R: [Hibernate] huge tring storage

Try sql-type attribute in tag: stefano -Messaggio originale- Da: Justen Stepka [mailto:[EMAIL PROTECTED] Inviato: giovedì 13 febbraio 2003 20.14 A: Justen Stepka; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Oggetto: Re: [Hibernate] huge tring storage What I found

R: R: [Hibernate] [ hibernate-Bugs-684496 ] Nested multiple columns composite-id causes "broken mapping"

Done. http://sourceforge.net/tracker/index.php?func=detail&aid=685907&group_id=40712&atid=428710 stefano -Messaggio originale- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Inviato: giovedì 13 febbraio 2003 8.28 A: Travelli Stefano Cc: [EMAIL PROTECTED] Oggetto: Re: R

R: [Hibernate] [ hibernate-Bugs-684496 ] Nested multiple columns composite-id causes "broken mapping"

Ok. The order is correct. There was an error in the mapping files I was using for the test. There was also a bug in the code of my previous message. I think that this should be the correct version of EntityPersister.postInstantiate in order to manage nested multiple columns composite-id. public

R: [Hibernate] [ hibernate-Bugs-684496 ] Nested multiple columns composite-id causes "broken mapping"

I'm trying to change EntityPersister.postInstantiate method in order to fix the nested multiple columns composite-id. With this implementation the code take care of the exact number of columns for each component of the composite-id. However it doesn't work because the order with which the columns

[Hibernate] composite-id with composite-id key-many-to-one components

Hi, a composite-id composed by a key-many-to-one component witch in turn has a composite-id, causes a "broken mapping error...". I found that this is due to the code in postInstantiate method of EntityPersister class: if ( idType.isComponentType() ) { AbstractComponentType actype = (Ab