September 2008 - hibernate-issues

[Hibernate-JIRA] Created: (EJB-279) Entity Listener defined in orm.xml does not work

by Gary Ip (JIRA)

Entity Listener defined in orm.xml does not work ------------------------------------------------ Key: EJB-279 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-279 Project: Hibernate Entity Manager Type: Bug Components: EntityManager Versions: 3.3.0.ga Environment: Hibernate core 3.2.2.GA, Hibernate Annotations 3.3.0.GA, Hibernate Entity Manager 3.3.0.GA, Spring 2.0.3, Tomcat 5.5.20, Oracle 9i Reporter: Gary Ip A default Entity Listener defined in orm.xml (this EJB3 deployment descriptor) worked in HEM and HAN 3.2.1 but not 3.3.0 http://forums.hibernate.org/viewtopic.php?t=972352&sid=95588b2c2391806158... -- 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, 8 months

4
9
0 / 0

[Hibernate-JIRA] Commented: (HHH-530) Allow application of filters on subqueries

by Shawn Clowater (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-530?page=co... ] Shawn Clowater commented on HHH-530: ------------------------------------ What's HQL? ;) Bleh, I actually thought it was working on the HQL already (we are primarily Criteria). From my initial pass trying to see what is disabling them in HQL it would appear that it might only be the following that would need to change.... In JoinProcessor there's a snippet {code} // Generate FROM and WHERE fragments for the from element. JoinFragment joinFragment = join.toJoinFragment( inSubquery ? Collections.EMPTY_MAP : queryTranslatorImpl.getEnabledFilters(), fromElement.useFromFragment() || fromElement.isDereferencedBySuperclassOrSubclassProperty(), fromElement.getWithClauseFragment(), fromElement.getWithClauseJoinAlias() ); {code} {code} Which i think should just be // Generate FROM and WHERE fragments for the from element. JoinFragment joinFragment = join.toJoinFragment( queryTranslatorImpl.getEnabledFilters(), fromElement.useFromFragment() || fromElement.isDereferencedBySuperclassOrSubclassProperty(), fromElement.getWithClauseFragment(), fromElement.getWithClauseJoinAlias() ); {code} Of course if it works then the whole inSubquery thing should be peeled back. The only other suspect code I see would be in the token(String token, QueryTranslatorImpl q) method of WhereParser but it might be fine (aka I'm not sure exactly what it's doing) > Allow application of filters on subqueries > ------------------------------------------ > > Key: HHH-530 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-530 > Project: Hibernate Core > Issue Type: Patch > Components: core > Reporter: Gavin King > Assignee: Steve Ebersole > Fix For: 3.3.x > > Attachments: HHH-530.3.3.SP1.patch, HHH-530.Additional.Subquery.patch, HHH-530.patch, hibernate_filter_fix-3.0.5.patch, hibernate_filter_fix-3.0.5_14.patch, SubqueriesWithFiltersTest.patch > > > Currently filter conditions are applied in subselects, they should not be. -- 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, 8 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-530) Allow application of filters on subqueries

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-530?page=co... ] Steve Ebersole commented on HHH-530: ------------------------------------ Shawn, I tried applying this patch but I am not seeing filters applied to subqueries for anything other than criteria. What about HQL? > Allow application of filters on subqueries > ------------------------------------------ > > Key: HHH-530 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-530 > Project: Hibernate Core > Issue Type: Patch > Components: core > Reporter: Gavin King > Assignee: Steve Ebersole > Fix For: 3.3.x > > Attachments: HHH-530.3.3.SP1.patch, HHH-530.Additional.Subquery.patch, HHH-530.patch, hibernate_filter_fix-3.0.5.patch, hibernate_filter_fix-3.0.5_14.patch, SubqueriesWithFiltersTest.patch > > > Currently filter conditions are applied in subselects, they should not be. -- 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, 8 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3439) Change o.h.cfg.Mappings to not require constructor

by Steve Ebersole (JIRA)

Change o.h.cfg.Mappings to not require constructor -------------------------------------------------- Key: HHH-3439 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3439 Project: Hibernate3 Issue Type: Improvement Components: metamodel Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.4 Mappings requiring passing all the mapping queues into its constructor causes interoperability issues with other components (annotations e.g.) because they generally extend Mappings to add extra information. Therefore we introduce an incompatibility whenever we add a new mapping attribute because we are currently forced to change the signature of the Mappings constructor. A better approach is to make Mappings an interface with an impl that defined as an inner class to o.h.cfg.Configuration so that it can expose access to the queues directly from there. Annotations, etc can than simply extend that Mappings impl. -- 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, 8 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3483) org.hibernate.test.hql.ScrollableCollectionFetchingTest#testScrollingJoinFetchesForward unsupported by DB2

