The 'id integer' is hibernates way to implement the 'ordered' constraint on an association from another object! This becomes AndroMDA:s problem since it (andromda) needs to tell hibernate which attribute to use for ordering. This is done by <index column="id"/> which aparently causes the conflict to happen. I'll investigate and file in jira. _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=85#85
------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
