[hibernate-issues] [Hibernate-JIRA] Commented: (OGM-174) Composite id fail on MongoDB: MongoDBDialect only takes the first id column into account and force _id
Emmanuel Bernard (JIRA)
noreply at atlassian.com
Wed May 16 10:37:11 EDT 2012
[ https://hibernate.onjira.com/browse/OGM-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46676#comment-46676 ]
Emmanuel Bernard commented on OGM-174:
--------------------------------------
Both but start with @EmbeddedId. If there is any difference, @EmbeddedId will be simpler
> Composite id fail on MongoDB: MongoDBDialect only takes the first id column into account and force _id
> ------------------------------------------------------------------------------------------------------
>
> Key: OGM-174
> URL: https://hibernate.onjira.com/browse/OGM-174
> Project: Hibernate OGM
> Issue Type: Bug
> Components: datastore
> Reporter: Emmanuel Bernard
> Assignee: Guillaume Scheibel
> Priority: Blocker
> Fix For: mongodb
>
>
> MongoDB dialect.getObject(EntityKey) does the following
> {code}DBObject searchObject = new BasicDBObject( ID_FIELDNAME, key.getColumnValues()[0] );{code}
> This cannot work in composite id environments. Same in createTuple()
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list