June 2012 - hibernate-issues - Jboss List Archives

[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

13 years, 9 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

13 years, 9 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

13 years, 9 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

13 years, 9 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

13 years, 9 months

2
3
0 / 0

[Hibernate-JIRA] Created: (OGM-179) Consider whether or not it is fine to store the same id value in both the identifier column and _id in MongoDB

by Emmanuel Bernard (JIRA)

Consider whether or not it is fine to store the same id value in both the identifier column and _id in MongoDB -------------------------------------------------------------------------------------------------------------- Key: OGM-179 URL: https://hibernate.onjira.com/browse/OGM-179 Project: Hibernate OGM Issue Type: Bug Components: datastore Reporter: Emmanuel Bernard Fix For: mongodb -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[Hibernate-JIRA] Created: (OGM-148) support for more types in BuiltinTypeTest

by Oliver Carr (JIRA)

support for more types in BuiltinTypeTest ----------------------------------------- Key: OGM-148 URL: https://hibernate.onjira.com/browse/OGM-148 Project: Hibernate OGM Issue Type: Improvement Components: core Reporter: Oliver Carr Assignee: Oliver Carr To help with new dialects like MongoDB add extra type coverage to the BuiltInType test. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
3
0 / 0

[Hibernate-JIRA] Created: (OGM-152) TimeZone Not Persisted

by Oliver Carr (JIRA)

TimeZone Not Persisted ----------------------- Key: OGM-152 URL: https://hibernate.onjira.com/browse/OGM-152 Project: Hibernate OGM Issue Type: Bug Components: core Affects Versions: mongodb Environment: all databases hibernate-core-4.1-FINAL Reporter: Oliver Carr Assignee: Oliver Carr Fix For: mongodb TimeZone information from Calendar objects are not persisted in hibernate OGM because it use the org.hibernate.type.descriptor.java.CalendarDateTypeDescriptor class mapping only; dd MMMM yyyy The class org.hibernate.type.descriptor.java.TimeZoneTypeDescriptor.class from hibernate-core should be used as well possibly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
3
0 / 0

[Hibernate-JIRA] Created: (OGM-180) Make MongoDB safe option defaults true in Hibernate OGM

by Emmanuel Bernard (JIRA)

Make MongoDB safe option defaults true in Hibernate OGM ------------------------------------------------------- Key: OGM-180 URL: https://hibernate.onjira.com/browse/OGM-180 Project: Hibernate OGM Issue Type: Improvement Components: datastore Reporter: Emmanuel Bernard Fix For: mongodb I am now convinced that safe=false is a very very bad default and that we should override it. I'd rather see people forcing safe to false. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3835) ORA-00932 when executing a HQL with "distinct" on an entity with a Blob

by Martin Zeltner (JIRA)

ORA-00932 when executing a HQL with "distinct" on an entity with a Blob ----------------------------------------------------------------------- Key: HHH-3835 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3835 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.2.6 Environment: Oracle 10 Reporter: Martin Zeltner Hi I get an Oracle exception "ORA-00932: inconsistent datatypes: expected - got BLOB" when I execute a HQL on an entity that has a blob and the HQL contains the "distinct". When I remove the "distinct" then it works. HQL: "select distinct ci from CircuitInstruction ci ..." Entity "CircuitInstruction" has the following property: /** * @return Returns the CI PDF. */ @Lob @Basic(fetch = FetchType.LAZY) public Blob getCiPdf() { return m_ciPdf; } Cheers Martin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues June 2012