I noticed this problem has been posted before, but the <key-many-to-one> does not have 'insert' and 'update' attribute so I can set them to false. Is there a different way to appraoch this error when using <key-many-to-one>? As you can see below PROJECT_ID is used twice in wto different foreign key constraints.

Thanks in advance for any help


Hibernate version:
3.0
Mapping documents:



Code between sessionFactory.openSession() and session.close():
NA
Full stack trace of any exception that occurs:
09:56:28,000 INFO HbmBinder:1974 - Mapping collection: com.RTvdMethod.SetOfStratWellSection -> STRAT_WELL_SECTION
09:56:28,000 INFO HbmBinder:1974 - Mapping collection: com.RTvdMethod.SetOfStratFieldSection -> STRAT_FIELD_SECTION
09:56:28,000 INFO Configuration:865 - processing association property references
09:56:28,000 INFO Configuration:894 - processing foreign key constraints
%%%% Error Creating SessionFactory %%%%
org.hibernate.MappingException: Repeated column in mapping for entity: com.ProjectStepXref column: PROJECT_ID (should be mapped with insert="false" update="false")
at org.hibernate.mapping.PersistentClass.checkColumnDuplication(PersistentClass.java:504)
at org.hibernate.mapping.PersistentClass.checkColumnDuplication(PersistentClass.java:542)
at org.hibernate.mapping.PersistentClass.validate(PersistentClass.java:335)
at org.hibernate.mapping.RootClass.validate(RootClass.java:188)
at org.hibernate.cfg.Configuration.validate(Configuration.java:816)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1050)
at com.HibernateSessionFactory.currentSession(HibernateSessionFactory.java:49)
at driver.Driver.main(Driver.java:24)
java.lang.NullPointerException
at com.HibernateSessionFactory.currentSession(HibernateSessionFactory.java:56)
at driver.Driver.main(Driver.java:24)
Exception in thread "main"


Name and version of the database you are using:
Oracle 10g

The generated SQL (show_sql=true):
NA

Debug level Hibernate log excerpt:
NA

I advise against use of <key-many-to-one>, especially in this case. Replace with a <key-property>, and also a <many-to-one insert=false update=false>.

Would this be the correct way using <key-property> and <many-to-one>? Just making sure, since other tables are producing the same error, and there are a total of 1300 tables. By the way if you need the Hibernate tools eclipse plugin to process 1200 tables ... system requirements are at least 2GB if Oracle is running on another machine. Ran like a dream! By the way, the <key-many-to-one> is being generated by the plugin. I noticed an open jira issues on this, so maybe in the future I will not have to manually change the <key-many-to-one> to <key-property> <many-to-one>.

Thanks in advance! :)