Not sure if this should be considered a bug or not (and maybe it should be considered a hibernate bug, if it is a bug)
Basically if you have a long class name and a long primary id name and you use @ManyToMany without specifying a @JoinColumn, when the EJB3 layer (through hibernate) tries to create the table DB2 will throw an error that the column name is longer then 30 characters. It would be nice if the DB2Dialect or EJB3 (not sure who is creating the database) would be able to realize that for DB2 the column name should be at most 30 characters and try to generate a shorter id. I also have a question: Is EJB3 or Hibernate using a hash() in my entities? And if yes, what is it using it for? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910128#3910128 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3910128 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
