June 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-6375) filter condition ignored by isEmpty() and size() on lazy PersistentBag

by Ken Jarrad (JIRA)

filter condition ignored by isEmpty() and size() on lazy PersistentBag ----------------------------------------------------------------------- Key: HHH-6375 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6375 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1 Environment: Hibernate 3.5.1 with Derby dialect Reporter: Ken Jarrad Priority: Minor Filter conditions are ignored by methods isEmpty() and size() on a lazy PersistentBag. More specifically, internal method readSize() ignores enabled filter conditions. The size returned is too large and subsequent attempts to access the collection throw ArrayIndexOutOfBoundsException. Methods such as Collections#binarySearch fail when applied to the lazy PersistentBag. -- 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

13 years

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6373) document property hibernate.jdbc.wrap_result_sets

by Strong Liu (JIRA)

document property hibernate.jdbc.wrap_result_sets ------------------------------------------------- Key: HHH-6373 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6373 Project: Hibernate Core Issue Type: Task Components: documentation Reporter: Strong Liu -- 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

13 years

1
0
0 / 0

[Hibernate-JIRA] Created: (OGM-81) Build uses <scope> optional instead of optional=true

by Sanne Grinovero (JIRA)

Build uses <scope> optional instead of optional=true ---------------------------------------------------- Key: OGM-81 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-81 Project: Hibernate OGM Issue Type: Bug Components: build Affects Versions: 3.0.0.Alpha2, 3.0.0.Alpha1 Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Trivial Fix For: 3.0-next Pom.xml(s) should read <optional>true</optional> instead of <scope>optional</scope> -- 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

13 years

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

13 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-781) Add a database backed Directory and DirectoryProvider

by Ted Pennings (JIRA)

Add a database backed Directory and DirectoryProvider ----------------------------------------------------- Key: HSEARCH-781 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-781 Project: Hibernate Search Issue Type: New Feature Components: directory provider Affects Versions: 3.4.0.Final Reporter: Ted Pennings It would be great if there were a database backed Luncene Directory and DirectoryProvider. This would be roughly similar to what Compass provided with their JdbcDirectory class. Unfortunately due to Lucene API differences, it's not easy to drop the Compass JdbcDirectory into Hibernate Search. -- 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

13 years

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

13 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6368) remove deprecated hibernate annotations

by Strong Liu (JIRA)

remove deprecated hibernate annotations --------------------------------------- Key: HHH-6368 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6368 Project: Hibernate Core Issue Type: Task Components: annotations Reporter: Strong Liu Assignee: Strong Liu Fix For: 4.0.0.next org.hibernate.annotations.CollectionOfElements org.hibernate.annotations.ForceDiscriminator org.hibernate.annotations.MapKey org.hibernate.annotations.MapKeyManyToMany those annotations above have been marked deprecated for a long time, time to delete them -- 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

13 years

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6367) Calling PersistenceSet.clear() prevents adding elements to it in the same session

by Gabriel Axel (JIRA)

Calling PersistenceSet.clear() prevents adding elements to it in the same session --------------------------------------------------------------------------------- Key: HHH-6367 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6367 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.5 Reporter: Gabriel Axel I have an entity that contains a Set annotated with @ElementCollection . When I try to clear the set and after that add new elements in the same session, only the clear works and the added elements are not persisted (matching rows are not added to the table). My workaround is instead of calling Set.clear() , to assign a new HashSet to it, and then adding new elements works fine. The same entity is also indexed with Hibernate Search, and while this bug happens with the database, Hibernate Search reindexes the collection properly (though the index does not match the database). -- 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

13 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-6364) Add org.hibernate.metamodel.relational.Value.getColumnSpan() and getColumns()

by Gail Badner (JIRA)

Add org.hibernate.metamodel.relational.Value.getColumnSpan() and getColumns() ----------------------------------------------------------------------------- Key: HHH-6364 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6364 Project: Hibernate Core Issue Type: Sub-task Components: core Reporter: Gail Badner Assignee: Gail Badner Fix For: 4.0.0.next -- 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

13 years

1
5
0 / 0

[Hibernate-JIRA] Created: (HHH-6363) NPE in class PropertyContainer.mustBeSkipped

by Yves Galante (JIRA)

NPE in class PropertyContainer.mustBeSkipped -------------------------------------------- Key: HHH-6363 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6363 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.5 Reporter: Yves Galante Attachments: PropertyContainer.patch When parsing annotation there is a NPE in PropertyContainer.mustBeSkipped(XProperty property) method. For some class (parameterized) the property.getType() return null, patched code check this. Case : @Embeddable public final class AAA<V extends Serializable> implements Serializable { @Column(name = "TYPE_AAA") private final Class<V> aaaType; } -- 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

13 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues June 2011