Hello,

I am using Middlegen R5. Composite keys are a real pain. In many cases they are not needed, for example when the is an auto incrementing part. I am dealing with a large legacy (Oracle) database that cannot be changed. Is there a way to tell Middlegen NOT to generate composite keys at all? I know I can manually edit the xml files but there are over a hundred and the assosiations are as hard to track down as the keys themselves.

Thanks and good job!
Tim

Yes composite keys are a pain. It also sounds like your database schema is not a good one. Currently there is no way to turn off composite key generation - not practical anyway - how do you automatically determine an appropriate key. Anyway, since you have your own rules for key selection, I would suggest you edit a copy of the velocity script. The composite key sections are obvious (and makes up a large portion of the script). This way you only edit one file rather than all of the hbm's.

I agree. My fix though was to write my own sequence generator but not as a sub class of hibernate's. I figured that since I have to invoke the generator myself I might as well decouple it.

So I ended up with:

.....Java code frag
seqGenerator sgen = new seqGenerator();

hibObj.City city = new hibObj.City();
sgen.setId(city); // sets sequential id from sequence in oracle
hibernateUtil.currentSession().save(city);

seqGenerator.setId() figures out the sequence name and the name of the id method ("set" + classname + "Id") and sets the value returned from the call to the sequence, always a Long.

It also knows how to handle composit id objects (classname + "PK") -- this is the evil thing that started all of this!

I can also run setId() on a any object whether or not it has a sequence associated with it.

I wrote and tested all of it in 1 day. Much faster than the alternative which was going to be a Perl script to add all of the <generator> stuff to the (100+) hbm.xml files and the hibernate specific generator for composites.

Cool. Nice work.