August 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-6759) Null properties mapped as boolean cause exception on Oracle

by Gail Badner (JIRA)

Null properties mapped as boolean cause exception on Oracle ----------------------------------------------------------- Key: HHH-6759 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6759 Project: Hibernate Core Issue Type: Bug Components: core Reporter: Gail Badner Assignee: Gail Badner Fix For: 4.0.0.next When PreparedStatement.setNull(index, java.sql.BOOLEAN) is called using Oracle, this exception is thrown: java.sql.SQLException: Invalid column type: 16 Types.BOOLEAN is defined as 16. The fix is to use Types.BIT instead of Types.BOOLEAN. This is done by overriding Dialect.getSqlTypeDescriptorOverride(int sqlCode) in Orcle8iDialect to return BitTypeDescriptor when sqlCode is Types.BOOLEAN. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-1017) Implement variable score on spatial queries

by Emmanuel Bernard (JIRA)

Implement variable score on spatial queries ------------------------------------------- Key: HSEARCH-1017 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-1017 Project: Hibernate Search Issue Type: New Feature Components: spatial Reporter: Emmanuel Bernard Assignee: Nicolas Helleringer Note that we can launch without this feature initially. That's why it's not a subtask of HSEARCH-923 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
12
0 / 0

[Hibernate-JIRA] (HHH-7557) Map entries get deleted

by Elizabeth Chatman (JIRA)

12 years, 4 months

4
12
0 / 0

[Hibernate-JIRA] (HHH-7398) Transaction timeouts are not properly enforced

by John Hardin (JIRA)

12 years, 4 months

3
17
0 / 0

[Hibernate-JIRA] Created: (HHH-7059) The DerbyDialect deprecation warning should appear no more, when using one of the version-specific dialects

by Guenther Demetz (JIRA)

The DerbyDialect deprecation warning should appear no more, when using one of the version-specific dialects ------------------------------------------------------------------------------------------------------------ Key: HHH-7059 URL: https://hibernate.onjira.com/browse/HHH-7059 Project: Hibernate ORM Issue Type: Improvement Components: core Affects Versions: 4.1.0, 4.0.1 Reporter: Guenther Demetz Priority: Minor Althoug setting a version=specific derby dialect config.setProperty("hibernate.dialect","org.hibernate.dialect.DerbyTenSevenDialect"); following warning log appears: @LogMessage(level = WARN) @Message(value = "The DerbyDialect dialect has been deprecated; use one of the version-specific dialects instead", id = 430) This is because currently all versioned DerbyDialects are extending from deprecated super class DerbyDialect and the constructor of the super class does produce this warning logging regardsless of which concrete type the dialect is. public DerbyDialect() { super(); LOG.deprecatedDerbyDialect(); ... } Please see also: https://forum.hibernate.org/viewtopic.php?t=1014416 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
3
0 / 0

[Hibernate-JIRA] (HHH-7518) NPE when registering EhCache JMX mbeans

by Mateus Pimenta (JIRA)

12 years, 4 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-7134) Detection of wrong circularity when two tables with same name in different schemas

by Didier Villevalois (JIRA)

Detection of wrong circularity when two tables with same name in different schemas ---------------------------------------------------------------------------------- Key: HHH-7134 URL: https://hibernate.onjira.com/browse/HHH-7134 Project: Hibernate ORM Issue Type: Bug Components: core Affects Versions: 4.1.0 Environment: Hibernate 4.1.0.Release, any database Reporter: Didier Villevalois Priority: Blocker Attachments: 0001-Fix-FKSecondPass-processing-to-take-catalog-and-sche.patch, jpa-test-fkcircularity.zip There is a problem when two related (in terms of joins) classes have the same name in different schemas. Attached is a test maven project (run "mvn package" to run the tests) and a fix patch for hibernate-core (based on bc643ddb7cc28db05a7168673746dbf3edee6cf7). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-7212) [Envers] Avoid useless temporary session in Tools.getTargetFromProxy()

by Fabien Le Bars (JIRA)

[Envers] Avoid useless temporary session in Tools.getTargetFromProxy() ---------------------------------------------------------------------- Key: HHH-7212 URL: https://hibernate.onjira.com/browse/HHH-7212 Project: Hibernate ORM Issue Type: Improvement Components: envers Affects Versions: 4.1.1 Environment: Hibernate 4.1.1.Final H2 1.3.165 Reporter: Fabien Le Bars Priority: Trivial The method from Tools class : public static Object getTargetFromProxy(SessionFactoryImplementor sessionFactoryImplementor, HibernateProxy proxy); uses a temporary session when the proxy is not initialized. In some cases though, the proxy.getSession() is not null and calling directly proxy.getHibernateLazyInitializer().getImplementation() will return an initialized object even though it was uninitialized right before the call. Thus changing the following lines if (!proxy.getHibernateLazyInitializer().isUninitialized()) { return proxy.getHibernateLazyInitializer().getImplementation(); } into: if (!proxy.getHibernateLazyInitializer().isUninitialized() || proxy.getHibernateLazyInitializer().getSession() != null) { return proxy.getHibernateLazyInitializer().getImplementation(); } avoids useless uses of the temporary session. The reason I had to made this minor change is that H2 does not handle well temporary sessions when using in-memory database with the initializing script direcly passed in the url (when the temporary session is opening a new connection, it attemps to recreate the whole database and miserably fails). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-7203) IdentityGenerator fails with JOINED Inheritance when inserting entity to PosgtreSQL

by Andrey Vlasov (JIRA)

IdentityGenerator fails with JOINED Inheritance when inserting entity to PosgtreSQL ----------------------------------------------------------------------------------- Key: HHH-7203 URL: https://hibernate.onjira.com/browse/HHH-7203 Project: Hibernate ORM Issue Type: Bug Components: core Affects Versions: 3.6.10 Environment: Hibernate 3.6.10, PostgreSQL 9.1-901.jdbc4 Reporter: Andrey Vlasov We have inheritance strategy JOIN in table. Now we want to insert some entity inheriting from this one, and we want PostgreSQL to automatically generate the ID for the new entity. Hibernate runs IdentityGenerator.GetGeneratedKeysDelegate.executeAndExtract(), which uses "persister.getIdentifierColumnNames()[0]" as identifierColumnName (in Hibernate 3.6.10 it's line 99 in IdentityGenerator) to getGeneratedIdentity. This identifierColumnName points actually to the child entity identifierColumn. So, this inserting to the parent table fails on getting identifier by wrong column name (a column from the child entity). This issue is a result of HHH-6580 changes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
6
0 / 0

[Hibernate-JIRA] (HHH-7545) Aliases for a collection key and element column can collide causing one to be excluded

by Gail Badner (JIRA)

12 years, 4 months

2
3
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 2012