February 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-694) Keep legacy constructor of DocumentExtractor for people using Infinispan Query 5.0.0.Alpha3

by Sanne Grinovero (JIRA)

Keep legacy constructor of DocumentExtractor for people using Infinispan Query 5.0.0.Alpha3 ------------------------------------------------------------------------------------------- Key: HSEARCH-694 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-694 Project: Hibernate Search Issue Type: Task Components: query Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Trivial Fix For: 3.4.0.Alpha1 This is not a public API, still I shouldn't have removed it as Infinispan Query was released targeting Hibernate Search 3.4.0-SNAPSHOT. To be removed at next tag. -- 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

15 years, 1 month

1
1
0 / 0

[Hibernate-JIRA] Created: (ANN-472) @UniqueConstraint declaration is not friendly towards inheritance or reflection

by Ted Bergeron (JIRA)

@UniqueConstraint declaration is not friendly towards inheritance or reflection ------------------------------------------------------------------------------- Key: ANN-472 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-472 Project: Hibernate Annotations Type: Improvement Versions: 3.2.0.ga Environment: Hibernate 3.2 GA Reporter: Ted Bergeron The current way to define a composite unique constraint is limiting. @Table(name="tbl_sky", uniqueConstraints = {@UniqueConstraint(columnNames={"month", "day"})} ) Suppose I have an abstract base class called A that gives me Id and Name, subclassed by abstract class B that gives me Customer. Then I have many concrete classes that subclass B. For all of these, I'd want the combination of Name and Customer to be unique. As I do not use @Table with abstract base classes, I currently have to repeat: uniqueConstraints = {@UniqueConstraint(columnNames={"name", "customer_id"})} on all concrete classes. If we had an alternate way to define these constraints at the property level (as XDoclet did with hibernate 2), I could define this in the base classes and inherit the constraint declaration. The other need is that I would like to use reflection to scan the properties and apply proper validations in the view layer. With @Column(unique = true) this is easy to do. The view layer makes an AJAX call and all is well. For a composite constraint, it does not work well currently. -- 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

15 years, 1 month

5
9
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-693) Avoid reflection when associating query matches to their DocumentBuilders

by Sanne Grinovero (JIRA)

Avoid reflection when associating query matches to their DocumentBuilders ------------------------------------------------------------------------- Key: HSEARCH-693 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-693 Project: Hibernate Search Issue Type: Improvement Components: engine, query Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.4.0.Alpha1 We don't always need to use the ReflectHelper, actually all cases we have the class instance already. The class is needed to figure out the proper DocumentBuilder and re-transform stored fields into their matching OO values (besides obviously loading Hibernate entities). -- 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

15 years, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-690) FieldSelectors are never used

by Sanne Grinovero (JIRA)

FieldSelectors are never used ----------------------------- Key: HSEARCH-690 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-690 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.3.0.Final Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.4.0 DocumentBuilder has a method checkAllowFieldSelection() which is invoked by the super constructor, even when it resolved to true after class initialization it's overwritten by the default class value (false). Actually, I didn't understand why this method is DocumentBuilder dependant and not only depending on the specific fields being asked for in the projection: we should still be able to use the FieldSelector for classes which don;t have only two-way bridges, as long as they are not selected for loading. -- 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

15 years, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-691) Automatically figure out the minimum set of fields needed to be loaded via a FieldSelector

by Sanne Grinovero (JIRA)

Automatically figure out the minimum set of fields needed to be loaded via a FieldSelector ------------------------------------------------------------------------------------------ Key: HSEARCH-691 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-691 Project: Hibernate Search Issue Type: Improvement Components: query Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.4.0 -- 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

15 years, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5868) Add Configuration.buildSessionFactory overload for ServicesRegistry

by Steve Ebersole (JIRA)

Add Configuration.buildSessionFactory overload for ServicesRegistry ------------------------------------------------------------------- Key: HHH-5868 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5868 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha1 Add Configuration.buildSessionFactory overload for ServicesRegistry -- 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

15 years, 1 month

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5943) Make ServiceRegistry mutable

by Steve Ebersole (JIRA)

Make ServiceRegistry mutable ---------------------------- Key: HHH-5943 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5943 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha1 Allow mutation of the ServiceRegistry in terms of both the regsitered Services and ServiceInitiators -- 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

15 years, 1 month

1
2
0 / 0

[Hibernate-JIRA] Updated: (HHH-1268) Unidirection OneToMany causes duplicate key entry violation when removing from list

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1268?page=c... ] Gail Badner updated HHH-1268: ----------------------------- Fix Version/s: 4.0.0.Alpha1 3.6.next Christian, thanks for the patch. I'll take a look at it for 3.6.2. > Unidirection OneToMany causes duplicate key entry violation when removing from list > ----------------------------------------------------------------------------------- > > Key: HHH-1268 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1268 > Project: Hibernate Core > Issue Type: Bug > Affects Versions: 3.1, 3.5.6, 3.6.0 > Environment: 3.1 final > MySql 4.1.14 using MYISAM tables > Reporter: Rex Madden > Assignee: Gail Badner > Fix For: 3.2.x, 3.3.x, 3.6.next, 4.0.0.Alpha1 > > Attachments: possible_solution.patch, src.zip > > > Simple OneToMany parent/child relationship using the default table structure (2 tables and a join table) > Add 3 children to the parent. Flush. Remove the first child. Flush throws error: > Exception in thread "main" org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update > at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:69) > at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) > at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:202) > at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:230) > at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:143) > at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:296) > at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) > at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:980) > at UnidirectionalOneToManyRemoveFromListBug.main(UnidirectionalOneToManyRemoveFromListBug.java:27) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:86) > Caused by: java.sql.BatchUpdateException: Duplicate key or integrity constraint violation, message from server: "Duplicate entry '5' for key 2" > at com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:1461) > at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:58) > at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:195) > ... 11 more > The problem is that there is a unique key on the relationship table that gets violated. The session removes the last row in the relationship table, then attempts to rewrite the child_id's. It fails since there is a uniqueness constraint on that column. -- 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

15 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-688) Exclude indirect dependency on JBoss WS Native

by Emmanuel Bernard (JIRA)

Exclude indirect dependency on JBoss WS Native ---------------------------------------------- Key: HSEARCH-688 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-688 Project: Hibernate Search Issue Type: Bug Components: build Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Priority: Minor Fix For: 3.4.0 -- 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

15 years, 1 month

3
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-430) Use multiple threads for text analysis in MassIndexer

by Sanne Grinovero (JIRA)

Use multiple threads for text analysis in MassIndexer ----------------------------------------------------- Key: HSEARCH-430 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-430 Project: Hibernate Search Issue Type: New Feature Components: documentation, engine Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.2.0.Beta3 org.hibernate.search.MassIndexer is defining the API already, it's commented. Implementor also has a sketch already, currently commented out. -- 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

15 years, 1 month

2
6
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 February 2011