July 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-93) index map<String, Object>

by koen handekyn (JIRA)

index map<String, Object> ------------------------- Key: HSEARCH-93 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-93 Project: Hibernate Search Issue Type: New Feature Components: engine Affects Versions: 3.0.0.beta3 Reporter: koen handekyn example class class MyDocument { @DocumentId long id; @Fields java.util.map<String, String> metaData; } the @Fields annotation stores each key value pair as a lucene key value. this allows efficient searching on loosely typed object meta data (which is typically hard to map onto a relational database model but perfect for a lucene index) note : this could probably be realized with a FieldBridge but a specifc annotaion could be handy note : ideally a MultiMap is also supported as a property can have multiple occurances in a lucene document -- 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

17 years, 3 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2688) HQL: Incorrect join when ordering by property of nullable many-to-one

by Scott Van Wart (JIRA)

HQL: Incorrect join when ordering by property of nullable many-to-one --------------------------------------------------------------------- Key: HHH-2688 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2688 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.4.sp1 Environment: Oracle 10gR2 Reporter: Scott Van Wart Attachments: pojos_and_mappings.zip I have two tables: Parent and Child. Children may not have a parent. I want to select all children, ordering by parent name: TABLE parent_table ( parent_id NUMBER PRIMARY KEY, parent_name VARCHAR2(30) NOT NULL ); TABLE child_table ( child_id NUMBER PRIMARY KEY, parent_id REFERENCES parent ON DELETE SET NULL ); So I create the two POJOs and mapping documents (attached). After openSession(): List children = session.createQuery( "from Child c order by c.parent.name" ).list(); I only get back the children with parents, because here's the generated SQL, with an INNER join: select child0_.child_id as child1_17_, child0_.parent_id as parent2_17_ from child_table child0_, parent_table parent1_ where child0_.parent_id=parent1_.parent_id order by parent1_.parent_name; Because parent_id in the child table is nullable, I would expect the generated SQL to be: select child_id, parent_id from child_table c LEFT JOIN parent_table p ON c.parent_id = p.parent_id order by p.parent_name; I guess a workaround might be to specify the join type explicitly in the HQL, but this default behavior kind of surprised me. Thanks. -- 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

17 years, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2010) getForUpdateString is not correct in DB2Dialect; session.lock doesn't work as expected.

by Lari Hotari (JIRA)

getForUpdateString is not correct in DB2Dialect; session.lock doesn't work as expected. --------------------------------------------------------------------------------------- Key: HHH-2010 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2010 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3, 3.2.0.cr3 Environment: 3.1.3, DB2 Reporter: Lari Hotari The correct getForUpdateString for DB2 should be "for update with rr" see: http://opensource.atlassian.com/projects/hibernate/browse/HB-1032 DB2 will release all locks created in a result set if the isolation level is lower than TRANSACTION_SERIALIZABLE (RR in DB2). Locks and concurrency control in DB2: http://publib.boulder.ibm.com/infocenter/db2help/topic/com.ibm.db2.udb.do... " The duration of row locking varies with the isolation level being used: * UR scans: No row locks are held unless row data is changing. * CS scans: Row locks are only held while the cursor is positioned on the row. * RS scans: Only qualifying row locks are held for the duration of the transaction. * RR scans: All row locks are held for the duration of the transaction. " -- 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

17 years, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2116) CLONE -explicit and implicit query with enabled filter gives different results

by Armin Haaf (JIRA)

CLONE -explicit and implicit query with enabled filter gives different results ------------------------------------------------------------------------------ Key: HHH-2116 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2116 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr2 Environment: hibernate 3.2.0.cr2, hibernate annotations 3.2.0.cr1 Reporter: Armin Haaf we are playing around with filters and found a inconsistent behaviour in using a filter in an explicit vs. implicit join. In explicit join a filter is not active, but in an implicit join it is active. Please look at the attachment -- 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

17 years, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2751) MappedSuperclass + M:N relation + PostUpdateListener = AssertionFailure: collection [xyz] was not processed by flush()

by S.Schnabl (JIRA)

MappedSuperclass + M:N relation + PostUpdateListener = AssertionFailure: collection [xyz] was not processed by flush() ---------------------------------------------------------------------------------------------------------------------- Key: HHH-2751 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2751 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.4.sp1, 3.2.4, 3.2.3, 3.2.2, 3.2.1 Environment: Windows-XP, Jboss 4.2 GA, Hibernate 3.2.1GA, EJB3 Reporter: S.Schnabl Attachments: Hibernate-TestCase.rar For more details see the attached testcase. I'm sorry, but in the short of time i only got a testcase for jboss-server 4.2. Please deploy the server.ear from /release-directory and then call the /src/client/TestCaseClient.java. Explanation: I have two entities A.class and B.class defined, both inheriting from an common (empty) abstract MappedSuperclass. A and B having a m:n relation between each other. Furthermore there is an PostUpdateListener, which iterates through all properties of updated entities. Testcase: Both entities are linked with each (m:n), now i do an update of a simple property of entity A --> MyPostUpdateListener will be called, which iterates through each property of the updated entity(ies). In case of this property was a collection (= property of the m:n relation), the listener furthermore iterates through this collection and get the id of each object in the collection. Doing so will raise following exception : Caused by: org.hibernate.AssertionFailure: collection [com.qualitype.testcase.server.ejb.entity.EntityB.entitiesOfA] was not processed by flush() at org.hibernate.engine.CollectionEntry.postFlush(CollectionEntry.java:205) at org.hibernate.event.def.AbstractFlushingEventListener.postFlush(AbstractFlushingEventListener.java:333) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:28) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) at org.hibernate.ejb.AbstractEntityManagerImpl$1.beforeCompletion(AbstractEntityManagerImpl.java:515) ... 29 more Summarized these error will only occur, in case we are inherating from a mappedSuperClass, having a m:n relation and having the listener touching the collection-elements. But these scenario isn'n very uncommon. We are using hibernate-event listener system for auditing-purposes, so you should understand that touching ever (element in the) collectin is necessary for audit-purposes. Seems for me like a bug. Need this fixed asap ... -- 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

