June 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2673) Collection <loader> doesn't support named hql queries

by Luca Dall'Olio (JIRA)

Collection <loader> doesn't support named hql queries ------------------------------------------------------ Key: HHH-2673 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2673 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.4.sp1 Environment: Hibernate 3.2.4 HSQLDB 1.8.0.1 Reporter: Luca Dall'Olio When mapping a "named HQL query loader" for a collection, you always get a "Named SQL query loader" Exception. The exception goes away just changing the <query> elemento into <sql-query> . By looking at the source code in org.hibernate.persister.collection.NamedQueryCollectionInitializer it looks like an unwanted limitation : AbstractQueryImpl query = (AbstractQueryImpl) session.getNamedSQLQuery(queryName); should be insted : AbstractQueryImpl query = (AbstractQueryImpl) session.getNamedQuery(queryName); This would make it work both for named HQL queries and for named SQL queries. This is an example mapping : <hibernate-mapping package="org.hibernate.test"> <class name="A"> <id> <generator class="native"/> </id> <property name="name" not-null="true"/> <set name="bees"> <one-to-many class="B"/> <loader query-ref="qb"/> </set> </class> <class name="B"> <id> <generator class="native"/> </id> <property name="name" not-null="true"/> </class> <query name="qb"> select bee from B bee </query> </hibernate-mapping> -- 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

18 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSHARDS-19) ShardedSessionImpl.replicate(String entityName, Object obj, ReplicationMode replicationMode);

by Max Ross (JIRA)

ShardedSessionImpl.replicate(String entityName, Object obj, ReplicationMode replicationMode); --------------------------------------------------------------------------------------------- Key: HSHARDS-19 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-19 Project: Hibernate Shards Issue Type: Task Components: engine Affects Versions: 3.0.0.Beta1 Reporter: Max Ross Assignee: Max Ross Fix For: 3.0.0.beta2 -- 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

18 years, 6 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSHARDS-18) ShardedSessionImpl.replicate(Object obj, ReplicationMode replicationMode);

by Max Ross (JIRA)

ShardedSessionImpl.replicate(Object obj, ReplicationMode replicationMode); -------------------------------------------------------------------------- Key: HSHARDS-18 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-18 Project: Hibernate Shards Issue Type: Task Components: engine Affects Versions: 3.0.0.Beta1 Reporter: Max Ross Assignee: Max Ross Fix For: 3.0.0.beta2 -- 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

18 years, 6 months

2
3
0 / 0

[Hibernate-JIRA] Closed: (HHH-952) Patch to allow subqueries with joins using Criteria API and Subqueries with DetachedCriteria

