hibernate-issues — Hibernate JIRA Notifications

[Hibernate-issues] [Hibernate-JIRA] Updated: (ANN-39) @CollectionId for idbags

[Emmanuel B. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/ANN-39?page=all ]

Emmanuel Bernard updated ANN-39:
--------------------------------

    Fix Version: 3.2.0

> @CollectionId for idbags
> ------------------------
>
>          Key: ANN-39
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-39
>      Project: Hibernate Annotations
>         Type: Improvement

>   Components: binder
>     Versions: 3.1beta3
>     Reporter: Emmanuel Bernard
>     Assignee: Emmanuel Bernard
>     Priority: Blocker
>      Fix For: 3.2.0

>
>
> @CollectionId(generator, params={@Parameter})
> for idbags

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (ANN-39) @CollectionId for idbags

[Christian B. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/ANN-39?page=all ]

Christian Bauer updated ANN-39:
-------------------------------

    Priority: Blocker  (was: Trivial)

Currently on-site, customer absolutely needs this to represent many-to-many with components (the usual "extra columns on join table" problem), and a surrogate PK column. It's actually the last important missing feature in HAN. Please consider for final release.


> @CollectionId for idbags
> ------------------------
>
>          Key: ANN-39
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-39
>      Project: Hibernate Annotations
>         Type: Improvement

>   Components: binder
>     Versions: 3.1beta3
>     Reporter: Emmanuel Bernard
>     Assignee: Emmanuel Bernard
>     Priority: Blocker

>
>
> @CollectionId(generator, params={@Parameter})
> for idbags

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HBX-666) generics not used when overriding Bag implementation from Collection type to List

[Chris K. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HBX-666?page=comments#action_23150 ] 

Chris Koch commented on HBX-666:
--------------------------------

related to this issue where Max suggested a jira issue was created

http://forum.hibernate.org/viewtopic.php?p=2306812#2306812

> generics not used when overriding Bag implementation from Collection type to List
> ---------------------------------------------------------------------------------
>
>          Key: HBX-666
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-666
>      Project: Hibernate Tools
>         Type: Improvement

>   Components: hbm2java
>     Versions: 3.1alpha5
>  Environment: hibernate 3.0.5, htools 3.1.5
>     Reporter: Chris Koch

>
>
> when overriding the Bag implementation from Collection type to java.util.List using the <meta attribute="property-type">java.util.List</meta>, generics are not generated for the List.  It'd be nice to be able to keep generics.

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HBX-666) generics not used when overriding Bag implementation from Collection type to List

[Chris K. (JIRA) <no...@at...>]

generics not used when overriding Bag implementation from Collection type to List
---------------------------------------------------------------------------------

         Key: HBX-666
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-666
     Project: Hibernate Tools
        Type: Improvement

  Components: hbm2java  
    Versions: 3.1alpha5    
 Environment: hibernate 3.0.5, htools 3.1.5
    Reporter: Chris Koch


when overriding the Bag implementation from Collection type to java.util.List using the <meta attribute="property-type">java.util.List</meta>, generics are not generated for the List.  It'd be nice to be able to keep generics.

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

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

[Erik K. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-952?page=comments#action_23149 ] 

Erik Kimmel commented on HHH-952:
---------------------------------

I tested the patch with v313 and all seems to be OK.

> 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
>         Type: Patch

>   Components: core
>     Versions: 3.1 beta 1, 3.1 beta 2
>  Environment: 3.1beta1 with MS SQL 2000 via jTDS
>     Reporter: John
>     Priority: Critical
>  Attachments: SubqueryExpression.java, subquery-patch-311.txt, subquery-patch-31beta3.txt, subquery-patch.txt, subquery-patch.txt
>
>
> 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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1293) java.lang.NoSuchMethodError: <persistent class>.getHibernateLazyInitializer()

