September 2010 - hibernate-issues

[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

11 years, 8 months

4
4
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

11 years, 8 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

11 years, 8 months

8
11
0 / 0

[Hibernate-JIRA] Created: (HHH-3135) SQL Server Dialect maps BIGINT to NUMERIC(19,0)

by Dominik Enkelmann (JIRA)

SQL Server Dialect maps BIGINT to NUMERIC(19,0) ----------------------------------------------- Key: HHH-3135 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3135 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: MS SQL Server Reporter: Dominik Enkelmann Priority: Trivial The SQLServerDialect.java maps the Hibernate BIGINT type to a NUMERIC(19,0) colum. The result is, that all Long fields in persisten classes map to hibernate-bigints which generate numeric(19,0) database column. Longs are typically used for surrogate primary keys and should be implemented as native SQL BIGINTs where possible. SQL Server supports SQL BIGINT since version 2000. There is a similar issue with the SQL BIT type that should be implemented as a native BIT column in SQL Server. A possible solution could be a pre-.SQL Server 2000 dialect and an updated SQL Server dialect. I filed a more detailed description with workaround in the user forum http://forum.hibernate.org/viewtopic.php?p=2377674#2377674 -- 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

11 years, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2942) Improve support for PostgreSQL

by Diego Pires Plentz (JIRA)

Improve support for PostgreSQL ------------------------------ Key: HHH-2942 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2942 Project: Hibernate3 Issue Type: Improvement Components: metamodel Reporter: Diego Pires Plentz Assignee: Diego Pires Plentz Priority: Minor Improve support for features in PostgreSQL 7.x and 8.x. I will probably create a new one for 8.x series. I asked for help of postgresql hackers. http://archives.postgresql.org/pgsql-hackers/2007-11/threads.php#00462 Docs index: http://www.postgresql.org/docs/ -- 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

11 years, 8 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5585) SubDialect of PostgreSQLDialect to support (@Lob + byte[]) combination

by Justin Sands (JIRA)

SubDialect of PostgreSQLDialect to support (@Lob + byte[]) combination ---------------------------------------------------------------------- Key: HHH-5585 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5585 Project: Hibernate Core Issue Type: Patch Environment: 3.6.0.CR1, postgresql Reporter: Justin Sands Attachments: CustomPostgreSQLDialect.zip >From hibernate 3.5 to 3.6 the annotation combination @Lob + byte[] does not on postgresql work due to idiosyncrasies in the postgresql JDBC driver. To support this combination, the following dialect variant can be used along with a basic-type override, provided that the application consistently uses the same annotation style (@Lob + byte[]). A similar approach could be used to support using the OID blob type which postgresql provides, although this patch does not address it. The user must register the basic type override MateralizedVarBinaryBlobType at boot time. I am unsure exactly where in the distribution this would fit so I have kept it in one package (org.hibernate.dialect.variant). I have test cases which I could detach from my current project, if the maintainers think this patch is worth including. -- 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

11 years, 8 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HBX-935) H2MetaDataDialect for identity detection

by Max Rydahl Andersen (JIRA)

H2MetaDataDialect for identity detection ---------------------------------------- Key: HBX-935 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-935 Project: Hibernate Tools Issue Type: Sub-task Components: reverse-engineer Affects Versions: 3.2beta9 Reporter: Max Rydahl Andersen Fix For: 3.2beta10 -- 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

11 years, 8 months

4
15
0 / 0

[Hibernate-JIRA] Created: (HHH-5376) Tests contain invalid SQL

by Fred Toussi (JIRA)

