[Hibernate-JIRA] Created: (OGM-174) Composite id fail on MongoDB: MongoDBDialect only takes the first id column into account and force _id
9:26 a.m.
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
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
7:50 a.m.
New subject: [Hibernate-JIRA] Assigned: (OGM-174) Composite id fail on MongoDB: MongoDBDialect only takes the first id column into account and force _id
[
https://hibernate.onjira.com/browse/OGM-174?page=com.atlassian.jira.plugi...
]
Guillaume Scheibel reassigned OGM-174:
--------------------------------------
Assignee: Guillaume Scheibel
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
7:52 a.m.
New subject: [Hibernate-JIRA] Commented: (OGM-174) Composite id fail on MongoDB: MongoDBDialect only takes the first id column into account and force _id
[
https://hibernate.onjira.com/browse/OGM-174?page=com.atlassian.jira.plugi...
]
Guillaume Scheibel commented on OGM-174:
----------------------------------------
In the tests, should I @IdClass, @EmbeddedId or both ?
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
8:07 a.m.
New subject: [Hibernate-JIRA] Issue Comment Edited: (OGM-174) Composite id fail on MongoDB: MongoDBDialect only takes the first id column into account and force _id
[
https://hibernate.onjira.com/browse/OGM-174?page=com.atlassian.jira.plugi...
]
Guillaume Scheibel edited comment on OGM-174 at 5/16/12 8:05 AM:
-----------------------------------------------------------------
In the tests, should I use @IdClass, @EmbeddedId or both ?
was (Author: guillaume):
In the tests, should I @IdClass, @EmbeddedId or both ?
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
9:37 a.m.
New subject: [Hibernate-JIRA] Commented: (OGM-174) Composite id fail on MongoDB: MongoDBDialect only takes the first id column into account and force _id
[
https://hibernate.onjira.com/browse/OGM-174?page=com.atlassian.jira.plugi...
]
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
9:07 a.m.
New subject: [Hibernate-JIRA] Commented: (OGM-174) Composite id fail on MongoDB: MongoDBDialect only takes the first id column into account and force _id
[
https://hibernate.onjira.com/browse/OGM-174?page=com.atlassian.jira.plugi...
]
Guillaume Scheibel commented on OGM-174:
----------------------------------------
A pull request has been created:
https://github.com/hibernate/hibernate-ogm/pull/89
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
1:18 p.m.
New subject: [Hibernate-JIRA] (OGM-174) Composite id fail on MongoDB: MongoDBDialect only takes the first id column into account and force _id
4 a.m.
New subject: [Hibernate-JIRA] (OGM-174) Composite id fail on MongoDB: MongoDBDialect only takes the first id column into account and force _id
4488
days inactive
4628
days old
hibernate-issues@lists.jboss.org
7 comments
2 participants
participants (2)
-
Emmanuel Bernard (JIRA) -
Guillaume Scheibel (JIRA)