[Britt P. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1293?page=comments#action_23148 ] 

Britt Park commented on HHH-1293:
---------------------------------

The same problem exists with Mac OS X's jdk1.5_06 on intel.  The same -server workaround works.  I'd guess that means that Apple is basing the intel JVM off of the linux source base.

> java.lang.NoSuchMethodError: <persistent class>.getHibernateLazyInitializer()
> -----------------------------------------------------------------------------
>
>          Key: HHH-1293
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1293
>      Project: Hibernate3
>         Type: Bug

>     Versions: 3.1.1
>     Reporter: Andreas Schildbach
>     Priority: Blocker
>  Attachments: manysessions.tgz
>
>
> As documented in
> http://forum.hibernate.org/viewtopic.php?t=940119
> some people (including me) are getting this exception with the final release of Hibernate 3.1:
> java.lang.NoSuchMethodError: de.schildbach.game.integration.HibernateGamePlayer.getHibernateLazyInitializer()Lorg/hibernate/proxy/LazyInitializer;
>         at de.schildbach.game.integration.HibernateGamePlayer$$EnhancerByCGLIB$$afecb986.getHibernateLazyInitializer(<generated>)
>         at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:274)
>         at org.hibernate.type.ManyToOneType.assemble(ManyToOneType.java:177)
>         at org.hibernate.type.TypeFactory.assemble(TypeFactory.java:398)
>         at org.hibernate.cache.entry.CacheEntry.assemble(CacheEntry.java:96)
>         at org.hibernate.cache.entry.CacheEntry.assemble(CacheEntry.java:82)
>         at org.hibernate.event.def.DefaultLoadEventListener.assembleCacheEntry(DefaultLoadEventListener.java:520)
>         at org.hibernate.event.def.DefaultLoadEventListener.loadFromSecondLevelCache(DefaultLoadEventListener.java:474)
>         at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:328)
>         at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:123)
>         at org.hibernate.event.def.DefaultLoadEventListener.returnNarrowedProxy(DefaultLoadEventListener.java:202)
>         at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:169)
>         at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:87)
>         at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:869)
>         at org.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:838)
>         at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:266)
>         at org.hibernate.type.ManyToOneType.assemble(ManyToOneType.java:177)
>         at org.hibernate.collection.PersistentList.initializeFromCache(PersistentList.java:378)
>         at org.hibernate.cache.entry.CollectionCacheEntry.assemble(CollectionCacheEntry.java:35)
>         at org.hibernate.event.def.DefaultInitializeCollectionEventListener.initializeCollectionFromCache(DefaultInitializeCollectionEventListener.java:130)
>         at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:48)
>         at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1627)
>         at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:344)
>         at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86)
>         at org.hibernate.collection.AbstractPersistentCollection.readSize(AbstractPersistentCollection.java:109)
>         at org.hibernate.collection.PersistentList.size(PersistentList.java:91)
> The exception varies with the actual persistent class in use. Most people seem to be using JDK 1.5 and Linux. Some reports say that the exception does not happen from the very start of the application, but it takes "several invocations"/"some time" until it appear, but then it appears very often.

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1775) collection batch fetching

[Steve E. (JIRA) <no...@at...>]

collection batch fetching
-------------------------

         Key: HHH-1775
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1775
     Project: Hibernate3
        Type: Improvement

  Components: core  
    Reporter: Steve Ebersole
 Assigned to: Steve Ebersole 
    Priority: Minor
     Fix For: 3.2.0


I have code local on my box to support "peeking" into the second level cache when determining whether to add a particular entity/collection key to a batch load request.  If the given key is contained in the second level cache, then do not batch fetch the entity/collection as it will be initialized from second level cache on access.

However, there are still large inefficiencies when performing this for collections; the biggest of which currently is the fact that we retreive a IdentityMap.entrySet for each and ever call to determine a collectiomn fetch batch.  For performance reasons, we should align this with how entity batches are handled where the entity keys considered to be "batch loadable" are tracked seperately on the BatchFetchQueue.

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1774) Wrong SQL generated from a composite-id HQL.

[Regis P. M. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1774?page=comments#action_23147 ] 

Regis Pires Magalhaes commented on HHH-1774:
--------------------------------------------

Sorry, priority is not Blocker. Can someone change this?


> Wrong SQL generated from a composite-id HQL.
> --------------------------------------------
>
>          Key: HHH-1774
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1774
>      Project: Hibernate3
>         Type: Bug

>   Components: query-hql
>     Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2
>  Environment: Hibernate 3.1.3 / 3.2.0 cr1 / 3.2.9 cr2
> Database: PostgreSQL 8.0 and Oracle 7.3.4
>     Reporter: Regis Pires Magalhaes
>     Priority: Blocker

>
>
> Hibernate is generating a wrong SQL related to a composite-id HQL.
> The details of the problem are described below...
> MAPPING:
> <hibernate-mapping>
>     <class name="Cobrador" table="cobrador">
>    <composite-id name="id" class="CobradorId">
>       <key-property name="empresa"/>
>       <key-property name="matricula"/>
>    </composite-id>
>         <property name="nome" type="string"/>
>     </class>
> </hibernate-mapping>
> HQL:
> from Cobrador cobrador
> where cobrador = :cobrador
> GENERATED SQL:
> select cobrador0_.empresa as empresa3_,
>        cobrador0_.matricula as matricula3_,
>        cobrador0_.nome as nome3_,
> from cobrador cobrador0_
> where (cobrador0_.empresa, cobrador0_.matricula)=?
> PARAMETERS BINDING:
> DEBUG 13/05/2006 10:32:18 [org.hibernate.type.IntegerType:80] - binding '1' to parameter: 1
> DEBUG 13/05/2006 10:32:18 [org.hibernate.type.IntegerType:80] - binding '1234' to parameter: 2
> Note that 2 parameters are binded, but there is just a single parameter in the generated SQL.
> DATABASE EXCEPTION:
> org.postgresql.util.PSQLException: The column index is out of range: 2, number of columns: 1
> The generated SQL should be:
> select cobrador0_.empresa as empresa3_,
>        cobrador0_.matricula as matricula3_,
>        cobrador0_.nome as nome3_,
> from cobrador cobrador0_
> where (cobrador0_.empresa, cobrador0_.matricula)=(?, ?)

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1774) Wrong SQL generated from a composite-id HQL.

