September 2012 - hibernate-issues

[Hibernate-JIRA] (HHH-7581) Javassist cannot load classes (undeterministic behaviour)

by Antal Kiss (JIRA)

11 years, 8 months

1
1
0 / 0

[Hibernate-JIRA] (HHH-7564) equals method in proxy should check reference equality first

by Rice Yeh (JIRA)

11 years, 8 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5841) Invalid table creation in Annotations Test Cases

by Fred Toussi (JIRA)

Invalid table creation in Annotations Test Cases ------------------------------------------------ Key: HHH-5841 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5841 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.6.next Environment: Tested with HSQLDB 2.0.1 Reporter: Fred Toussi Some tests create a table with the definition like the one below. As Standard SQL does not allow two unique constraints (or one unique and one PK) on the same column(s) the table definition fails, resulting in test failure. 23:41:40,437 DEBUG SchemaExport:415 - create table MedicalHistory ( lastupdate date, FK varchar(255) not null, primary key (FK), unique (FK) ) The pattern of failure shows in several tests. For example: package org.hibernate.test.annotations.derivedidentities.e4.a; DerivedIdentitySimpleParentSimpleDepTest To reproduce, use an up-to-date HSQLDB 2.0.1 RC from http://hsqldb.org (I have not checked with 2.0.0, as this version has been superseded) -- 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

3
2
0 / 0

[Hibernate-JIRA] (HHH-7576) Hibernate Developer Guide contains invalid reference in Optional configuration properties section

by David Grant (JIRA)

11 years, 8 months

1
0
0 / 0

[Hibernate-JIRA] (HHH-7575) Hibernate Getting Started Guide refers to incorrect tutorial directory for annotations tutoral

by David Grant (JIRA)

11 years, 8 months

2
3
0 / 0

[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

11 years, 8 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

11 years, 8 months

2
12
0 / 0

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

by Elizabeth Chatman (JIRA)

11 years, 8 months

4
12
0 / 0

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

by John Hardin (JIRA)

11 years, 8 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

11 years, 8 months

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