May 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Issue Comment Edited: (HHH-1501) insert long string (more than 32700) fails on derby

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Gail Badner edited comment on HHH-1501 at 5/5/10 3:09 PM: ---------------------------------------------------------- In that case, DerbyDialect (or DBDialect?) would need to be updated to work using the JPA defaults. The Hibernate types "materialized_clob" and "materialized_blob" use CLOB and BLOB. was (Author: gbadner): In that case, DerbyDialect (or DBDialect?) would need to be updated to work using the JPA defaults. The Hibernate types "materialized_clob" and "materialized_blob" use "long varchar" and "long varchar for bit data". > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

14 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5198) Generating schema for JoinColumn with SecondaryTable and SingleTable inheritance.

by Yasen Terziivanov (JIRA)

Generating schema for JoinColumn with SecondaryTable and SingleTable inheritance. --------------------------------------------------------------------------------- Key: HHH-5198 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5198 Project: Hibernate Core Issue Type: Bug Components: envers Reporter: Yasen Terziivanov Attachments: envers-test-ejbProject-and-client.zip Well basically as described in [here | https://community.jboss.org/thread/151214] when generating db schema if I have a secondary table and a one2one property and I want to specify that the join column should be in the secondary table using @JoinColumn annotation in the generated script the column is missing from the audited table. This is tested with the 1.2.2 version of envers. -- 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

14 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5194) SequenceHiLoGenerator does not update the lo value

by Swen Thümmler (JIRA)

SequenceHiLoGenerator does not update the lo value -------------------------------------------------- Key: HHH-5194 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5194 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1 Reporter: Swen Thümmler Priority: Critical SequenceHiLoGenerator checks lo > maxLo but never increments lo. This leads to duplicate ids when using the same sequence for multiple tables. This change was made in r18789 -- 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

14 years

2
4
0 / 0

[Hibernate-JIRA] Issue Comment Edited: (HHH-1501) insert long string (more than 32700) fails on derby

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Steve Ebersole edited comment on HHH-1501 at 5/5/10 9:29 AM: ------------------------------------------------------------- Gail, I see MaterializedClob using CLOB not LONGVARCHAR (which makes sense right?). What am i missing? http://fisheye.jboss.org/browse/Hibernate/core/trunk/core/src/main/java/o... http://fisheye.jboss.org/browse/Hibernate/core/branches/Branch_3_5/core/s... Similarly for MaterializedBlob, I see BLOB http://fisheye.jboss.org/browse/Hibernate/core/branches/Branch_3_5/core/s... was (Author: steve): Gail, I see MaterializedClob using CLOB not LONGVARCHAR (which makes sense right?). What am i missing? http://fisheye.jboss.org/browse/Hibernate/core/trunk/core/src/main/java/o... http://fisheye.jboss.org/browse/Hibernate/core/branches/Branch_3_5/core/s... > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

14 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1501) insert long string (more than 32700) fails on derby

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Steve Ebersole commented on HHH-1501: ------------------------------------- Gail, I see MaterializedClob using CLOB not LONGVARCHAR (which makes sense right?). What am i missing? http://fisheye.jboss.org/browse/Hibernate/core/trunk/core/src/main/java/o... http://fisheye.jboss.org/browse/Hibernate/core/branches/Branch_3_5/core/s... > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

14 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1501) insert long string (more than 32700) fails on derby

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Steve Ebersole commented on HHH-1501: ------------------------------------- We are not going to remove these sane attempts at limiting the size of columns we create as the default. If you want to increase the storage size you have a number of options: 1) List the column length in the metadata 2) Use an explicit Hibernate Type declaration ('materialized_clob', etc) which does what you want 3) Supply a custom dialect that defines the sizes *you* want. > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

14 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5183) Inheritance (single table) and @SecondaryTable

by Nicolas Romanetti (JIRA)

Inheritance (single table) and @SecondaryTable ----------------------------------------------- Key: HHH-5183 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5183 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.2 Environment: Hibernate 3.3.2.GA H2 Database version 1.2.131 Reporter: Nicolas Romanetti When @SecondaryTable is declared (with the same secondary table name) in 2 distinct entities that belong to the same hierarchy (single table inheritance), hibernate considers that the secondary tables are different! Indeed, when persisting the entity, if the properties (using the secondary table) are set in the entity itself and its parent, hibernate does 2 inserts on the secondary table instead of one (one for the 'secondary' property of the parent, and one for the 'secondary' property of the current entity) This triggers a pk violation exception as the same PK is used twice on the secondary table. -- 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

14 years

3
3
0 / 0

[Hibernate-JIRA] Commented: (HHH-1501) insert long string (more than 32700) fails on derby

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Gail Badner commented on HHH-1501: ---------------------------------- In that case, DerbyDialect (or DBDialect?) would need to be updated to work using the JPA defaults. The Hibernate types "materialized_clob" and "materialized_blob" use "long varchar" and "long varchar for bit data". > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

14 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5030) BaseRegionAdapter shouldn't rely on optional Cache#toMap method

by Adrian Hummel (JIRA)

BaseRegionAdapter shouldn't rely on optional Cache#toMap method --------------------------------------------------------------- Key: HHH-5030 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5030 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.5.0-CR-2 Environment: hibernate-oscache 3.5.0.Beta-1 Reporter: Adrian Hummel Attachments: bugreport.zip Get an {{UnsupportedOperationException}} when checking the L2 cache if it contains an entity: {code} emf.getCache().contains(MyEntity.class, pk); {code} Result: {code} java.lang.UnsupportedOperationException at org.hibernate.cache.OSCache.toMap(OSCache.java:126) at org.hibernate.cache.impl.bridge.BaseRegionAdapter.contains(BaseRegionAdapter.java:62) at org.hibernate.impl.SessionFactoryImpl$CacheImpl.containsEntity(SessionFactoryImpl.java:967) at org.hibernate.impl.SessionFactoryImpl$CacheImpl.containsEntity(SessionFactoryImpl.java:962) at org.hibernate.ejb.EntityManagerFactoryImpl$JPACache.contains(EntityManagerFactoryImpl.java:164) ... {code} The {{Cache#toMap}} method is optional (according to Javadoc), thus, {{BaseRegionAdapter}} shouldn't rely on this method. -- 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

14 years

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5189) Same table is mapped twice but different primary keys. Giving error while secondPassCompileForeignKeys.

by Sardar Romender Singh (JIRA)

Same table is mapped twice but different primary keys. Giving error while secondPassCompileForeignKeys. ------------------------------------------------------------------------------------------------------- Key: HHH-5189 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5189 Project: Hibernate Core Issue Type: Bug Environment: OS: Linux DB : Oracle Hibernate Version : 3.2.5 ga Reporter: Sardar Romender Singh Priority: Trivial Two tables are mapped with different primary keys. Example : I have customer table which is mapped to Customer Entity whose primary keys are Customer id and status (which says authorized customer or un authorized customer). I have one more entity mapped to same table CustomerLight which will load only some specific fields of the customer which contains the where clause which specifies to load only authorized customer. There are some more entities which are mapped to customer entity with key-many-to-one relationship. After loading of the mapping file while validation of foriegn key constraints its failing Foreign key constraint failed "must have same number of columns as the referenced primary key" This is happening only in some environments not all. -- 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

14 years

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2010