[Regis P. M. (JIRA) <no...@at...>]

Wrong SQL generated from a composite-id HQL.
--------------------------------------------

         Key: HHH-1774
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1774
     Project: Hibernate3
        Type: Bug

  Components: query-hql  
    Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2    
 Environment: Hibernate 3.1.3 / 3.2.0 cr1 / 3.2.9 cr2
Database: PostgreSQL 8.0 and Oracle 7.3.4

    Reporter: Regis Pires Magalhaes
    Priority: Blocker


Hibernate is generating a wrong SQL related to a composite-id HQL.
The details of the problem are described below...

MAPPING:
<hibernate-mapping>
    <class name="Cobrador" table="cobrador">
   <composite-id name="id" class="CobradorId">
      <key-property name="empresa"/>
      <key-property name="matricula"/>
   </composite-id>
        <property name="nome" type="string"/>
    </class>
</hibernate-mapping>

HQL:
from Cobrador cobrador
where cobrador = :cobrador

GENERATED SQL:
select cobrador0_.empresa as empresa3_,
       cobrador0_.matricula as matricula3_,
       cobrador0_.nome as nome3_,
from cobrador cobrador0_
where (cobrador0_.empresa, cobrador0_.matricula)=?

PARAMETERS BINDING:
DEBUG 13/05/2006 10:32:18 [org.hibernate.type.IntegerType:80] - binding '1' to parameter: 1
DEBUG 13/05/2006 10:32:18 [org.hibernate.type.IntegerType:80] - binding '1234' to parameter: 2

Note that 2 parameters are binded, but there is just a single parameter in the generated SQL.

DATABASE EXCEPTION:
org.postgresql.util.PSQLException: The column index is out of range: 2, number of columns: 1

The generated SQL should be:
select cobrador0_.empresa as empresa3_,
       cobrador0_.matricula as matricula3_,
       cobrador0_.nome as nome3_,
from cobrador cobrador0_
where (cobrador0_.empresa, cobrador0_.matricula)=(?, ?)



-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Resolved: (HHH-1773) Typo in ImprovedNamingStrategy

[Emmanuel B. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1773?page=all ]
     
Emmanuel Bernard resolved HHH-1773:
-----------------------------------

    Fix Version: 3.2.0
     Resolution: Fixed
      Assign To: Emmanuel Bernard

thanks

> Typo in ImprovedNamingStrategy
> ------------------------------
>
>          Key: HHH-1773
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1773
>      Project: Hibernate3
>         Type: Improvement

>   Components: core
>     Versions: 3.2.0.cr2
>     Reporter: Christopher G. Stach II
>     Assignee: Emmanuel Bernard
>     Priority: Trivial
>      Fix For: 3.2.0

>
> Original Estimate: 1 minute
>         Remaining: 1 minute
>
> 		if (header == null) throw new AssertionFailure("NammingStrategy not properly filled");

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-281) ".class" with <joined-subclass> problem

