August 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (METAGEN-29) Embedded generic types not supported by metamodel generator

by Adrian Hummel (JIRA)

Embedded generic types not supported by metamodel generator ----------------------------------------------------------- Key: METAGEN-29 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-29 Project: Hibernate Metamodel Generator Issue Type: Bug Components: processor Affects Versions: 1.0.0-CR-1 Environment: Hibernate 3.5.0-CR-2 Reporter: Adrian Hummel Assignee: Hardy Ferentschik Priority: Critical Attachments: bugreport.zip Scenario: I have a @MappedSuperclass defining an abstract entity. This class has a technical primary key and a business identity. The business identity is realized by means of a generic embeddable (e.g. for a Customer class there is a corresponding CustomerId class for its business identity). The JPAMetaModelEntityProcessor does generate the AbstractEntity_ class but does only include the primary key field but omits the generic field for the business identity (which leads to subsequent errors when accessing this field using a CriteriaBuilder). Attached a mini project with a test case which illustrates the problem. -- 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

4
8
0 / 0

[Hibernate-JIRA] Created: (HHH-4539) Make UPPER and LOWER work on MS SQL Server text and ntext columns

by Sergiu Dumitriu (JIRA)

Make UPPER and LOWER work on MS SQL Server text and ntext columns ----------------------------------------------------------------- Key: HHH-4539 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4539 Project: Hibernate Core Issue Type: Improvement Components: query-sql Affects Versions: 3.3.2 Environment: MS SQL Server Reporter: Sergiu Dumitriu Trying to use UPPER or LOWER on a text column results in: ERROR util.JDBCExceptionReporter - Argument data type text is invalid for argument 1 of upper function. http://databases.aspfaq.com/database/why-do-i-get-argument-data-type-text... suggests a workaround, which I think should be automatically used by Hibernate, so that the HQL query can work with other dialects. -- 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, 10 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3965) Expose the ability to use varchar(max) or nvarchar(max)

by Ido Ran (JIRA)

Expose the ability to use varchar(max) or nvarchar(max) ------------------------------------------------------- Key: HHH-3965 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3965 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate 3.4.0GA as provider for JPA 1.0 - SQL Server 2005 Database Reporter: Ido Ran Priority: Blocker I have an entity which needs to store long text field (at least 30,000 characters). I use SQL Server 2005 as back-end database. SQL Server varchar support up-to 8,000 characters in length of a field, or the reserved word MAX which indicate that the field length will be 2^31-1. I think that the class SQLServerDialect should be changed to have the following line in it's ctor: registerColumnType( Types.VARCHAR, 8001, "varchar(MAX)" ); this way, all String fields with length above 8000 will have varchar(MAX) as column type. -- 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, 10 months

5
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-517) ThreadLocal in ContextHolder causes memory leak when deployed in a web container

by Vojtěch Krása (JIRA)

ThreadLocal in ContextHolder causes memory leak when deployed in a web container -------------------------------------------------------------------------------- Key: HSEARCH-517 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-517 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.2.0.CR1, 3.2.0.Beta1, 3.1.1.GA, 3.1.0.GA, 3.1.0.CR1, 3.1.0.Beta2, 3.1.0.Beta1, 3.0.1.GA, 3.0.0.GA Environment: Hibernate 3.4.0.GA/3.5.1-Final, Tomcat 6.0.26, Spring 2.5.6/3.0.1, Sun JDK 1.6; Hibernate 3.3.1.GA Tomcat 6.0.18 Spring 2.5.6 Java OpenJDK 1.6 Reporter: Vojtěch Krása Priority: Critical Attachments: dump.zip, testCase.zip The SearchFactory has a static ThreadLocal variables which holds a reference to the SearchFactoryImpl. The ThreadLocal is not cleared when the application is undeployed, causing a memory leak. http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-314 -- 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, 10 months

4
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5403) Update to hsqldb 2.0.0 for testing

by Gail Badner (JIRA)

Update to hsqldb 2.0.0 for testing ---------------------------------- Key: HHH-5403 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5403 Project: Hibernate Core Issue Type: Bug Reporter: Gail Badner Fix For: 3.5.x, 3.6.x When 2.0.0 is available from the JBoss Nexus repo, parent/pom.xml should be updated in Branch_3_5 and trunk so testing is done using 2.0.0. -- 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, 10 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5492) PostInsertListener doing new insert works on Mysql/HSQLDB, but not on Oracle.

by Barry (JIRA)

PostInsertListener doing new insert works on Mysql/HSQLDB, but not on Oracle. ----------------------------------------------------------------------------- Key: HHH-5492 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5492 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.4 Environment: Oracle Database 10g Express Edition Release 10.2.0.1.0 and Oracle Database 11g Release 11.1.0.0.0 Reporter: Barry Attachments: EventListener-test.zip I'm trying to implement a hibernate event listener that inserts a new record every time a specific entity is updated, deleted or inserted. I've implemented a listener for post-insert, post-update, post-delete. Its a requirement that the new record is inserted in the same transaction as the one that originally triggered the update/deletion/insert. The relevant section of my listener looks like this (similar for postInsert & postDelete): {code} public void onPostUpdate(PostUpdateEvent event) { if (isAuditable(event.getEntity())) { saveAuditRecord(event.getSession()); } } private boolean isAuditable(Object entity) { return entity instanceof SomeEntity; } private void saveAuditRecord(Session session) { AuditRecord record = new AuditRecord(); record.setId(Double.doubleToLongBits(Math.random())); session.save(record); } {code} The listener is triggered for each event, but it seems as though the AuditRecord is not saved when using an Oracle database. Using MySQL or HSQLDB works fine. So my guess is that it has something to do with the Oracle dialect? I've attached a test case which demonstrates it failing (but you will need to connect to an Oracle DB :-)) Same result for Oracle XE and the full monty. -- 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, 10 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3527) Null Version Comparator for versioned class due to reuse of Second Level CacheDataDescriptionImpl