17 years, 3 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2104) Infinite recursion in org.hibernate.cfg.Configuration.setListener(String, Object)

by Daniel Beer (JIRA)

Infinite recursion in org.hibernate.cfg.Configuration.setListener(String, Object) --------------------------------------------------------------------------------- Key: HHH-2104 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2104 Project: Hibernate3 Type: Bug Components: core Versions: 3.1 rc 1 Environment: Hibernate 3.1, but also newer versions contain this bug. Reporter: Daniel Beer When method org.hibernate.cfg.Configuration.setListener(String, Object) is called with second argument set to <null> (in order to remove all listeners of that type) an infinite recursion occurs. Cause: There is a check against null in this method which invokes a wrong method (its a simple typos): if ( listener == null ) { setListener( type, null ); } Instead the method "setListeners(String, Object[])" should be invoked (notice the trailing "s" in the methods name). -- 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

17 years, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2400) ability to specify joinType in createAlias in DetachedCriteria

by Michal Pavlasek (JIRA)

ability to specify joinType in createAlias in DetachedCriteria -------------------------------------------------------------- Key: HHH-2400 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2400 Project: Hibernate3 Type: New Feature Versions: 3.2.1 Environment: 3.2.1 Reporter: Michal Pavlasek Criteria has two methods than can create an alias, but DetachedCriteria has only one method, without the possibility of specifying the joinType. It will be very useful for me to have that opportunity. Now I have to use Criteria instead of DetachedCriteria in some cases. Criteria: Criteria createAlias(String associationPath, String alias) Join an association, assigning an alias to the joined association. Criteria createAlias(String associationPath, String alias, int joinType) Join an association using the specified join-type, assigning an alias to the joined association. DetachedCriteria: DetachedCriteria createAlias(String associationPath, String alias) -- 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

17 years, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2379) adding a new method to DetachedCriteria

by Vadim Marchenko (JIRA)

adding a new method to DetachedCriteria --------------------------------------- Key: HHH-2379 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2379 Project: Hibernate3 Type: Improvement Components: core Versions: 3.2.1 Environment: 3.2, all db flavors Reporter: Vadim Marchenko I propose to add additional method to detached criteria to allow creating of left join constructs as in public DetachedCriteria createAlias(String associationPath, String alias, int joinType) throws HibernateException { criteria.createAlias(associationPath, alias, joinType); return 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

17 years, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2364) DetachedCriteria.getExecutableCriteria(session) does not return a new criteria each time

by Amir Pashazadeh (JIRA)

DetachedCriteria.getExecutableCriteria(session) does not return a new criteria each time ---------------------------------------------------------------------------------------- Key: HHH-2364 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2364 Project: Hibernate3 Type: Bug Components: query-criteria Versions: 3.2.1 Reporter: Amir Pashazadeh detachedCriteria.getExecutableCriteria(session) does not return a new Criteria each time; so if some projection or ... is applied on the result criteria, it will remain on next criterias. -- 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

17 years, 3 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2653) DetachedCriteria does not create assocation criteria with alias

by Jörg Heinicke (JIRA)

DetachedCriteria does not create assocation criteria with alias --------------------------------------------------------------- Key: HHH-2653 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2653 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.4.sp1 Reporter: Jörg Heinicke It's known that ordering on association properties in the criteria API only works with aliases (http://forum.hibernate.org/viewtopic.php?t=972241 and countless other threads, HHH-2629). Unfortunately, you can't even use the aliases with DetachedCriteria since it has a bug: public DetachedCriteria createCriteria(String associationPath, String alias) throws HibernateException { return new DetachedCriteria( impl, criteria.createCriteria(associationPath) ); } public DetachedCriteria createCriteria(String associationPath) throws HibernateException { return new DetachedCriteria( impl, criteria.createCriteria(associationPath) ); } As you can see both implementations are equal, the first one ignores the alias parameter. It has to be public DetachedCriteria createCriteria(String associationPath, String alias) throws HibernateException { return new DetachedCriteria( impl, criteria.createCriteria(associationPath, alias) ); } -- 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

17 years, 3 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2007