[Den R. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HB-281?page=comments#action_23145 ] 

Den Raskovalov commented on HB-281:
-----------------------------------

Gavin, suggest better way to extract class for several objects, without its creating? I need to create some cache of class info for hierarchies of more 1000000 objects.

> ".class" with <joined-subclass> problem
> ---------------------------------------
>
>          Key: HB-281
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-281
>      Project: Hibernate2
>         Type: Bug

>   Components: core
>  Environment: windows 2000
>     Reporter: Simone Ricciardi
>     Priority: Minor

>
>
> I've acknowledged an error that happens using "select count (*) ..." 
> together to a where clause "... where alias.class = ClassName ". 
> Suppose to have two classes: 
> public class Foo
> {
> String id;
> String attr1;
> public String getId(){ return id; }
> public void setId(String id){ this.id = id; }
> public String getAttr1(){ return attr1; }
> public void setAttr1(String attr1){ this.attr1 = attr1; }
> }
> public class Bar extends Foo
> {
> String attr2;
> public String getAttr2(){ return attr2; }
> public void setAttr2(String attr2){ this.attr2 = attr2; }
> }
> and the corresponding mapping file: 
> <hibernate-mapping>
> <class name="test.persistents.Foo" table="Foo">
> <id name="id" type="string">
> <column name="id" length="32"/>
> <generator class="uuid.hex"/>
> </id>
> <property name="attr1" column="attr1" type="string"/>
> <joined-subclass name="test.persistents.Bar" table="Bar">
> <key column="foo_id"/>
> <property name="attr2" column="attr2" type="string"/>
> </joined-subclass>
> </class>
> </hibernate-mapping>
> When I try to make the following query: 
> Query query = session.createQuery("select count(*) from Foo foo where foo.class = Foo"); 
> I get an error of this type:
> java.sql.SQLException: General error, message from server: "Unknown table 'foo0__1' in where clause"
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1651)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:889)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:956)
> at com.mysql.jdbc.Connection.execSQL(Connection.java:1874)
> at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1538)
> at com.p6spy.engine.logging.P6LogPreparedStatement.executeQuery(P6LogPreparedStatement.java:171)
> at net.sf.hibernate.impl.BatcherImpl.getResultSet(BatcherImpl.java:71)
> at net.sf.hibernate.loader.Loader.getResultSet(Loader.java:551)
> at net.sf.hibernate.loader.Loader.doFind(Loader.java:140)
> at net.sf.hibernate.loader.Loader.find(Loader.java:620)
> at net.sf.hibernate.hql.QueryTranslator.find(QueryTranslator.java:928)
> at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1343)
> at net.sf.hibernate.impl.QueryImpl.list(QueryImpl.java:76)
> at test.Test.main(Test.java:42)
> 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:324)
> while if I perform the same query without the select count(*) (select foo from Foo foo where foo.class = Foo) 
> all works fine.
> Comparing the two queries produced by hibernate in both cases, 
> it seems that the error derives from the lack of the "left outer join" with the Bar table in the "from" clause:
> with select count(*):
> select count(*) as x0_0_ 
> from Foo foo0_ 
> where (case when foo0__1.foo_id is not null then 1 when foo0_.id is not null then 0 end=0 )
> without select count(*):
> select foo0_.id as id, 
> case when foo0__1.foo_id is not null then 1 
> when foo0_.id is not null then 0 end 
> as clazz_, 
> foo0_.attr1 as attr10_, 
> foo0__1.attr2 as attr21_ 
> from Foo foo0_ left outer join Bar foo0__1 on foo0_.id=foo0__1.foo_id 
> where (case when foo0__1.foo_id is not null then 1 when foo0_.id is not null then 0 end=0 )
> in fact the query should be the following:
> select count(*) as x0_0_ 
> from Foo foo0_ left outer join Bar foo0__1 on foo0_.id=foo0__1.foo_id 
> where (case when foo0__1.foo_id is not null then 1 when foo0_.id is not null then 0 end=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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1773) Typo in ImprovedNamingStrategy

[Christopher G. S. II (JIRA) <no...@at...>]

Typo in ImprovedNamingStrategy
------------------------------

         Key: HHH-1773
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1773
     Project: Hibernate3
        Type: Improvement

  Components: core  
    Versions: 3.2.0.cr2    
    Reporter: Christopher G. Stach II
    Priority: Trivial


		if (header == null) throw new AssertionFailure("NammingStrategy not properly filled");


-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HHH-1772) SchemaUpdate creates a sequence with error: java.sql.SQLException: ERROR: relation "rbrsequence" already exists

[Wojciech M. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1772?page=all ]

Wojciech Matysik updated HHH-1772:
----------------------------------

    Attachment: applicationContext-jdbc.xml

Schema update is enabled

> SchemaUpdate creates a sequence with error: java.sql.SQLException: ERROR: relation "rbrsequence" already exists
> ---------------------------------------------------------------------------------------------------------------
>
>          Key: HHH-1772
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1772
>      Project: Hibernate3
>         Type: Bug

>     Versions: 3.1.3
>  Environment: Spring 1.2.6, Hibernate 3.1.3, PostgreSQL driver 8.0-314, JBoss 4.0.3, Windows XP
>     Reporter: Wojciech Matysik
>  Attachments: ClaimDocument.hbm.xml, applicationContext-jdbc.xml, applicationContext-jdbc.xml
>
>
> I'v created HBM with id generator section:
>     <id column="ID" access="property" name="id">
>       <generator class="native">
>         <param name="sequence">rbrSequence</param>
>         <param name="schema">rbr</param>
>       </generator>
>     </id>
> SchemaUpdate is enabled. Following code inside org.springframework.orm.hibernate3.LocalSessionFactoryBean
> tries to invoke hibernate code:
> -----------------------------------------------------------------------------------------------
> import org.hibernate.Session;
> import org.hibernate.SessionFactory;
> import org.hibernate.cfg.Configuration;
> import org.hibernate.cfg.NamingStrategy;
> import org.hibernate.dialect.Dialect;
> import org.hibernate.tool.hbm2ddl.DatabaseMetadata;
> import java.sql.Connection;
> import java.sql.SQLException;
> import java.sql.Statement;
> ...
> public void updateDatabaseSchema() throws HibernateException {
> ...
>   Connection con = session.connection();
>   final Dialect dialect = Dialect.getDialect(configuration.getProperties());
>   DatabaseMetadata metadata = new DatabaseMetadata(con, dialect);
>   String[] sql = configuration.generateSchemaUpdateScript(dialect, metadata);
>   executeSchemaScript(con, sql);
> ...
> }
> -----------------------------------------------------------------------------------------------
> where sql variable is:    create sequence rbr.rbrSequence
> The method: executeSchemaScript throws exception:
> java.sql.SQLException: ERROR: relation "rbrsequence" already exists
> The problem is: rbrsequence has been created earlier, SchemaUpdate doesn't recognize it, and tries to create the same sequence again (I think that the schema parameter inside the generator params mislead SchemaUpdate). Other parts of Hibernate works properly.

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1772) SchemaUpdate creates a sequence with error: java.sql.SQLException: ERROR: relation "rbrsequence" already exists

