August 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2680) Blobs not updated on Session.merge() for detached instances

by Timo Thomas (JIRA)

Blobs not updated on Session.merge() for detached instances ----------------------------------------------------------- Key: HHH-2680 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2680 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1, 3.2.2 Environment: Windows XP Prof., Java 1.5_010, HSQLDB 1.8.0 Reporter: Timo Thomas Attachments: BlobTest.zip Blob columns are not updated when a detached instance is saved at the session with merge(). See attached TestCase. -- 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, 9 months

11
27
0 / 0

[Hibernate-JIRA] Created: (HHH-5284) Allow Type to dictate the default length/scale/precision

by Steve Ebersole (JIRA)

Allow Type to dictate the default length/scale/precision -------------------------------------------------------- Key: HHH-5284 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5284 Project: Hibernate Core Issue Type: Improvement Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6 Not sure if this is doable in 3.6 timeframe, but it would be fantastic if Types could name the default column size for its sql definition. Examples of where this is useful include * mapping a single char/Character versus mapping a String etc to a CHAR * UUID mappings, where it would be nice to properly size the data. -- 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, 9 months

1
5
0 / 0

[Hibernate-JIRA] Created: (HHH-4509) Ability to control JBoss Cache eviction via session factory properties

by Brian Stansberry (JIRA)

Ability to control JBoss Cache eviction via session factory properties ---------------------------------------------------------------------- Key: HHH-4509 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4509 Project: Hibernate Core Issue Type: New Feature Components: caching (L2) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.5 A la what Galder has added for the Infinispan integration. -- 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, 9 months

2
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2843) org.hibernate.PropertyAccessException: IllegalArgumentException occurred calling getter of natural Key component

by Charles Canning (JIRA)

org.hibernate.PropertyAccessException: IllegalArgumentException occurred calling getter of natural Key component ---------------------------------------------------------------------------------------------------------------- Key: HHH-2843 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2843 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.3 Environment: Linux Reporter: Charles Canning The full description is here in the forums: http://forum.hibernate.org/viewtopic.php?t=979408 I will provide more details if I can. -- 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, 9 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4999) createSQLQuery(query).list() result screw up when when columns in different tables have same name

by thogau (JIRA)

createSQLQuery(query).list() result screw up when when columns in different tables have same name ------------------------------------------------------------------------------------------------- Key: HHH-4999 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4999 Project: Hibernate Core Issue Type: Bug Components: query-sql Affects Versions: 3.5.0-CR-2 Environment: hibernate-core 3.5.0-CR-2 MySQL 5 Reporter: thogau Attachments: joinProblem.zip The same SQL query doesn't retrieve the same results with hibernate and SQL client : {{SELECT groupe.name, center.name, roles.displayname, users.username, CASE WHEN center.id = 2 THEN 1 ELSE 0 END AS showlast FROM groupe, center, users, roles WHERE users.role_id = roles.id AND users.center_id = center.id AND center.group_id = groupe.id ORDER BY showlast, groupe.sitecoordinateur DESC, groupe.name, center.headcenter DESC, center.name, roles.id}} When performed with hibernate, *group.name* is retrieved twice (*center.name* is always the same as *group.name*). Still, it is possible to retrieve the correct value for *center.name* using *CONCAT('', center.name)* A small eclipse + maven projet with unit test is attached. -- 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, 9 months

4
15
0 / 0

[Hibernate-JIRA] Created: (HHH-5406) Schema export does not consistently follow naming strategy for unique constraints

by Jonathan (JIRA)

Schema export does not consistently follow naming strategy for unique constraints --------------------------------------------------------------------------------- Key: HHH-5406 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5406 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.4 Environment: Hibernate 3.5.4, No database needed Reporter: Jonathan Priority: Minor Attachments: UniqueConstraintTest.java When performing a schema export for entities that include annotated unique constraints, Hibernate does not consistently follow the naming strategy for field names in the unique constraint. It appears that a naming strategy applies only for fields that are mapped to another class. The attached test demonstrates this. -- 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, 9 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-520) Make work queue size configurable in Lucene backend

by Sanne Grinovero (JIRA)

Make work queue size configurable in Lucene backend --------------------------------------------------- Key: HSEARCH-520 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-520 Project: Hibernate Search Issue Type: Improvement Components: engine Reporter: Sanne Grinovero Fix For: 3.3.0 What's currently hardcoded as org.hibernate.search.batchindexing.Executors.QUEUE_MAX_LENGTH might be nice to be configurable, especially as the async backend will block after filling it up (see HSEARCH-515). The larger the better it will be able to handle load spikes but using more memory to store the scheduled work. -- 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, 9 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-543) Is it expected for SyncBackendLongWorklistsStressTest to take ~40s

by Emmanuel Bernard (JIRA)

Is it expected for SyncBackendLongWorklistsStressTest to take ~40s ------------------------------------------------------------------ Key: HSEARCH-543 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-543 Project: Hibernate Search Issue Type: Task Components: build Environment: Reporter: Emmanuel Bernard Assignee: Sanne Grinovero I wonder if it is expected for the test to take so long. 40 secs for 3000 entities seems long to me. DEBUG logs do not seem to be the bottlenech. Note that most of the time is spent before the query counting is executed. As if async was not used. -- 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, 9 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5159) 'in elements' does not work on ElementCollections of Enums

by Peer Hartmann (JIRA)

'in elements' does not work on ElementCollections of Enums ---------------------------------------------------------- Key: HHH-5159 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5159 Project: Hibernate Core Issue Type: Bug Components: core, entity-manager, query-hql Affects Versions: 3.5.1, 3.3.2 Environment: Oracle 10, Hibernate 3.5.1-Final Reporter: Peer Hartmann Attachments: bugreport-mvn.zip When performing a query with an 'in elements' clause and an enum typed parameter, hibernate does not correctly set the parameter value for the underlying SQL. Here is an example (HQL) query: select e from Employee e where :function in elements( e.jobFunctions ); Hibernate makes the following SQL of that (correct) Hibernate: select employee0_.id as id9_, employee0_.name as name9_ from Employee employee0_ where ? in (select jobfunctio1_.jobfunction from employee2jobfunction jobfunctio1_ where employee0_.id=jobfunctio1_.employeeId) ...but sets the parameter wrong as it uses toString instead of the name of the enum: [LogPreparedStatement] DEBUG - executing PreparedStatement: 'select ... from employee2jobfunction ...' with bind parameters: {1=[B@2eb6fb} the exmaple uses an employee entity class with an ElementCollection of JobFunction-enum entries. See the attached zip-file for details. The same query works when using an entity instead of an enum. -- 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, 9 months

4
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-438) @IndexedEmbedded does not work for child classes in inheritance tree

by Ted Williams (JIRA)

@IndexedEmbedded does not work for child classes in inheritance tree -------------------------------------------------------------------- Key: HSEARCH-438 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-438 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.1.1.GA Environment: Jboss 4.2.3.GA Hibernate Core 3.2 Hibernate Search 3.1.1.GA Reporter: Ted Williams Priority: Critical Attachments: Classes.zip When using @IndexedEmbedded on a set/list of parent/top classes the @Field annotations in the child classes are not picked up and indexed. @IndexedEmbedded(depth=100) @OneToMany(fetch = FetchType.LAZY, mappedBy = "top", cascade = CascadeType.ALL) public Set<Parent> getParents() { return parents; } public class Child extends Parent { private String childName; @Field(name = "childName", index=Index.TOKENIZED) // This field is not picked up!!! . . } -- 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, 9 months

5
23
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 2010