Tests contain invalid SQL ------------------------- Key: HHH-5376 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5376 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.x Environment: Using HSQLDB 2.0.1 and Hibernate trunk (12 July 2010) Reporter: Fred Toussi These create table statements declare both primary key and unique constraints on the same set of columns. This is against the SQL standard and will fail with most databases. public class DerivedIdentitySimpleParentSimpleDepTest extends TestCase { 22:52:06,265 ERROR SchemaExport:386 - Unsuccessful: create table MedicalHistory (lastupdate date, FK varchar(255) not null, primary key (FK), unique (FK)) 22:52:06,265 ERROR SchemaExport:387 - a UNIQUE constraint already exists on the set of columns in statement [create table MedicalHistory (lastupdate date, FK varchar(255) not null, primary key (FK), unique (FK))] public class DerivedIdentityIdClassParentSameIdTypeIdClassDepTest extends TestCase { public void testOneToOneExplicitJoinColumn() throws Exception { 23:16:18,328 DEBUG SchemaExport:415 - create table MedicalHistory ( FK1 varchar(255) not null, FK2 varchar(255) not null, primary key (FK1, FK2), unique (FK1, FK2) ) 23:16:18,328 ERROR SchemaExport:386 - Unsuccessful: create table MedicalHistory (FK1 varchar(255) not null, FK2 varchar(255) not null, primary key (FK1, FK2), unique (FK1, FK2)) 23:16:18,328 ERROR SchemaExport:387 - a UNIQUE constraint already exists on the set of columns in statement [create table MedicalHistory (FK1 varchar(255) not null, FK2 varchar(255) not null, primary key (FK1, FK2), unique (FK1, FK2))] -- 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

11 years, 8 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4751) Fix for @embeddedid error: Type not supported: org.hibernate.type.ManyToOneType

by David Coleman (JIRA)

Fix for @embeddedid error: Type not supported: org.hibernate.type.ManyToOneType -------------------------------------------------------------------------------- Key: HHH-4751 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4751 Project: Hibernate Core Issue Type: Improvement Components: envers Reporter: David Coleman Priority: Minor Attachments: IDMetadataGenerator_patch.txt Hi, After creating hibernate entities from the legacy database with envers hibernate tool, I noticed the following error occurred on creating an audit tables that has an @EmbeddedId attribute (related to ENVERS-76]: Caused by: org.hibernate.MappingException: Type not supported: org.hibernate.type.ManyToOneType .. I found out by looking at the source that the reason it failed was that the property type was not an instance of ImmutableType (not mutable); which was true as the embedded id was a combination of an int and a mutable java data object. I switched the mutable java date object to a immutable joda datetime object using the joda date time hibernate user type to fix the immutable problem. I also patched IdMetadataGenerator locally to the one attached as hibernate usertypes do not implement the ImmutableType interface; using the method 'isMutable()' should be suffice. Let me know if this is okay so I can submit the patch. -- 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

11 years, 9 months

7
29
0 / 0

[Hibernate-JIRA] Created: (HHH-5188) Use provided enum type ordinal/string when reading

by Stefan Larsson (JIRA)

Use provided enum type ordinal/string when reading -------------------------------------------------- Key: HHH-5188 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5188 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1, 3.5.0-CR-2 Reporter: Stefan Larsson Priority: Minor Attachments: EnumType.java-typeSafeNullSafeGet.patch When Hibernate reads a PostgreSQL enum type using ResultSet.getObject(), the JDBC driver returns a driver-specific PGObject object, which preserves both the value of the enum and its type ordinal/string. Hibernate fails with a ClassCastException when it attempts to cast the PGObject into a String in org.hibernate.type.EnumType.nullSafeGet(). The code in org.hibernate.type.EnumType assumes that ResultSet.getObject() will either return a Number or a String, which is not true for the PostgreSQL driver. IMHO it would be better to let the JDBC driver do the conversion using ResultSet.getInt() or getString() instead. The attached patch allows JBoss AS 6 M3 (Hibernate 3.5.0-CR-2) to read PostgreSQL enums, using JPA, with a a Java enum annotated as @javax.persistence.Enumerated(javax.persistence.EnumType.STRING). Also, I believe that perhaps ignoring the given enum type causes Issue HHH-4230, where an ordinal enum was stored in character field. ResultSet.getInteger() might work for that one depending on the JDBC driver. -- 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

11 years, 9 months

5
18
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2010