[Wojciech M. (JIRA) <no...@at...>]

SchemaUpdate creates a sequence with error: java.sql.SQLException: ERROR: relation "rbrsequence" already exists
---------------------------------------------------------------------------------------------------------------

         Key: HHH-1772
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1772
     Project: Hibernate3
        Type: Bug

    Versions: 3.1.3    
 Environment: Spring 1.2.6, Hibernate 3.1.3, PostgreSQL driver 8.0-314, JBoss 4.0.3, Windows XP
    Reporter: Wojciech Matysik
 Attachments: ClaimDocument.hbm.xml, applicationContext-jdbc.xml

I'v created HBM with id generator section:

    <id column="ID" access="property" name="id">
      <generator class="native">
        <param name="sequence">rbrSequence</param>
        <param name="schema">rbr</param>
      </generator>
    </id>

SchemaUpdate is enabled. Following code inside org.springframework.orm.hibernate3.LocalSessionFactoryBean
tries to invoke hibernate code:

-----------------------------------------------------------------------------------------------
import org.hibernate.Session;
import org.hibernate.SessionFactory;
import org.hibernate.cfg.Configuration;
import org.hibernate.cfg.NamingStrategy;
import org.hibernate.dialect.Dialect;
import org.hibernate.tool.hbm2ddl.DatabaseMetadata;
import java.sql.Connection;
import java.sql.SQLException;
import java.sql.Statement;
...
public void updateDatabaseSchema() throws HibernateException {
...
  Connection con = session.connection();
  final Dialect dialect = Dialect.getDialect(configuration.getProperties());
  DatabaseMetadata metadata = new DatabaseMetadata(con, dialect);
  String[] sql = configuration.generateSchemaUpdateScript(dialect, metadata);
  executeSchemaScript(con, sql);
...
}
-----------------------------------------------------------------------------------------------

where sql variable is:    create sequence rbr.rbrSequence

The method: executeSchemaScript throws exception:
java.sql.SQLException: ERROR: relation "rbrsequence" already exists

The problem is: rbrsequence has been created earlier, SchemaUpdate doesn't recognize it, and tries to create the same sequence again (I think that the schema parameter inside the generator params mislead SchemaUpdate). Other parts of Hibernate works properly.


-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1771) Broken Column Mapping on one-to-one with foreign-key

[ron p. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1771?page=comments#action_23143 ] 

ron piterman commented on HHH-1771:
-----------------------------------

It is now (to me) that the one-to-one is not possible, changed to many-to-one and it works.

PLEASE CLOSE.

> Broken Column Mapping on one-to-one with foreign-key
> ----------------------------------------------------
>
>          Key: HHH-1771
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1771
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.1.3
>     Reporter: ron piterman
>  Attachments: bug.zip
>
>
> Here are the exception and the files:
> ( added comments on the xml to ease reading )
> org.hibernate.MappingException: broken column mapping for: parentStateState.state of: com.pvs.pmm.client.state.StateNodeImpl
> 	at org.hibernate.persister.entity.AbstractPropertyMapping.initPropertyPaths(AbstractPropertyMapping.java:122)
> 	at org.hibernate.persister.entity.AbstractPropertyMapping.initIdentifierPropertyPaths(AbstractPropertyMapping.java:183)
> 	at org.hibernate.persister.entity.AbstractPropertyMapping.initPropertyPaths(AbstractPropertyMapping.java:160)
> 	at org.hibernate.persister.entity.AbstractEntityPersister.initOrdinaryPropertyPaths(AbstractEntityPersister.java:1585)
> 	at org.hibernate.persister.entity.AbstractEntityPersister.initPropertyPaths(AbstractEntityPersister.java:1613)
> 	at org.hibernate.persister.entity.AbstractEntityPersister.postConstruct(AbstractEntityPersister.java:2610)
> 	at org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:386)
> 	at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:55)
> <class name="StateNodeState">
>   <composite-id name="id">
>     <key-many-to-one name="parentNode"/> <!-- class="StateNodeImpl" -->
>     <key-property name="stateName"/> <!-- type="String"-->
>   </composite-id>
>   <one-to-one name="state" foreign-key="state" class="StateNodeImpl"/>
> </class>
> public class StateNodeState {
> 	
> 	private StateNodeStatePK id;
> 	private StateNodeImpl state;
> // here come setters and getters...
> // ...
> }
> public class StateNodeStatePK implements Serializable {
> 	
> 	private StateNodeImpl parentNode;
> 	private String stateName;
> // here come setters and getters...
> // ...
> }
> <class name="StateNodeImpl" table="StateNode">
>   <id name="id"> <!-- Long -->
>     <generator class="foreign">
> 	<param name="property">parentStateState</param>
>     </generator>
>   </id>
>   <property name="stateName"/>
>   <property name="stateValue"/>
>   <one-to-one name="parentStateState" property-ref="state"/> <!-- class=StateNodeState -->
>   <many-to-one name="parentState"/> <!-- class="StateNodeImpl" -->
> </class>
> public class StateNodeImpl {
> 	private Long id;
> 	private String stateName;
> 	private Long stateValue;
> 	
> 	private StateNodeImpl parentState;
> 	private StateNodeState parentStateState;
>   // here comes auto generated setters and getters...
>   // ...
> }
> ---
> I also tried without it without the <generator class="foreign"> and the reverse one-to-one from StateNode to StateNodeState, the result was the same.

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1771) Broken Column Mapping on one-to-one with foreign-key