by Chris Bredesen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-952?page=co... ] Chris Bredesen closed HHH-952. ------------------------------ > Patch to allow subqueries with joins using Criteria API and Subqueries with DetachedCriteria > -------------------------------------------------------------------------------------------- > > Key: HHH-952 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-952 > Project: Hibernate3 > Issue Type: Patch > Components: core > Affects Versions: 3.1 beta 1, 3.1 beta 2 > Environment: 3.1beta1 with MS SQL 2000 via jTDS > Reporter: John > Assignee: Chris Bredesen > Priority: Critical > Fix For: 3.3 > > Attachments: subquery-patch-3.2.4.SP1.txt, subquery-patch-311.txt, subquery-patch-313.txt, subquery-patch-31beta3.txt, subquery-patch.txt, subquery-patch.txt, SubqueryExpression.java > > > The existing code in SubqueryExpression.java constructed a select statement but did not have any provisions for creating joins. Therefore, it was not possible using the criteria API to create an exists subselect that had a join, even though running the source DetachedCriteria alone works perfectly. > For example, if this is the goal: > select * from foo f > where exists (select id from bar b join other o on b.o_id = o.id where o.prop = '123' and b.foo_id = f.id) > One might try something like this: > Criteria crit = session.createCriteria(Foo.class, fooAlias); > DetachedCriteria barCrit = DetachedCriteria.forClass(Bar.class, barAlias); > DetachedCriteria otherCrit = barCrit.createCriteria(Bar.OTHER_JOIN); > otherCrit.add( Restrictions.eq(Other.PROP, "123") ); > barCrit.add( Restrictions.eqProperty( -- props to join to foo here --) ); > barCrit.setProjection( Projections.id() ); > crit.add( Subqueries.exists(barCrit) ); > However, the existing code generates something like the following, which gets an error with an unknown alias 'o': > select * from foo f > where exists (select id from bar b where o.prop = '123' and b.foo_id = f.id) > This is also described here (at the end): http://forum.hibernate.org/viewtopic.php?t=942488 > The patch to SubqueryExpression.java fixes this to included the joins necessary for the filtering. This code was modeled (copied) off of code from CriteriaLoader. For me this works perfectly, but I don't understand the internals of this stuff enough to say how robust it is. Also included is a patch to the test case to enable testing of this, which was present but commented out. I did not change the contents of the test, which currently only attempts a joined subquery. This used to fail with an error, but now it works. The test does not check the results at all. (Inconsequential to the patch - Enrollment has two Ls.) > -----side notes > The patch file also has two other patches. The first increases the delay in BulkManipulationTest because I was getting inconsistent test results. I think that the precision on the version timestamp is not enough for 300 milliseconds delay to be enough to guarantee the test results. Also, in build.xml, there was a line that was meant to exclude the performance tests, but there was no **/*, on *, so they actually were not excluded. I changed this so the tests would complete in a reasonable amount of time. However, there is one other issue with testing that I worked around manually. After each test run, two databases (Users and Email) were left in the database. If I did not manually delete these then the number of failures on the next test run was different. This was really confusing until I figured it out because I was trying to make sure all the other testcases still passed with my patch, but even without the patch I was getting different results. -- 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

18 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Resolved: (HHH-952) Patch to allow subqueries with joins using Criteria API and Subqueries with DetachedCriteria

by Chris Bredesen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-952?page=co... ] Chris Bredesen resolved HHH-952. -------------------------------- Resolution: Fixed Fix Version/s: 3.3 Code committed is the 3.2.4.SP1 patch almost verbatim. > Patch to allow subqueries with joins using Criteria API and Subqueries with DetachedCriteria > -------------------------------------------------------------------------------------------- > > Key: HHH-952 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-952 > Project: Hibernate3 > Issue Type: Patch > Components: core > Affects Versions: 3.1 beta 1, 3.1 beta 2 > Environment: 3.1beta1 with MS SQL 2000 via jTDS > Reporter: John > Assignee: Chris Bredesen > Priority: Critical > Fix For: 3.3 > > Attachments: subquery-patch-3.2.4.SP1.txt, subquery-patch-311.txt, subquery-patch-313.txt, subquery-patch-31beta3.txt, subquery-patch.txt, subquery-patch.txt, SubqueryExpression.java > > > The existing code in SubqueryExpression.java constructed a select statement but did not have any provisions for creating joins. Therefore, it was not possible using the criteria API to create an exists subselect that had a join, even though running the source DetachedCriteria alone works perfectly. > For example, if this is the goal: > select * from foo f > where exists (select id from bar b join other o on b.o_id = o.id where o.prop = '123' and b.foo_id = f.id) > One might try something like this: > Criteria crit = session.createCriteria(Foo.class, fooAlias); > DetachedCriteria barCrit = DetachedCriteria.forClass(Bar.class, barAlias); > DetachedCriteria otherCrit = barCrit.createCriteria(Bar.OTHER_JOIN); > otherCrit.add( Restrictions.eq(Other.PROP, "123") ); > barCrit.add( Restrictions.eqProperty( -- props to join to foo here --) ); > barCrit.setProjection( Projections.id() ); > crit.add( Subqueries.exists(barCrit) ); > However, the existing code generates something like the following, which gets an error with an unknown alias 'o': > select * from foo f > where exists (select id from bar b where o.prop = '123' and b.foo_id = f.id) > This is also described here (at the end): http://forum.hibernate.org/viewtopic.php?t=942488 > The patch to SubqueryExpression.java fixes this to included the joins necessary for the filtering. This code was modeled (copied) off of code from CriteriaLoader. For me this works perfectly, but I don't understand the internals of this stuff enough to say how robust it is. Also included is a patch to the test case to enable testing of this, which was present but commented out. I did not change the contents of the test, which currently only attempts a joined subquery. This used to fail with an error, but now it works. The test does not check the results at all. (Inconsequential to the patch - Enrollment has two Ls.) > -----side notes > The patch file also has two other patches. The first increases the delay in BulkManipulationTest because I was getting inconsistent test results. I think that the precision on the version timestamp is not enough for 300 milliseconds delay to be enough to guarantee the test results. Also, in build.xml, there was a line that was meant to exclude the performance tests, but there was no **/*, on *, so they actually were not excluded. I changed this so the tests would complete in a reasonable amount of time. However, there is one other issue with testing that I worked around manually. After each test run, two databases (Users and Email) were left in the database. If I did not manually delete these then the number of failures on the next test run was different. This was really confusing until I figured it out because I was trying to make sure all the other testcases still passed with my patch, but even without the patch I was getting different results. -- 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

18 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-817) using projections is causing SQL query error on oracle (ORA-00904 error)

by Waldemar Prabucki (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-817?page=co... ] Waldemar Prabucki commented on HHH-817: --------------------------------------- I have simmilar problem with following query (@Hibernate 3.2.4sp1): "delete SupplierBO libo1 where libo.oid not in (select abbo.supplier.oid from PartBO abbo) and libo.oid not in (select pobo.supplier.oid from PotentialanalyseSourceBO pobo)". Everything is ok if there is only one condition either " libo.oid not in (select pobo.lieferwerk.oid from PotenzialanalyseQuelleBO pobo)" or "ibo.oid not in (select abbo.lieferwerk.oid from AbrufteilBO abbo)" but with both of them i run into ORA-00904: "SUPPLIER0_"."OID" from the second condition. I am new in Hibernate and I will be very thankful if anyone could suggets me some efficient and safe workaround to this. Is this published patch safe in this case? If yes could it have some negative effects on other hibernate components? > using projections is causing SQL query error on oracle (ORA-00904 error) > ------------------------------------------------------------------------ > > Key: HHH-817 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-817 > Project: Hibernate3 > Issue Type: Bug > Affects Versions: 3.0.5 > Environment: Oracle 9.2.0.6, Hibernate 3.0.5, Spring Framework 1.2.2 based application working on Jakarta Tomcat 5.0.28 > Reporter: Michal Jastak > Priority: Minor > Attachments: HHH-817.patch > > > following java code: > protected Entity loadEntityLightweight(Serializable entityId) throws DataAccessException { > Criteria criteria = getSession().createCriteria(Entity.class); > ProjectionList projectionList = Projections.projectionList(); > projectionList.add(Property.forName(BaseEntity.PROP_ID), BaseEntity.PROP_ID); > projectionList.add(Property.forName(BaseEntity.PROP_TYPE), BaseEntity.PROP_TYPE); > criteria.setProjection(projectionList); > criteria.add(Restrictions.eq(BaseEntity.PROP_ID, entityId)); > criteria.setResultTransformer(new AliasToBeanResultTransformer(Entity.class)); > return (Entity) criteria.uniqueResult(); > } > generates following SQL query: > select this_.id as y0_, this_.type as y1_ from entities this_ left outer join facilities this_1_ on this_.id=this_1_.id left outer join users this_2_ on this_.id=this_2_.id left outer join addresses address2_ on this_.address_id=address2_.id left outer join entities entity3_ on this_2_.employer_id=entity3_.id left outer join facilities entity3_1_ on entity3_.id=entity3_1_.id left outer join users entity3_2_ on entity3_.id=entity3_2_.id where y0_=? > y0_ = ? expression in where clause is causing a 904 error on Oracle 9: > ORA-00904: "Y0_": invalid identifier > hibernate dialect: org.hibernate.dialect.Oracle9Dialect > mapping for Entity class: > <?xml version="1.0"?> > <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" > "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> > <hibernate-mapping default-lazy="false" default-cascade="save-update"> > > <class name="Entity" table="entities" mutable="true"> > <id name="id" type="java.lang.Long" unsaved-value="null"> > <generator class="sequence"> > <param name="sequence">entities_id_seq</param> > </generator> > </id> > <many-to-one name="address" class="Address" column="address_id" /> > ... >  > <joined-subclass name="Facility" table="facilities"> > <key column="id" /> > ... > <set name="users" inverse="true" lazy="true"> > <key column="facility_id" /> > <one-to-many class="User" /> > </set> > </joined-subclass> >  > <joined-subclass name="User" table="users" dynamic-insert="true" dynamic-update="true"> > <key column="id" /> > <many-to-one name="employer" class="Entity" column="employer_id" cascade="none" /> > ... > <set name="userAuthorities" inverse="true" cascade="all-delete-orphan"> > <key column="user_id" /> > <one-to-many class="Authority" /> > </set> > </joined-subclass> > </class> > </hibernate-mapping> -- 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

