August 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3341) org.hibernate.StaleObjectStateException always logged on the error level in the org.hibernate.event.def.AbstractFlushingEventListener.java class

by Krzysztof Hycnar (JIRA)

org.hibernate.StaleObjectStateException always logged on the error level in the org.hibernate.event.def.AbstractFlushingEventListener.java class ------------------------------------------------------------------------------------------------------------------------------------------------ Key: HHH-3341 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3341 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.5, Oracle 10g Reporter: Krzysztof Hycnar Priority: Minor Detailed description of the problem and possible consequences can be found here -> http://forum.hibernate.org/viewtopic.php?p=2387696 -- 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

16 years, 4 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HV-63) Missing pom.xml dependency for hibernate-commons-annotations

by Allen Parslow (JIRA)

Missing pom.xml dependency for hibernate-commons-annotations ------------------------------------------------------------ Key: HV-63 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-63 Project: Hibernate Validator Issue Type: Bug Affects Versions: 3.0.0.ga Environment: Maven2 Repo: http://repo1.maven.org/maven2/org/hibernate/hibernate-validator/3.0.0.ga/ Reporter: Allen Parslow Priority: Minor In the Maven2 Repo (http://repo1.maven.org/maven2/org/hibernate/hibernate-validator/3.0.0.ga/), the pom.xml does not include the required dependency for hibernate-commons-annotations. -- 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

16 years, 4 months

2
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-1936) IdentityGenerator doesn't support BigInteger as a valid identity type.

by Guenther Enthaler (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1936?page=c... ] Guenther Enthaler commented on HHH-1936: ---------------------------------------- I'd like to add BigInteger as an allowed type: ... else if ( clazz == java.math.BigDecimal.class ) { return rs.getBigDecimal( 1 ); } else if (clazz == BigInteger.class) { return rs.getBigDecimal(1).toBigIntegerExact(); } else { throw new IdentifierGenerationException( "this id generator generates long, integer, short, biginteger, bigdecimal or string" ); } Likewise, this is working for us... > IdentityGenerator doesn't support BigInteger as a valid identity type. > ---------------------------------------------------------------------- > > Key: HHH-1936 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1936 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.0.5 > Environment: Hibernate 3.0.5, Sybase 12.05, Window/ Unix > Reporter: Leonid Shtivelman > > Identity generator strategy doesn't support BigInteger as a valid id type. This causes problem with Sybase which requires identity column to be numeric. It would seem an obvious way to get around this problem is to set column mapping to long in hibernate xml and the actual java object. This will solve obvious problem of creating identity, but will cause performance problem on selection. In order for Sybase to use index for parameter query the variable type of the parameter and column index type has to be the same. If ones maps column type to Long, Hibernate will use JDBC method setLong(long) to set value in the prepared statement. This will cause mismatch between parameter type and column index type, and Sybase will not use index to locate index. As you can see this is a big problem for anyone that is using identity columns Sybase and Hibernate -- 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

16 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-35) Add a "trim" attribute to @NotEmpty

by Mike Youngstrom (JIRA)

Add a "trim" attribute to @NotEmpty ----------------------------------- Key: HV-35 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-35 Project: Hibernate Validator Issue Type: New Feature Affects Versions: 3.0.0.ga Reporter: Mike Youngstrom Frequently where an empty string is invalid so would " " be invalid. I think trim attribute added to @NotEmpty(trim=true) would be a simple and useful addition. -- 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

16 years, 4 months

7
12
0 / 0

[Hibernate-JIRA] Created: (HHH-3437) re-add incorrectly removed public getSource() methods on events

by Steve Ebersole (JIRA)

re-add incorrectly removed public getSource() methods on events --------------------------------------------------------------- Key: HHH-3437 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3437 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.3.0.GA Reporter: Steve Ebersole Assignee: Steve Ebersole Priority: Blocker Application of HHH-2926 incorrectly removed the public getSource() methods. We need to add those back as they are part of a public API and as such should never have been removed. -- 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

16 years, 4 months

1
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-1936) IdentityGenerator doesn't support BigInteger as a valid identity type.

