| [Teneo]Custom primary key column is not being defined correctly. [message #604438] |
Fri, 06 April 2007 18:41 |
 Michael Kanaley
Messages: 89
Registered: July 2009 |
Member |
|
|
Hi Martin,
According to the page http://www.elver.org/hibernate/ejb3_features.html:
When an eattribute has its ID property set to true and there is no @Id
annotated eattribute in the eclass then the ID eattribute is used. This
default behavior can be changed using the option: ID_FEATURE_AS_PRIMARY_KEY.
When I follow the instructions above and set the ID property (and I don't
set the option), I get a mapping of the form:
<id name="id" type="long">
<column not-null="true" unique="false" name="`id`"/>
</id>
But this mapping does not generate the primary key (and does not set the
unique constraint).
Back in Teneo v200610261350, it generated the mapping below which works
fine.
I am not sure in which specific Teneo version introduced the problem.
<id name="id" type="long" column="`ID`">
<generator class="native"/>
</id>
Let me know if this is a bug or if there is some other setting that I am
missing.
Attached is a plugin (like the others) that duplicates this problem - it
throws a NonUniqueObjectException.
Thanks,
-mike
|
|
|
Powered by
FUDForum. Page generated in 0.02908 seconds
] 
Search
Help
Register
Login
Home
