September 2012 - hibernate-issues

[Hibernate-JIRA] (HHH-7532) SQLGrammarException generating Id's with DB2400Dialect

by Nelson Rodrigues (JIRA)

11 years, 8 months

2
5
0 / 0

[Hibernate-JIRA] (HHH-7524) Enabling AvailableSettings.ENABLE_LAZY_LOAD_NO_TRANS results in leaking DB-connections

by Andreas Joseph Krogh (JIRA)

11 years, 8 months

4
24
0 / 0

[Hibernate-JIRA] Created: (HHH-4751) Fix for @embeddedid error: Type not supported: org.hibernate.type.ManyToOneType

by David Coleman (JIRA)

Fix for @embeddedid error: Type not supported: org.hibernate.type.ManyToOneType -------------------------------------------------------------------------------- Key: HHH-4751 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4751 Project: Hibernate Core Issue Type: Improvement Components: envers Reporter: David Coleman Priority: Minor Attachments: IDMetadataGenerator_patch.txt Hi, After creating hibernate entities from the legacy database with envers hibernate tool, I noticed the following error occurred on creating an audit tables that has an @EmbeddedId attribute (related to ENVERS-76]: Caused by: org.hibernate.MappingException: Type not supported: org.hibernate.type.ManyToOneType .. I found out by looking at the source that the reason it failed was that the property type was not an instance of ImmutableType (not mutable); which was true as the embedded id was a combination of an int and a mutable java data object. I switched the mutable java date object to a immutable joda datetime object using the joda date time hibernate user type to fix the immutable problem. I also patched IdMetadataGenerator locally to the one attached as hibernate usertypes do not implement the ImmutableType interface; using the method 'isMutable()' should be suffice. Let me know if this is okay so I can submit the patch. -- 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

11 years, 8 months

7
29
0 / 0

[Hibernate-JIRA] Created: (HHH-7115) Allow types to have access to target usage data

by Michael Nascimento Santos (JIRA)

Allow types to have access to target usage data ----------------------------------------------- Key: HHH-7115 URL: https://hibernate.onjira.com/browse/HHH-7115 Project: Hibernate ORM Issue Type: Improvement Components: core Affects Versions: 4.1.0 Environment: hibernate-core:4.1.0.Final Reporter: Michael Nascimento Santos In order to being able to support a type hierarchy without having to write a Type per class, access to the actual target property type is needed. This has been hardcoded in org.hibernate.cfg.annotations.SimpleValueBinder for some Hibernate types, such as org.hibernate.type.EnumType and org.hibernate.type.SerializableToBlobType. Even for the same scenarios above, if one is trying to write his own type for enums or serializables, he has to end up writing a type per target class since the same facility is not provided by Hibernate in a general fashion. Hence, Hibernate should provide a set of standard properties for type implementations that need actual target usage data. Since some types might use the same property names used by EnumType with a different meaning, injecting these properties for any ParameterizedType might break existing types. Therefore, a ParameterizedType subinterface which also declares the standard property names for this case seems a better design choice. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-7300) TypeDefs won't be found depending of files read-order

by Stefan Schulze (JIRA)

TypeDefs won't be found depending of files read-order ----------------------------------------------------- Key: HHH-7300 URL: https://hibernate.onjira.com/browse/HHH-7300 Project: Hibernate ORM Issue Type: Bug Components: metamodel Affects Versions: 4.1.3, 3.6.10, 4.0.1 Reporter: Stefan Schulze If the Configuration first load (i.e. addResource or addDirectory or similar) an entity-mapping and after that a type, which is used by the entity, the call to buildSessionFactory() fails: > org.hibernate.MappingException: Could not determine type for: testenumtype, at table: TestTable, for columns: [org.hibernate.mapping.Column(ENUM)] > at org.hibernate.mapping.SimpleValue.getType(SimpleValue.java:305) > at org.hibernate.mapping.SimpleValue.isValid(SimpleValue.java:289) > at org.hibernate.mapping.Property.isValid(Property.java:238) > at org.hibernate.mapping.PersistentClass.validate(PersistentClass.java:468) > at org.hibernate.mapping.RootClass.validate(RootClass.java:270) > at org.hibernate.cfg.Configuration.validate(Configuration.java:1294) > at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1736) > at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1782) > at de.ckc.sschulze.hibernate.testcase.MyTest.testFirstEntityThenType(MyTest.java:37) In the secondPassCompile the mappings are processed in the order of addition to the Configuration (in case of addDirectory, addJar and addPackage this is quite random). This can cause the HbmBinder not to find the typedef used in an entity, because the typedef is processed after the entity, so the SimpleValue-type is set to the typename in the entity-mapping instead to the name of the type-class. During validation, the TypeResolver is not able to resolve this typename (because it's no basic type and no classname), so a MappingException is thrown. I think this issue could be solved by registering a new SecondPass in HbmBinder if no typedef could be found and the type is not a basictype, which resolves this unresolved type. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
4
0 / 0

[Hibernate-JIRA] (HHH-7543) EnversPostUpdateEventListenerImpl causes a NullPointerException due to the fact that the "oldstate" is null

by Nils Probson (JIRA)

11 years, 8 months

3
12
0 / 0

[Hibernate-JIRA] (HHH-7560) ehcache unit test intermittently failing (UnknownServiceException)

by Brett Meyer (JIRA)

11 years, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5188) Use provided enum type ordinal/string when reading

by Stefan Larsson (JIRA)

Use provided enum type ordinal/string when reading -------------------------------------------------- Key: HHH-5188 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5188 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1, 3.5.0-CR-2 Reporter: Stefan Larsson Priority: Minor Attachments: EnumType.java-typeSafeNullSafeGet.patch When Hibernate reads a PostgreSQL enum type using ResultSet.getObject(), the JDBC driver returns a driver-specific PGObject object, which preserves both the value of the enum and its type ordinal/string. Hibernate fails with a ClassCastException when it attempts to cast the PGObject into a String in org.hibernate.type.EnumType.nullSafeGet(). The code in org.hibernate.type.EnumType assumes that ResultSet.getObject() will either return a Number or a String, which is not true for the PostgreSQL driver. IMHO it would be better to let the JDBC driver do the conversion using ResultSet.getInt() or getString() instead. The attached patch allows JBoss AS 6 M3 (Hibernate 3.5.0-CR-2) to read PostgreSQL enums, using JPA, with a a Java enum annotated as @javax.persistence.Enumerated(javax.persistence.EnumType.STRING). Also, I believe that perhaps ignoring the given enum type causes Issue HHH-4230, where an ordinal enum was stored in character field. ResultSet.getInteger() might work for that one depending on the JDBC driver. -- 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

11 years, 8 months

5
18
0 / 0

[Hibernate-JIRA] (HHH-7567) Better checking when @Enumerated involved

by Steve Ebersole (JIRA)

11 years, 8 months

2
2
0 / 0

[Hibernate-JIRA] (HHH-7566) Activating fetch profile with mode=JOIN in hierarchical entity causes StackOverflowError because of endless loop

by Sebastian Götz (JIRA)

11 years, 8 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2012