by Paul FitzPatrick (JIRA)

Null Version Comparator for versioned class due to reuse of Second Level CacheDataDescriptionImpl ------------------------------------------------------------------------------------------------- Key: HHH-3527 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3527 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.3.1 Environment: 3.3.1 GA, Postgres 8.3.3, EH Cache Reporter: Paul FitzPatrick Priority: Minor When the SessionFactoryImpl constructor builds the EntityPersister for classes, it consults a cache of entityAccessStrategies for all the known second level cache regions. If only some of the classes in that region have version tags, then it is possible the cached EntityRegionAccessStrategy will be created without a Version Comparator. Subsequent calls to load an object using a Criteria query failed with a NullPointerException (stack trace below). The line being executed is "return version!=null && comparator.compare(version, newVersion) < 0;" and in this case "version" is an Integer object and comparator is null. Not sure the appropriate solution. It would seem from an examination of the code that if the EntityRegionAccessStrategy is to be shared, then all classes in the second level cache region _must_ either all have a "version" column or all have no "version" column. Further, it seems implied that if they use a "version" column, then they must all use the exact same data type. If this is the case, then a better error check on the configuration data may be in order. Caused by: java.lang.NullPointerException at org.hibernate.cache.ReadWriteCache$Item.isPuttable(ReadWriteCache.java:426) at org.hibernate.cache.ReadWriteCache.put(ReadWriteCache.java:180) at org.hibernate.cache.impl.bridge.EntityAccessStrategyAdapter.putFromLoad(EntityAccessStrategyAdapter.java:68) at org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:179) at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:877) at org.hibernate.loader.Loader.doQuery(Loader.java:752) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259) at org.hibernate.loader.Loader.doList(Loader.java:2228) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2125) at org.hibernate.loader.Loader.list(Loader.java:2120) at org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:118) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1596) at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:306) at org.hibernate.impl.CriteriaImpl.uniqueResult(CriteriaImpl.java:328) -- 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, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5202) polymorphism=PolymorphismType.EXPLICIT not work

by zhuzhangsuo (JIRA)

polymorphism=PolymorphismType.EXPLICIT not work ------------------------------------------------ Key: HHH-5202 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5202 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.5.1 Environment: hibernate3.5.1 mysql 5.1 Reporter: zhuzhangsuo Attachments: src.rar class Book ,Section is Inheritanced from EntityItem and use @Inheritance(strategy=InheritanceType.JOINED) I want to use @org.hibernate.annotations.Entity(dynamicUpdate=true,selectBeforeUpdate=true, polymorphism=PolymorphismType.EXPLICIT) to select the base table into EntityItem but not Book or Section The sql is : select entityitem0_.entity_id as entity1_0_, entityitem0_.entity_author as entity2_0_, entityitem0_.entity_category as entity3_0_, entityitem0_.entity_ctime as entity4_0_, entityitem0_.entity_desc as entity5_0_, entityitem0_.entity_folder as entity6_0_, entityitem0_.entity_keyword as entity7_0_, entityitem0_.entity_name as entity8_0_, entityitem0_.entity_operator as entity9_0_, entityitem0_.entity_order as entity10_0_, entityitem0_.entity_pid as entity18_0_, entityitem0_.entity_picture as entity11_0_, entityitem0_.entity_status as entity12_0_, entityitem0_.entity_tag as entity13_0_, entityitem0_.entity_template as entity14_0_, entityitem0_.entity_type as entity15_0_, entityitem0_.entity_update_time as entity16_0_, entityitem0_.entity_url as entity17_0_, entityitem0_1_.section_content as section1_1_, entityitem0_2_.book_continue as book1_2_, entityitem0_2_.book_copyright as book2_2_, entityitem0_2_.book_grade as book3_2_, entityitem0_2_.book_press as book4_2_, entityitem0_2_.book_price as book5_2_, entityitem0_2_.book_pv as book6_2_, entityitem0_2_.book_translate as book7_2_, case when entityitem0_1_.entity_id is not null then 1 when entityitem0_2_.entity_id is not null then 2 when entityitem0_.entity_id is not null then 0 end as clazz_ from book_entity entityitem0_ left outer join book_section_detail entityitem0_1_ on entityitem0_.entity_id=entityitem0_1_.entity_id left outer join book_detail entityitem0_2_ on entityitem0_.entity_id=entityitem0_2_.entity_id -- 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, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-433) Think about exposing not yet committed changes by opening IndexReaders off IndexWriters

by Emmanuel Bernard (JIRA)

Think about exposing not yet committed changes by opening IndexReaders off IndexWriters --------------------------------------------------------------------------------------- Key: HSEARCH-433 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-433 Project: Hibernate Search Issue Type: Sub-task Reporter: Emmanuel Bernard -- 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, 10 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-511) Clean up orphaned lock files on startup

by Marc Schipperheyn (JIRA)

Clean up orphaned lock files on startup --------------------------------------- Key: HSEARCH-511 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-511 Project: Hibernate Search Issue Type: Improvement Components: engine Affects Versions: 3.2.0.CR1 Reporter: Marc Schipperheyn I have had several occassions when the MassIndexer failed to complete for some reason and I had to restart Tomcat. MassIndexer creates lockfiles for the indexes it is updating. These lock files remain after a restart and block MassIndexer from running again. I suggest that Hibernate Search during startup checks for the existence of lock files in the index directory and removes then if they are there. This prevents an administrator from having to go and do it manually which is a bummer in production. -- 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, 10 months

3
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2010