by Dejan Predovic (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1936?page=c... ] Dejan Predovic commented on HHH-1936: ------------------------------------- This issue is still open for both 3.2 and 3.3 branches. We patched it by simply adding BigDecimal as an allowed type: public static Serializable get(ResultSet rs, Type type) throws SQLException, IdentifierGenerationException { Class clazz = type.getReturnedClass(); if ( clazz == Long.class ) { return new Long( rs.getLong( 1 ) ); } else if ( clazz == Integer.class ) { return new Integer( rs.getInt( 1 ) ); } else if ( clazz == Short.class ) { return new Short( rs.getShort( 1 ) ); } else if ( clazz == String.class ) { return rs.getString( 1 ); } else if ( clazz == java.math.BigDecimal.class ) { return rs.getBigDecimal( 1 ); } else { throw new IdentifierGenerationException( "this id generator generates long, integer, short, bigdecimal or string" ); } } and it works, we see no side effects. It would be nice if this could find it's way into the trunk. > IdentityGenerator doesn't support BigInteger as a valid identity type. > ---------------------------------------------------------------------- > > Key: HHH-1936 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1936 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.0.5 > Environment: Hibernate 3.0.5, Sybase 12.05, Window/ Unix > Reporter: Leonid Shtivelman > > Identity generator strategy doesn't support BigInteger as a valid id type. This causes problem with Sybase which requires identity column to be numeric. It would seem an obvious way to get around this problem is to set column mapping to long in hibernate xml and the actual java object. This will solve obvious problem of creating identity, but will cause performance problem on selection. In order for Sybase to use index for parameter query the variable type of the parameter and column index type has to be the same. If ones maps column type to Long, Hibernate will use JDBC method setLong(long) to set value in the prepared statement. This will cause mismatch between parameter type and column index type, and Sybase will not use index to locate index. As you can see this is a big problem for anyone that is using identity columns Sybase and Hibernate -- 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

16 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3436) Second-level cache is not evicted on failure of update

by Fol De Rol (JIRA)

Second-level cache is not evicted on failure of update ------------------------------------------------------ Key: HHH-3436 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3436 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.3.0.GA Reporter: Fol De Rol Using cluster-wide TreeCache as a 2nd-level cache provider for Hibernate, I have noticed that in case of failure of update operation, e.g. in case of constraint violation, the object with inconsistent data is still persisted in the second-level cache. So, the forthcoming load() perfromed in a separate session/transaction returns the erroneous object from the cache instead of the actual state from the DB. -- 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

16 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2934) ScrollableResults.get(int column) returns only the first character of a database column type char(10)

by Samir Jyoti (JIRA)

ScrollableResults.get(int column) returns only the first character of a database column type char(10) ----------------------------------------------------------------------------------------------------- Key: HHH-2934 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2934 Project: Hibernate3 Issue Type: Bug Components: query-sql Affects Versions: 3.2.4.sp1 Environment: IBM DB2 8.1.7, Reporter: Samir Jyoti ScrollableResults.get(int column) returns only the first character of a database column type char(n) where n> 1 (say 10 or 18). So if your column has value 'SIMPSON ' , it only returns 'S'. Had to warp the column with a DB2 SQL "VARCHAR" function to convert it into a String. -- 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

16 years, 5 months

5
5
0 / 0

[Hibernate-JIRA] Created: (HV-53) AssertTrue and AssertFalse not compatible with null values

by benoit heinrich (JIRA)

AssertTrue and AssertFalse not compatible with null values ---------------------------------------------------------- Key: HV-53 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-53 Project: Hibernate Validator Issue Type: Bug Components: validators Affects Versions: 3.0.0.ga Reporter: benoit heinrich The AssertTrue and AssertFalse validators do not work with null values, they actually generate a NullPointerException. The code fix for this should be: public class AssertFalseValidator implements Validator<AssertFalse>, Serializable { public boolean isValid(Object value) { if (value == null) return true; << this is the fix return !(Boolean) value; } public void initialize(AssertFalse parameters) { } } public class AssertTrueValidator implements Validator<AssertTrue>, Serializable { public boolean isValid(Object value) { if (value == null) return true; << this is the fix return (Boolean) value; } public void initialize(AssertTrue parameters) { } } Cheers, /Benoit -- 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

16 years, 5 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HBX-1072) hbm2java generates bad code for BigDecimal in equals() (Remains after HBX-426)

by Arnaud Renouf (JIRA)

hbm2java generates bad code for BigDecimal in equals() (Remains after HBX-426) ------------------------------------------------------------------------------ Key: HBX-1072 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1072 Project: Hibernate Tools Issue Type: Bug Components: hbm2java Affects Versions: 3.2.1 Environment: Hibernate 3, Postgres Reporter: Arnaud Renouf Even with the correction in HBX-426, the bug is still there. In BasicPOJOClass.java in method useCompareTo(String javaTypeName), the javaTypeName is not the complete type name (with packages). So the test "java.math.BigDecimal".equals(javaTypeName) always returns false and the BigDecimal.compareTo method is never used in the generated equals 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

16 years, 5 months

2
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2008