July 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3007) Unchanged persistent set gets marked dirty on session.merge()

by Lars Koedderitzsch (JIRA)

Unchanged persistent set gets marked dirty on session.merge() ------------------------------------------------------------- Key: HHH-3007 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3007 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Reporter: Lars Koedderitzsch Persistent sets are marked dirty on session.merge() even if there have been no changes to the collection. This is especially painful when the collection is immutable and results in an "changed an immutable collection instance" exception on flush. I tracked the behaviour down a bit and believe the problem to be in CollectionType.replace(). Here the passed in orginal PersistentSet is replaced by a plain HashSet in this line: Object result = target == null || target == original ? instantiateResult( original ) : target; The "result" object (HashSet) is then passed to the CollectionType.replaceElements() method (instead of the original PersistentSet). In CollectionType.replaceElements() the code to clear the dirty state of the collection does not execute anymore, because the passed-in "original" collection is the described HashSet and *not* the original PersistentSet. This way the PersistentSet remains marked dirty. A workaround is to manually clear the dirty state of an immutable collection after merge but before flush. -- 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

15 years, 4 months

3
8
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

15 years, 4 months

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

15 years, 4 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3936) Provide Hibernate Dialect for MS SQL Server 2005

by Claudio (JIRA)

Provide Hibernate Dialect for MS SQL Server 2005 ------------------------------------------------ Key: HHH-3936 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3936 Project: Hibernate Core Issue Type: Task Environment: Hibernate 3.3.1 Reporter: Claudio Attachments: SQLServer2005Dialect.java Hibernate should support a dialect for MS SQL Server 2005. There are some particularities comparing to SQL Server 2000 (SQL Limit strategy for example). Find the dialect attached. Test Case must be created for it. -- 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

15 years, 4 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-307) Implement clustering with JBoss Cache

by Hardy Ferentschik (JIRA)

Implement clustering with JBoss Cache ------------------------------------- Key: HSEARCH-307 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-307 Project: Hibernate Search Issue Type: New Feature Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik -- 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

15 years, 4 months

4
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2716) Session.replicate failure with identity column

by Yves Martin (JIRA)

Session.replicate failure with identity column ---------------------------------------------- Key: HHH-2716 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2716 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.2 Environment: Java 1.5, MySQL 5.0.27 and Hibernate Annotations 3.2.1.GA Reporter: Yves Martin I'm trying to use replicate: http://www.hibernate.org/hib_docs/reference/en/html/objectstate.html#obje... The column "@version" is replicated properly (same value in second db) but the column "@Id @GeneratedValue" contains a new value from the db2 sequence. In fact the insert statement generated by the replicate method does not include the "id" column. -- 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

15 years, 4 months

6
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3081) SQL queries do not currently support iteration

by MG (JIRA)

SQL queries do not currently support iteration ---------------------------------------------- Key: HHH-3081 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3081 Project: Hibernate3 Issue Type: Bug Reporter: MG Query sqlQuery = session.createSQLQuery("select * from TRADE").addEntity(Trade.class); sqlQuery.setReadOnly(true); sqlQuery.setCacheMode(CacheMode.IGNORE); sqlQuery.setCacheable(false); sqlQuery.setFetchSize(1000); Iterator<Trade> trades = sqlQuery.iterate(); Causes Exception in thread "main" java.lang.UnsupportedOperationException: SQL queries do not currently support iteration at org.hibernate.impl.SQLQueryImpl.iterate(SQLQueryImpl.java:190) -- 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

15 years, 4 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2315) relax schemaupdate complaining about numeric/decimal

by Max Rydahl Andersen (JIRA)

relax schemaupdate complaining about numeric/decimal ---------------------------------------------------- Key: HHH-2315 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2315 Project: Hibernate3 Type: Improvement Components: core Reporter: Max Rydahl Andersen Fix For: 3.2.2 http://jira.jboss.com/jira/browse/JBSEAM-596 -- 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

15 years, 4 months

5
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3356) Support for subselect (subquery) in from clause

by Geoffrey De Smet (JIRA)

Support for subselect (subquery) in from clause ----------------------------------------------- Key: HHH-3356 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3356 Project: Hibernate3 Issue Type: New Feature Components: query-hql Reporter: Geoffrey De Smet Many databases support subselects in the from clause, for example: http://dev.mysql.com/doc/refman/5.0/en/unnamed-views.html And it's very handy. Native query's are sometimes a working workaround, but have many disadvantages, unlike HQL. Btw, I've searched through jira for over 20 minutes and didn't find an issue for this already. If there is one already, please give it a better title or link it to this issue :) -- 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

15 years, 4 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HV-68) Consider reponening (see new patch)

by Lucien Weller (JIRA)

Consider reponening (see new patch) ----------------------------------- Key: HV-68 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-68 Project: Hibernate Validator Issue Type: Sub-task Reporter: Lucien Weller -- 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

15 years, 5 months

4
6
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 July 2009