by Gail Badner (JIRA)

org.hibernate.test.hql.ScrollableCollectionFetchingTest#testScrollingJoinFetchesForward unsupported by DB2 ---------------------------------------------------------------------------------------------------------- Key: HHH-3483 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3483 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.2.6 Environment: DB2 Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.2.x, 3.3.x Test org.hibernate.test.hql.ScrollableCollectionFetchingTest#testScrollingJoinFetchesForward uses scroll mode FORWARD_ONLY, but DB2 requires SCROLL_INSENSITIVE and SCROLL_SENSITIVE for scrolling. This is not a bug. According to the JDBC spec, a TYPE_FORWARD_ONLY ResultSet is non-scrollable, so isAfterLast does not need to be supported. The fix is for DB2Dialect to override Dialect.supportsResultSetPositionQueryMethodsOnForwardOnlyCursor() and return 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

15 years, 8 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3479) NPE in ForeignKey

by Thomas Diesler (JIRA)

NPE in ForeignKey ----------------- Key: HHH-3479 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3479 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.6 Reporter: Thomas Diesler java.lang.NullPointerException at org.hibernate.mapping.ForeignKey.isPhysicalConstraint(ForeignKey.java:125) at org.jbpm.db.JbpmSchema.getCleanSql(JbpmSchema.java:132) at org.jbpm.db.JbpmSchema.cleanSchema(JbpmSchema.java:214) at org.jbpm.persistence.db.DbPersistenceServiceFactory.cleanSchema(DbPersistenceServiceFactory.java:123) public boolean isPhysicalConstraint() { return referencedTable.isPhysicalTable() && getTable().isPhysicalTable() && !referencedTable.hasDenormalizedTables(); } This NPE occurs when the referencedTable is null. There are several methods that assume that that the referencedTable is not null. The referencedEntityName however is not null in my use case. -- 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, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (EJB-344) API method to return callback methods

by Shane Bryzak (JIRA)

API method to return callback methods ------------------------------------- Key: EJB-344 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-344 Project: Hibernate Entity Manager Issue Type: New Feature Components: EntityManager Reporter: Shane Bryzak We need an easy way to determine the callback methods (pre-create, pre-update, etc) for a given Hibernate bean in Seam. Currently I've hacked together some nasty reflection code based on Emmanuel's advice. Related issue: http://jira.jboss.org/jira/browse/JBSEAM-2029 -- 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, 8 months

4
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3394) ScrollableResults delivers sometime wrong collections when used with a LEFT JOIN FETCH clause

by Thomas Scherm (JIRA)

ScrollableResults delivers sometime wrong collections when used with a LEFT JOIN FETCH clause --------------------------------------------------------------------------------------------- Key: HHH-3394 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3394 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.6 Environment: Windows, Java SE 6.06, Oracle 9 / 10, Hibernate 3.2.6 Reporter: Thomas Scherm Following stament is used to create a ScrollableResult from a Query. SELECT DISTINCT f FROM Fall f LEFT JOIN FETCH f.leistungen l WHERE (f.status = '2' OR f.status = '3') AND f.quartalJahr = ? It schould deliver a Faelle with prefeched sets of Leistungen. The first row is ok. All subsequent rows return exactly one leistungen. Th SQL Statement is ok, the session cache works fine and has the missing Leistungen, but they are not attached. As Workaround we removed the FETC clause and let it work with lazy loading. It works. -- 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, 8 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HBX-1063) Any mapping not working for Eclipse Hibernate Plugin

by Marcus Ilgner (JIRA)

Any mapping not working for Eclipse Hibernate Plugin ---------------------------------------------------- Key: HBX-1063 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1063 Project: Hibernate Tools Issue Type: Bug Components: eclipse Affects Versions: 3.2.2 Reporter: Marcus Ilgner My project uses JPA with Hibernate and I have created a Hibernate Console configuration accordingly. One of my entity classes uses the @Any annotation on one of its properties. If I try to open the SessionFactory, I receive the message: org.hibernate.MappingException: property mapping has wrong number of columns However, the object works fine in the software/unit tests. -- 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, 8 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HSHARDS-51) ShardResolutionStrategyImpl needs equals() and hashCode()

by Max Ross (JIRA)

ShardResolutionStrategyImpl needs equals() and hashCode() --------------------------------------------------------- Key: HSHARDS-51 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-51 Project: Hibernate Shards Issue Type: Bug Components: engine Reporter: Max Ross Assignee: Max Ross Priority: Minor Fix For: 3.0.0 There's basically no way to implement a cache-aware ShardResolutionStrategy until we implement equals() and hashCode() on ShardResolutionStrategyImpl. -- 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, 8 months

2
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2008