in my model I have an abstract superclass which serves the unique id for
all objects in the model. I have the generator annotations from
http://dev.eclipse.org/newslists/news.eclipse.tools.emf/msg41996.html in
place at the package and the id field. The cardinality of the id field in
the super class is 0:1 - it is optional. So basically I should be able to
leave it blank and it should be generated when the objects are stored to
the database, correct?
Now to speed things up, I've set the id, mentioned above, to be the key
for every reference in the model. I've used the keys property of the
references to do this. This leads to diagnostics of this pattern:
The feature 'objects' has key [uniqueId=null] for
'model.impl.ObjectImpl@1e45641{hibernate://?dsname=ModelStore#//@objects[uniqueId=null]}'
which collides with that of
'model.impl.ObjectImpl@1f1779e{hibernate://?dsname=ModelStore#//@objects[uniqueId=null]}'
Is there any way to fix this without loosing the performance gained from
having an index in the database for the references?