April 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-6173) Implement embedded entities (component) mapping via annotation

by Hardy Ferentschik (JIRA)

Implement embedded entities (component) mapping via annotation -------------------------------------------------------------- Key: HHH-6173 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6173 Project: Hibernate Core Issue Type: Sub-task Reporter: 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

14 years, 9 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5771) PersistentBag.remove() and removeAll() load the whole collection

by Dobes Vandermeer (JIRA)

PersistentBag.remove() and removeAll() load the whole collection ---------------------------------------------------------------- Key: HHH-5771 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5771 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.5 Reporter: Dobes Vandermeer When removing an entity from the database, it is a requirement in hibernate that you remove the entity from any persistent collections it is in so that you don't get errors about transient objects being referenced by a collection. However, calling remove() on a persistent collection seems to load the whole collection into memory. The use of very large (too big to load all at once) lazy collections is apparently not well supported in hibernate because it is difficult to use them without loading the whole collection into memory rather than load it incrementally. Nevertheless, it is possible to request subsets of collections and having the ability to remove() without loading the lazy collection would be a bonus for those of us who do use large lazy collections that way. Here is the offending code: {code} public boolean remove(Object o) { initialize( true ); if ( bag.remove( o ) ) { dirty(); return true; } else { return false; } } {/code} -- 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

14 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (OGM-35) Implement JPA IDENTITY generated value strategy for a grid

by Emmanuel Bernard (JIRA)

Implement JPA IDENTITY generated value strategy for a grid ---------------------------------------------------------- Key: OGM-35 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-35 Project: Hibernate OGM Issue Type: New Feature Reporter: Emmanuel Bernard -- 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

14 years, 9 months

1
4
0 / 0

[Hibernate-JIRA] Created: (OGM-34) Implement JPA AUTO generated value strategy for a grid

by Emmanuel Bernard (JIRA)

Implement JPA AUTO generated value strategy for a grid ------------------------------------------------------ Key: OGM-34 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-34 Project: Hibernate OGM Issue Type: New Feature Reporter: Emmanuel Bernard -- 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

14 years, 9 months

1
4
0 / 0

[Hibernate-JIRA] Created: (OGM-33) Implement JPA SEQUENCE generated value strategy for a grid

by Emmanuel Bernard (JIRA)

Implement JPA SEQUENCE generated value strategy for a grid ---------------------------------------------------------- Key: OGM-33 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-33 Project: Hibernate OGM Issue Type: New Feature Reporter: Emmanuel Bernard -- 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

14 years, 9 months

1
4
0 / 0

[Hibernate-JIRA] Created: (HHH-6024) NPE in CastFunction when casting a field named "date" to type "date" in HQL

by Jon Mann (JIRA)

NPE in CastFunction when casting a field named "date" to type "date" in HQL --------------------------------------------------------------------------- Key: HHH-6024 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6024 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.2 Environment: Hibernate 3.6.0.Final and 3.6.2.Final MySQL 5.0 Reporter: Jon Mann Attachments: hibernate-cast-date.zip In Hibernate version "3.6.2.Final" when casting a field named "date" to type "date": SELECT entity FROM DateEntity AS entity WHERE CAST(entity.date AS date) = ? we encounter a NullPointerException in CastFunction: java.lang.NullPointerException at org.hibernate.dialect.function.CastFunction.render(CastFunction.java:56) at org.hibernate.hql.ast.SqlGenerator.endFunctionTemplate(SqlGenerator.java:214) at org.hibernate.hql.antlr.SqlGeneratorBase.methodCall(SqlGeneratorBase.java:2325) ... If we rename the field "date" to "creationDate", the problem dissapears. If we cast to "time" instead of "date", the problem dissapears. We encountered this problem while using Hibernate version "3.6.0.Final" against MySQL 5.0. Upgrading to Hibernate version "3.6.2.Final" did not resolve the problem. We guess this problem is a bug in the Hibernate HQL parsing code. It might be a problem with our usage of Hibernate, in which case it would be helpful for Hibernate to return a useful error message. Please find attached a minimal Maven test case (using HSQL memory DB) which demonstrates the problem. The following JIRA issue maybe related to this problem: HHH-3770 - NPE in o.h.dialect.function.CastFunction Credit to my colleague Sergey Shinkevich for creating the test case. Thanks to the Hibernate team for a great product. -- 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

14 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6012) HSQLDialect support for ROWNUM

by Ondrej Medek (JIRA)

HSQLDialect support for ROWNUM ------------------------------ Key: HHH-6012 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6012 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.6.0.CR2, 3.6.0.CR1, 3.5.6, 3.6.0.Beta4, 3.6.0.Beta3, 3.5.5, 3.6.0.Beta2, 3.6.0.Beta1, 3.5.4, 3.5.3, 3.5.2, 3.5.1, 3.5.0-Final, 3.5.0-CR-2, 3.5.0-CR-1, 3.5.0-Beta-4, 3.5.0-Beta-3, 3.5.0-Beta-2, 3.5.0.Beta-1, 3.3.2, 3.3.1 Reporter: Ondrej Medek New HSQLDB has a support for Oracel compatibility by: SET DATABASE SQL SYNTAX ORA TRUE So, the HSQLDB knows ROWNUM. However, I cannot use it in @Formula. Please, add ROWNUM into the HSQLDialect in the same way, as it is in the Oracle9iDialect. E.g. add: // Oracle compatibility mode support - SET DATABASE SQL SYNTAX ORA TRUE registerFunction( "rownum", new NoArgSQLFunction("rownum", Hibernate.LONG, false) ); -- 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

14 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6122) HSQLDialect uses wrong trim() function when running HSQLDB v1.8

by Matthew Pies (JIRA)

HSQLDialect uses wrong trim() function when running HSQLDB v1.8 --------------------------------------------------------------- Key: HHH-6122 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6122 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.6.0 Environment: Maven: hibernate-core-3.6.0.Final.jar, hsqldb-1.8.0.10.jar Reporter: Matthew Pies The default dialect behavior assumes the TRIM function has the form "TRIM(?1 ?2 ?3 ?4)", whereas HSQLDB v1.8 specifies: "TRIM([{LEADING | TRAILING | BOTH}] FROM <string expression>)" (http://www.hsqldb.org/doc/1.8/guide/ch09.html#stored-section). Simply fixed in the HSQLDialect class constructor by overriding the function registered in the parent Dialect class: if ( hsqldbVersion < 20 ) { // maybe == 18? not sure best practice here... registerFunction("trim", new SQLFunctionTemplate(StandardBasicTypes.STRING, "trim(both from ?1)")); } Simple test case (assuming HSQLDialect + HSQL JDBC driver): sessionFactory.getCurrentSession().createQuery("from User where trim(email) = 'foo(a)bar.com'").list(); -- 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

14 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (OGM-19) Implement Referencable#getReference in OgmSessionFactory

by Emmanuel Bernard (JIRA)

Implement Referencable#getReference in OgmSessionFactory -------------------------------------------------------- Key: OGM-19 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-19 Project: Hibernate OGM Issue Type: New Feature Components: core Reporter: Emmanuel Bernard Priority: Trivial low priority -- 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

14 years, 9 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5671) Apply entity-mode information to the logical model

by Steve Ebersole (JIRA)

Apply entity-mode information to the logical model -------------------------------------------------- Key: HHH-5671 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5671 Project: Hibernate Core Issue Type: Sub-task Reporter: Steve Ebersole -- 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

14 years, 9 months

2
7
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 April 2011