[ron p. (JIRA) <no...@at...>]

Broken Column Mapping on one-to-one with foreign-key
----------------------------------------------------

         Key: HHH-1771
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1771
     Project: Hibernate3
        Type: Bug

  Components: core  
    Versions: 3.1.3    
    Reporter: ron piterman
 Attachments: bug.zip

Here are the exception and the files:
( added comments on the xml to ease reading )

org.hibernate.MappingException: broken column mapping for: parentStateState.state of: com.pvs.pmm.client.state.StateNodeImpl
	at org.hibernate.persister.entity.AbstractPropertyMapping.initPropertyPaths(AbstractPropertyMapping.java:122)
	at org.hibernate.persister.entity.AbstractPropertyMapping.initIdentifierPropertyPaths(AbstractPropertyMapping.java:183)
	at org.hibernate.persister.entity.AbstractPropertyMapping.initPropertyPaths(AbstractPropertyMapping.java:160)
	at org.hibernate.persister.entity.AbstractEntityPersister.initOrdinaryPropertyPaths(AbstractEntityPersister.java:1585)
	at org.hibernate.persister.entity.AbstractEntityPersister.initPropertyPaths(AbstractEntityPersister.java:1613)
	at org.hibernate.persister.entity.AbstractEntityPersister.postConstruct(AbstractEntityPersister.java:2610)
	at org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:386)
	at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:55)

<class name="StateNodeState">
  <composite-id name="id">
    <key-many-to-one name="parentNode"/> <!-- class="StateNodeImpl" -->
    <key-property name="stateName"/> <!-- type="String"-->
  </composite-id>
  <one-to-one name="state" foreign-key="state" class="StateNodeImpl"/>
</class>

public class StateNodeState {
	
	private StateNodeStatePK id;
	private StateNodeImpl state;

// here come setters and getters...
// ...
}

public class StateNodeStatePK implements Serializable {
	
	private StateNodeImpl parentNode;
	private String stateName;
// here come setters and getters...
// ...
}


<class name="StateNodeImpl" table="StateNode">
  <id name="id"> <!-- Long -->
    <generator class="foreign">
	<param name="property">parentStateState</param>
    </generator>
  </id>
  <property name="stateName"/>
  <property name="stateValue"/>
  <one-to-one name="parentStateState" property-ref="state"/> <!-- class=StateNodeState -->
  <many-to-one name="parentState"/> <!-- class="StateNodeImpl" -->
</class>

public class StateNodeImpl {
	private Long id;
	private String stateName;
	private Long stateValue;
	
	private StateNodeImpl parentState;
	private StateNodeState parentStateState;
  // here comes auto generated setters and getters...
  // ...
}


---

I also tried without it without the <generator class="foreign"> and the reverse one-to-one from StateNode to StateNodeState, the result was the same.



-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1615) GROUP BY entity does not work

