February 2011 - hibernate-issues - Jboss List Archives

[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

[Hibernate-JIRA] Created: (HHH-5798) Is it really necessary to explicitly specifiy discriminatorValue for abstract classes?

by Oleksandr Alesinskyy (JIRA)

Is it really necessary to explicitly specifiy discriminatorValue for abstract classes? -------------------------------------------------------------------------------------- Key: HHH-5798 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5798 Project: Hibernate Core Issue Type: Improvement Components: entity-manager Affects Versions: 3.6.0 Reporter: Oleksandr Alesinskyy At the time being if the SINGLE_TABLE inheritance strategy is used, the discriminator type is set to char and some abstract classes in the hierarchy do not have an explicit discriminator value specified the following error occurs: {quote} Caused by: org.hibernate.AnnotationException: Using default @DiscriminatorValue for a discriminator of type CHAR is not safe at org.hibernate.cfg.annotations.EntityBinder.bindDiscriminatorValue(EntityBinder.java:373) at org.hibernate.cfg.annotations.EntityBinder.bindEntity(EntityBinder.java:200) at org.hibernate.cfg.AnnotationBinder.bindClass(AnnotationBinder.java:586) at org.hibernate.cfg.Configuration$MetadataSourceQueue.processAnnotatedClassesQueue(Configuration.java:3977) at org.hibernate.cfg.Configuration$MetadataSourceQueue.processMetadata(Configuration.java:3931) at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1368) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1345) at org.hibernate.ejb.Ejb3Configuration.buildMappings(Ejb3Configuration.java:1477) at org.hibernate.ejb.EventListenerConfigurator.configure(EventListenerConfigurator.java:193) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:1096) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:685) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73) {quote} At the same time it is clear that no one row in the corresponding table may represent the abstract class, so it is absolutely safe to completely ignore abstract classes when decision is made which class is represented by a row. -- 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
3
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

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

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

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

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

13 years, 6 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HHH-5841) Invalid table creation in Annotations Test Cases

by Fred Toussi (JIRA)

Invalid table creation in Annotations Test Cases ------------------------------------------------ Key: HHH-5841 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5841 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.6.next Environment: Tested with HSQLDB 2.0.1 Reporter: Fred Toussi Some tests create a table with the definition like the one below. As Standard SQL does not allow two unique constraints (or one unique and one PK) on the same column(s) the table definition fails, resulting in test failure. 23:41:40,437 DEBUG SchemaExport:415 - create table MedicalHistory ( lastupdate date, FK varchar(255) not null, primary key (FK), unique (FK) ) The pattern of failure shows in several tests. For example: package org.hibernate.test.annotations.derivedidentities.e4.a; DerivedIdentitySimpleParentSimpleDepTest To reproduce, use an up-to-date HSQLDB 2.0.1 RC from http://hsqldb.org (I have not checked with 2.0.0, as this version has been superseded) -- 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, 7 months

3
2
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 February 2011