September 2012 - hibernate-issues

[Hibernate-JIRA] (OGM-235) Remove testsuite Skip setting to avoid ISPN-2149

by Sanne Grinovero (JIRA)

12 years, 3 months

1
1
0 / 0

[Hibernate-JIRA] Created: (OGM-147) Update project documentation with the mongodb implementation

by Guillaume Scheibel (JIRA)

Update project documentation with the mongodb implementation ------------------------------------------------------------ Key: OGM-147 URL: https://hibernate.onjira.com/browse/OGM-147 Project: Hibernate OGM Issue Type: New Feature Components: documentation Reporter: Guillaume Scheibel Priority: Minor The point is to update the hibernate-ogm-documentation project with all the requiered information about the MongoDB implementation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
3
0 / 0

[Hibernate-JIRA] Created: (OGM-166) Add parameters to build to override MongoDB instance used for tests

by Sanne Grinovero (JIRA)

Add parameters to build to override MongoDB instance used for tests ------------------------------------------------------------------- Key: OGM-166 URL: https://hibernate.onjira.com/browse/OGM-166 Project: Hibernate OGM Issue Type: Task Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: mongodb Currently the instance the testsuite will use is hardcoded in properties files. We need to be able to override this for those who have the Mongo instance running on a different host/port. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (OGM-169) configurable where/how associations are stored in MongoDB dialect

by Alan (JIRA)

configurable where/how associations are stored in MongoDB dialect ----------------------------------------------------------------- Key: OGM-169 URL: https://hibernate.onjira.com/browse/OGM-169 Project: Hibernate OGM Issue Type: Improvement Components: datastore Affects Versions: mongodb Reporter: Alan Priority: Minor Add a configuration property which will allow user to choose where associations are stored: 1) in a prefixed collection - eg. associations_Entity. 2) in a global collection. 3) in the same collection as the entity, in a separate document at the same level. I've done this, patch will follow. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (OGM-176) Embed @ElementCollection within the entity owning the collection

by Emmanuel Bernard (JIRA)

Embed @ElementCollection within the entity owning the collection ---------------------------------------------------------------- Key: OGM-176 URL: https://hibernate.onjira.com/browse/OGM-176 Project: Hibernate OGM Issue Type: New Feature Components: datastore Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Fix For: mongodb -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
2
0 / 0

[Hibernate-JIRA] Created: (OGM-174) Composite id fail on MongoDB: MongoDBDialect only takes the first id column into account and force _id

by Emmanuel Bernard (JIRA)

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

12 years, 3 months

2
7
0 / 0

[Hibernate-JIRA] Created: (OGM-156) Avoid using a table scan with MongoDB nextValue implementation

by Sanne Grinovero (JIRA)

Avoid using a table scan with MongoDB nextValue implementation -------------------------------------------------------------- Key: OGM-156 URL: https://hibernate.onjira.com/browse/OGM-156 Project: Hibernate OGM Issue Type: Improvement Reporter: Sanne Grinovero Fix For: mongodb I'm referring to the MongoDBDialect.nextValue implementation: when enabling the configuration option {code}notablescan = true{code} the tests using it fail. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
4
0 / 0

[Hibernate-JIRA] Created: (OGM-144) Support associations in MongoDB

by Emmanuel Bernard (JIRA)

Support associations in MongoDB ------------------------------- Key: OGM-144 URL: https://hibernate.onjira.com/browse/OGM-144 Project: Hibernate OGM Issue Type: New Feature Components: datastore Reporter: Emmanuel Bernard h3. Proposal 1 {code:json} { "_id" : ObjectId("4f7486c6318ca0fafa7761d0"), "columnNames" : [ "addresses_id" ], "columnValues" : [ "169e2d61-ce39-4bca-8300-185487df7119" ], "rows" : { "-387062339" : { "table" : "User_Address", "columnNames" : [ "User_id", "nick" ], "columnValues" : [ "f11e01e8-7c2f-4795-81dc-94de7c4ba246", "home" ] } }, "table" : "User_Address" } {code} h3. Proposal 2 {code:json} //example 2: closer to how entities are stored { "_id" : ObjectId("4f7486c6318ca0fafa7761d0"), "table" : "User_Address", "columnNames" : [ "addresses_id" ], "columnValues" : [ "169e2d61-ce39-4bca-8300-185487df7119" ], "rows" : { "9d2386c6318ca0fafa32867ae" : { "User_id": "f11e01e8-7c2f-4795-81dc-94de7c4ba246", "nick": "home" } } } {code} h3. Proposal 3 assuming MongoDB collection == table {code:json} //example 3: considering that MongoDB collections == tables // in collection "User_Address" { "_id" : ObjectId("4f7486c6318ca0fafa7761d0"), "addresses_id": "169e2d61-ce39-4bca-8300-185487df7119", "rows" : { "9d2386c6318ca0fafa32867ae" : { "User_id": "f11e01e8-7c2f-4795-81dc-94de7c4ba246", "nick": "home" } } } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
6
0 / 0

[Hibernate-JIRA] Created: (OGM-162) Have an option to build the project without requiring a running MongoDB instance

by Sanne Grinovero (JIRA)

Have an option to build the project without requiring a running MongoDB instance -------------------------------------------------------------------------------- Key: OGM-162 URL: https://hibernate.onjira.com/browse/OGM-162 Project: Hibernate OGM Issue Type: Task Components: build Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: mongodb -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
5
0 / 0

[Hibernate-JIRA] Created: (OGM-143) Implement dialect.nextValue in MongoDB

by Emmanuel Bernard (JIRA)

Implement dialect.nextValue in MongoDB -------------------------------------- Key: OGM-143 URL: https://hibernate.onjira.com/browse/OGM-143 Project: Hibernate OGM Issue Type: New Feature Components: datastore Reporter: Emmanuel Bernard MongoDB ha the notion of findAndModify operation that is perfect to map nextValue. http://www.mongodb.org/display/DOCS/findAndModify+Command What they call side counter method http://www.mongodb.org/display/DOCS/How+to+Make+an+Auto+Incrementing+Field -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2012