[Giampaolo T. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1615?page=comments#action_23141 ] 

Giampaolo Tomassoni commented on HHH-1615:
------------------------------------------

For another example of the very same problem, see: http://forum.hibernate.org/viewtopic.php?t=959692

> GROUP BY entity does not work
> -----------------------------
>
>          Key: HHH-1615
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1615
>      Project: Hibernate3
>         Type: Bug

>   Components: query-hql
>     Versions: 3.1.3
>  Environment: PostgreSQL 8.1.3, Hibernate 3.1.3
>     Reporter: Xavier Bugaud

>
>
> The query : "select cat, count(*) from Cat cat group by cat" does not work.
> ERROR: column "xxxx" must appear in the GROUP BY clause or be used in an aggregate function
> See :
>  - http://forum.hibernate.org/viewtopic.php?t=953716
>  - http://jira.nhibernate.org/browse/NH-528

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1646) Bad code in FastClass.equals

[Greg M. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1646?pa=
ge=3Dcomments#action_23140 ]=20

Greg Matthews commented on HHH-1646:
------------------------------------

You don't strictly really need the null check either. The instanceof operat=
or handles null. i.e. the following will work just fine.

if(o instanceof FastClass) {
  return this.type.equals(((FastClass)o).type);
}
return false;  // if o is null, we'll return false

> Bad code in FastClass.equals
> ----------------------------
>
>          Key: HHH-1646
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/H=
HH-1646
>      Project: Hibernate3
>         Type: Bug

>     Versions: 3.1.3, 3.2.0 cr1
>  Environment: 3.2.0
>     Reporter: Niels Harremo=C3=ABs
>     Priority: Blocker
>  Attachments: FastClass.patch
>
> Original Estimate: 3 minutes
>         Remaining: 3 minutes
>
> In FastClass, the equals method is:
>   public boolean equals(Object o) {
>     if ( o =3D=3D null || ( o instanceof FastClass ) ) {
>       return false;
>     }
>     return this.type.equals( ( ( FastClass ) o ).type );
> }
> There's a missing ! - the first line should be=20
>  if ( o =3D=3D null ||  !  ( o instanceof FastClass ) ) {

--=20
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=
.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HBX-665) add 'exclude' option to 'foreign-key' element

[Sung Oh (JIRA) <no...@at...>]

add 'exclude' option to 'foreign-key' element
---------------------------------------------

         Key: HBX-665
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-665
     Project: Hibernate Tools
        Type: New Feature

  Components: reverse-engineer  
 Environment: Hibernate version: 3.1.3
Name and version of the database you are using: DB2 v8.1
hibernatetools version: 3.1.0.beta5 
    Reporter: Sung Oh


Add 'exclude' option for 'foreign-key' element.

<foreign-key constraint-name="oldname" exclude="true"/>

see this link : http://forum.hibernate.org/viewtopic.php?p=2306505#2306505

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1770) All event must inherit AbstractEvent

[Benjamin P. (JIRA) <no...@at...>]

All event must inherit AbstractEvent
------------------------------------

         Key: HHH-1770
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1770
     Project: Hibernate3
        Type: Patch

  Components: core  
    Versions: 3.2.0    
 Environment: Hibernate svn revision 9939
    Reporter: Benjamin Poussin
 Attachments: AbstractEvent-inheritance.patch

Some events inherit AbstractEvent (ex:PostLoadEvent) and other not  (ex:PostUpdateEvent). Some other rewrite some code from AbstractEvent to have Session (ex:PreInsertEvent).

I think all events must inherit AbstractEvent. With that all event have session associated and event is useable. Without Session event is not very usefull.

This patch do that, without modify other thing

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1700) HAVING clause not supported in Criteria API

[Manuel D. S. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1700?page=comments#action_23139 ] 

Manuel Dominguez Sarmiento commented on HHH-1700:
-------------------------------------------------

True, dumb mistake.  I didn't thoroughly test the code with aliases.

> HAVING clause not supported in Criteria API
> -------------------------------------------
>
>          Key: HHH-1700
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1700
>      Project: Hibernate3
>         Type: New Feature

>   Components: query-criteria
>     Versions: 3.1.3
>  Environment: Hibernate 3.1.3, Oracle 10g (not DB specific)
>     Reporter: Manuel Dominguez Sarmiento
>     Priority: Minor
>  Attachments: CustomProjections.java
>
> Original Estimate: 2 hours
>         Remaining: 2 hours
>
> Currently the Criteria API does not support the HAVING clause.  I have create a factory class which creates Projection instances using sqlGroupProjection.  Probably not the best approach, but an idea which could be further developed.  These factory methods could be included in the Projections factory class.
> Usage example w/one property:
> criteria.setProjection(CustomProjections.groupByHaving("id", Hibernate.LONG, "count(distinct id) >= 3"));
> Also allows aliases:
> criteria.setProjection(CustomProjections.groupByHaving("id", "idAlias", Hibernate.LONG, "count(distinct idAlias) >= 3"));
> Usage example w/many properties:
> String[] columns = new String[2];
> columns[0] = "id";
> columns[1] = "name";
> String[] aliases = new String[2];
> aliases[0] = "idAlias";
> aliases[1] = "nameAlias";
> Type[] types = new Type[2];
> types[0] = Hibernate.LONG;
> types[1] = Hibernate.STRING;
> criteria.setProjection(CustomProjections.groupByHaving(columns, aliases, types, "count(distinct id) >= 3 and name='george'"));

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HHH-1646) Bad code in FastClass.equals