18 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-624) Autodiscover all @Entity-annotated Classes

by James Carman (JIRA)

Autodiscover all @Entity-annotated Classes ------------------------------------------ Key: ANN-624 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-624 Project: Hibernate Annotations Issue Type: New Feature Reporter: James Carman The EntityManager implementation contains an "autodiscovery" feature that would be nice to have added to the core Hibernate library. Maybe we could add an AnnotationConfiguration.addAutodiscoveredEntities() method? -- 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

18 years, 6 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2670) Allow proxy classes to be passed in to API methods

by Mike Quilleash (JIRA)

Allow proxy classes to be passed in to API methods -------------------------------------------------- Key: HHH-2670 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2670 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.1 Environment: Any Reporter: Mike Quilleash Specifically session.get() sessionFactory.getClassMetadata() At the moment if you have a proxy object and do the following session.get( proxyObject.getClass(), id ); You'll get an exception because it just does .getName() on the class. Ideally all the hibernate APIs should handle proxy classes being passed in and normalise them to the base class. -- 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

18 years, 6 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2671) Add a method of getting the entity class from a proxy class

by Mike Quilleash (JIRA)

Add a method of getting the entity class from a proxy class ----------------------------------------------------------- Key: HHH-2671 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2671 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.1 Environment: Any Reporter: Mike Quilleash Currently you can get the object class from a proxy object by calling Hibernate.getClass( proxyObject ). A method for getting the object class from a proxy class would also be useful. Contrived example. Hibernate.getClass( proxyObject.getClass() ) OR Hibernate.getClass( proxyClass ) So if I did Hibenerate.getClass( obj1.getObj2().getClass() ) the class of the Obj2 relationship would be returned rather than the proxy class. -- 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

18 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HBX-739) APT ProcessorFactory for @Entity Annotations

by James Carman (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-739?page=co... ] James Carman commented on HBX-739: ---------------------------------- It would be nice if the autodiscovery stuff was brought down into Hibernate from the EntityManager implementation. Maybe add a method like AnnotationConfiguration.addAutodiscoveredEntities()? > APT ProcessorFactory for @Entity Annotations > -------------------------------------------- > > Key: HBX-739 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-739 > Project: Hibernate Tools > Issue Type: New Feature > Reporter: James Carman > Priority: Minor > Attachments: ConfigFileProcessorFactory.java > > > Please provide an APT ProcessorFactory which looks for all @Entity annotations in a source directory and creates a hibernate.cfg.xml file which contains mapping entries for each class found with an @Entity annotation. -- 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

18 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues June 2007