April 2012 - hibernate-issues - Jboss List Archives

[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, 6 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, 6 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, 6 months

2
3
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, 6 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, 6 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, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-677) Blob is null with Postgresql

by Aaron Luchko (JIRA)

Blob is null with Postgresql ---------------------------- Key: ANN-677 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-677 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.2.1 Environment: hibernate-3.2.1, hibernate-annotations-3.2.1, postgresql-8.2.5-1.fc7, postgresql-jdbc-8.2.504-1jpp.fc7 and postgresql-8.2-506.jdbc4.jar Reporter: Aaron Luchko Attachments: hibPostgresbug.zip I've found that after a sequence of queries, starting new transactions and clearing the session, a Blob will not be successfully from the database and null will be returned by the InputStream instead. Using the debugger I've followed this into the jdbc code and from what I can tell some message is sent to load the blob but the database replies with an empty set of data which naturally causes the InputStream to read null. I've attached a test case (sorry, no makefile or pom.xml, I just ran it using eclipse) which, for me, replicates the bug. Note I've also used hsqldb and mysql and didn't see the bug with them, only postgresql. thanks, Aaron -- 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, 6 months

4
4
0 / 0

[Hibernate-JIRA] Created: (JPA-8) JPA Blob feature severely lacking! It does not support java.sql.Blob interface! Any fix in Hibernate JPA?

by Colbert Philippe (JIRA)

JPA Blob feature severely lacking! It does not support java.sql.Blob interface! Any fix in Hibernate JPA? ------------------------------------------------------------------------------------------------------------ Key: JPA-8 URL: http://opensource.atlassian.com/projects/hibernate/browse/JPA-8 Project: Java Persistence API Issue Type: Improvement Reporter: Colbert Philippe My issue has to do with the Blob feature under JPA. The JPA standard documentation says that : (I quote) "The Java types mappled to BLOB columns are byte[], Byte[], Serializable type, while char[], Character[] and String are mapped to CLOB". There is an important function missing in this statement. This feature is given by JDBC and made available in Hibernate Persistence. Why is it missing in JPA? The way JPA is implemented all BLOB objects are either not-loaded into memory or completely loaded into memory. What happens when an application only wants to work with only part of the BLOB object, not the entire BLOB object? THE MISSING FEATURE: JDBC and Hibernate, allow for declaration of fields of type java.sql.Blob (interface). This interface has special functionality that allows an application to load only part of a BLOB object (not the entire Blob object, which can be very big) . Similarly, the Blob interface allows an application to write to only part of BLOB object (not the entire BLOB object). These two important functions are lost in JPA! That's a severe drawback! My question is: Is there a way of going around the JPA standard and allow support for java.sql.Blob columns? Colbert -- 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, 6 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-4635) Oracle ORA-24816 inserting and updating data for entities containg LOB attributes

by Clay Atkins (JIRA)

Oracle ORA-24816 inserting and updating data for entities containg LOB attributes --------------------------------------------------------------------------------- Key: HHH-4635 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4635 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Reporter: Clay Atkins Priority: Critical Inserting or updating an entity with LOB results in the following error from oracle: {noformat} Caused by: java.sql.SQLException: ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column {noformat} Fairly confident that the ordering of the LOB attributes is not putting them at the end of the insert or the update. Oracle requires all LOB columns to be the last in the statement. -- 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, 6 months

9
23
0 / 0

[Hibernate-JIRA] Created: (HBX-978) unique=true attribute of primary key in generated class prevents the schema to be regenerated

by Ali Sadik Kumlali (JIRA)

unique=true attribute of primary key in generated class prevents the schema to be regenerated --------------------------------------------------------------------------------------------- Key: HBX-978 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-978 Project: Hibernate Tools Issue Type: Bug Environment: OS: Windows Vista 6.0,x86 Database: Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production Java VM: Java HotSpot(TM) Server VM 1.5.0_11-b03,Sun Microsystems Inc. Eclipse Europa: Version: 3.3.0 Build id: I20070621-1340 HibernateTools-3.2.0.beta10 Reporter: Ali Sadik Kumlali Priority: Minor Hi, When I reverse engineer against Oracle, unique=true attribute is added to @Column annotation of primary key column. But, when I generate schema from these generated files, Oracle throws "ORA-02261: such unique or primary key already exists in the table" error. I first ran into this situation while trying Seam and posted the problem to Seam's forum: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=116478. After I got the response, decided to try it without Seam. Then, downloaded the latest HibernateTools & Eclipse Europa and reverse engineered the schema. I saw that generated classes have unique=true attribute which clearly showed that the problem was related with HibernateTools, not with Seam. Here is the DDL of the table against which I made my test: CREATE TABLE PEOPLE ("ID" NUMBER NOT NULL, "SURNAME" VARCHAR2(50 BYTE), "NAME" VARCHAR2(25 BYTE), CONSTRAINT "PEOPLE_PK" PRIMARY KEY ("ID")); Regards, Ali Sadik Kumlali -- 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, 6 months

8
11
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 April 2012