[Konstantin I. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1646?p=
age=3Dall ]

Konstantin Ignatyev updated HHH-1646:
-------------------------------------

    Attachment: FastClass.patch

Patch that implements that

> Bad code in FastClass.equals
> ----------------------------
>
>          Key: HHH-1646
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/H=
HH-1646
>      Project: Hibernate3
>         Type: Bug

>     Versions: 3.1.3, 3.2.0 cr1
>  Environment: 3.2.0
>     Reporter: Niels Harremo=C3=ABs
>     Priority: Blocker
>  Attachments: FastClass.patch
>
> Original Estimate: 3 minutes
>         Remaining: 3 minutes
>
> In FastClass, the equals method is:
>   public boolean equals(Object o) {
>     if ( o =3D=3D null || ( o instanceof FastClass ) ) {
>       return false;
>     }
>     return this.type.equals( ( ( FastClass ) o ).type );
> }
> There's a missing ! - the first line should be=20
>  if ( o =3D=3D null ||  !  ( o instanceof FastClass ) ) {

--=20
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=
.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HHH-1593) Infinite loop/StackOverflow when calling configuration.setListener(null)

[Konstantin I. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1593?page=all ]

Konstantin Ignatyev updated HHH-1593:
-------------------------------------

    Attachment: Configuration.patch

Patch to org.hibernate.cfg.Configuration

> Infinite loop/StackOverflow when calling configuration.setListener(null)
> ------------------------------------------------------------------------
>
>          Key: HHH-1593
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1593
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.1.3, 3.1
>     Reporter: Shawn Kerstetter
>  Attachments: Configuration.patch
>
>
> calling config.setListener(null) will result in an infinite loop.
> It's a one character problem/fix:
> 	public void setListener(String type, Object listener) {
> 		if ( listener == null ) {
> 			setListener( type, null ); //infinite recursion
> 		}
> should be:
> 	public void setListener(String type, Object listener) {
> 		if ( listener == null ) {
> 			setListeners( type, null ); //need the plural
> 		}

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1769) NullPointerException when try to session after commit

[Christian B. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1769?pa=
ge=3Dcomments#action_23136 ]=20

Christian Bauer commented on HHH-1769:
--------------------------------------

And use a final release, not some arbitrary release candidate.


> NullPointerException when try to session after commit
> -----------------------------------------------------
>
>          Key: HHH-1769
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/H=
HH-1769
>      Project: Hibernate3
>         Type: Bug

>     Versions: 3.1 rc3
>  Environment: postgresql8, jboss4.0.3SP1, unix (linux, os x)
>     Reporter: C=C3=A9dric Chantepie

>
>
> When trying to get entity by "load" on hibernate session, just after havi=
ng commit underlying transaction, and before closing session, a NullPointer=
Exception is thrown from Batcher (AbstractBatcher, BatchingBatcher) as conn=
ectionManager return a null connection so method "prepareQueryStatement" in=
 this batcher cannot work.
> It seems ok that it should not work after commit but I think a more expli=
cit exception should be provided in order to make debug more easy.
> ---
> hsession.saveOrUpdate(test);
> tx.commit();
> Test tsaved =3D hsession.load(Test.class, "pk"); // NullPointerException =
raises here
> hsession.close();

--=20
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=
.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1769) NullPointerException when try to session after commit

[Christian B. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1769?pa=
ge=3Dcomments#action_23135 ]=20

Christian Bauer commented on HHH-1769:
--------------------------------------

This worked perfectly fine for me last week when I was testing auto-commit =
mode, so you need to provide at least, an _isolated_ and _minimal_ test tha=
t shows the problem.


> NullPointerException when try to session after commit
> -----------------------------------------------------
>
>          Key: HHH-1769
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/H=
HH-1769
>      Project: Hibernate3
>         Type: Bug

>     Versions: 3.1 rc3
>  Environment: postgresql8, jboss4.0.3SP1, unix (linux, os x)
>     Reporter: C=C3=A9dric Chantepie

>
>
> When trying to get entity by "load" on hibernate session, just after havi=
ng commit underlying transaction, and before closing session, a NullPointer=
Exception is thrown from Batcher (AbstractBatcher, BatchingBatcher) as conn=
ectionManager return a null connection so method "prepareQueryStatement" in=
 this batcher cannot work.
> It seems ok that it should not work after commit but I think a more expli=
cit exception should be provided in order to make debug more easy.
> ---
> hsession.saveOrUpdate(test);
> tx.commit();
> Test tsaved =3D hsession.load(Test.class, "pk"); // NullPointerException =
raises here
> hsession.close();

--=20
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=
.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira