hibernate-issues — Hibernate JIRA Notifications

[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1894) moving child between parents in tree-like structure

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

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

Aaron Digulla commented on HHH-1894:
------------------------------------

To make this code work, just replace "all-delete-orphans" in the mapping file with "all".

But now, you have to manage orphans (objects which have been removed from the parent but not attached anywhere else), manually!

> moving child between parents in tree-like structure
> ---------------------------------------------------
>
>          Key: HHH-1894
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1894
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.1.3
>  Environment: HSQLDB 1.8.0.4
>     Reporter: Aaron Digulla
>  Attachments: parentchild.zip
>
>
> After asking in the forum, I was directed here. I'm not sure if the bug is in Hibernate or in my code. If it's in my code, I'd suggest to change this bug report into an enhancement request and add my code to the test suite of Hibernate as an example.
> Basically, I have a tree-like structure and I want to move a node between parents. Here is the implementation of Node.setParent():
>     public void setParent(Node parent)
>     {
> 	if (this.parent != null)
> 	    this.parent.getChildren().remove(this);
> 	
>         this.parent = parent;
>         
> 	if (this.parent != null)
> 	    this.parent.getChildren().add(this);
>     }
> When I try this, I get:
> org.hibernate.ObjectDeletedException: deleted object would be re-saved by cascade (remove deleted object from associations): [org.hibernate.parentchild.Node#2]
> in Session.flush().
> I tried many different ways to implement this (see the test case) but in the end, the only solution I found was to clone the child, delete it manually(!) and create a new object.
> This issue was discussed in the forum: http://forum.hibernate.org/viewtopic.php?t=961777
> This might be a regression from 3.0 (see issue HHH-273)

-- 
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-785) Persistence through cascading should have higher precedence than orphan-delete

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

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

Aaron Digulla commented on HHH-785:
-----------------------------------

Note: In HHH-1894, I have a much more simple case which is inside a transation, using non-detached objects and there, it doesn't work as well.

A pity.

> Persistence through cascading should have higher precedence than orphan-delete
> ------------------------------------------------------------------------------
>
>          Key: HHH-785
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-785
>      Project: Hibernate3
>         Type: Improvement

>   Components: core
>     Versions: 3.1 beta 1
>     Reporter: Christian Bauer

>
>
> A typical tree mapped using an adjacency list:
> <many-to-one name="parent" cascade="none"/>
> <set name="children" cascade="all, delete-orphan"/>
> A normal tree operation is moving a node:
> a.remove(b);
> c.add(b);
> This results in an exception, as Hibernate currently rates the delete-orphan as more important and warns that the node would become persistent again through cascading. However, this is the only way to implement relocation of a node in a tree without resorting to complex session coding. I argue that the "delete orphans" guarantee given in the mapping should not have precedence over the the actual non-orphaned persistent state in the Session.

-- 
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-1894) moving child between parents in tree-like structure

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

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1894?page=all ]
     
Christian Bauer resolved HHH-1894:
----------------------------------

    Resolution: Won't Fix

http://opensource.atlassian.com/projects/hibernate/browse/HHH-785

> moving child between parents in tree-like structure
> ---------------------------------------------------
>
>          Key: HHH-1894
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1894
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.1.3
>  Environment: HSQLDB 1.8.0.4
>     Reporter: Aaron Digulla
>  Attachments: parentchild.zip
>
>
> After asking in the forum, I was directed here. I'm not sure if the bug is in Hibernate or in my code. If it's in my code, I'd suggest to change this bug report into an enhancement request and add my code to the test suite of Hibernate as an example.
> Basically, I have a tree-like structure and I want to move a node between parents. Here is the implementation of Node.setParent():
>     public void setParent(Node parent)
>     {
> 	if (this.parent != null)
> 	    this.parent.getChildren().remove(this);
> 	
>         this.parent = parent;
>         
> 	if (this.parent != null)
> 	    this.parent.getChildren().add(this);
>     }
> When I try this, I get:
> org.hibernate.ObjectDeletedException: deleted object would be re-saved by cascade (remove deleted object from associations): [org.hibernate.parentchild.Node#2]
> in Session.flush().
> I tried many different ways to implement this (see the test case) but in the end, the only solution I found was to clone the child, delete it manually(!) and create a new object.
> This issue was discussed in the forum: http://forum.hibernate.org/viewtopic.php?t=961777
> This might be a regression from 3.0 (see issue HHH-273)

-- 
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-391) SecondaryTables not recognized when using JOINED inheritance

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

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

Sebastian Kirsch updated ANN-391:
---------------------------------

    Attachment: TestSecondaries.java

Added some more tests illustrating the problem and that simple workarounds fail.

> SecondaryTables not recognized when using JOINED inheritance
> ------------------------------------------------------------
>
>          Key: ANN-391
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-391
>      Project: Hibernate Annotations
>         Type: Bug

>     Versions: 3.1.0.Beta10, 3.2.0.cr1
>  Environment: Hibernate 3.2.0CR1; db is irrelevant, as the buildSessionFactory() fails.
>     Reporter: Sebastian Kirsch
>  Attachments: TestSecondaries.java, TestSecondaries.java
>
>
> The Configuration doesn't recognize secondary tables of a super class.
> Calling AnnotationConfiguration.buildSessionFactory fails, claiming that the secondary table used in the super class cannot be found in the subclass.
> Adding the secondary table to the subclass doesn't help either.
> See attached JUnit test 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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (ANN-391) SecondaryTables not recognized when using JOINED inheritance

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

SecondaryTables not recognized when using JOINED inheritance
------------------------------------------------------------

         Key: ANN-391
         URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-391
     Project: Hibernate Annotations
        Type: Bug

    Versions: 3.1.0.Beta10, 3.2.0.cr1    
 Environment: Hibernate 3.2.0CR1; db is irrelevant, as the buildSessionFactory() fails.
    Reporter: Sebastian Kirsch
 Attachments: TestSecondaries.java

The Configuration doesn't recognize secondary tables of a super class.
Calling AnnotationConfiguration.buildSessionFactory fails, claiming that the secondary table used in the super class cannot be found in the subclass.
Adding the secondary table to the subclass doesn't help either.

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

[Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1896) New delete method on org.hibernate.impl.SessionImpl

[Steven (JIRA) <no...@at...>]

New delete method on org.hibernate.impl.SessionImpl
---------------------------------------------------

         Key: HHH-1896
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1896
     Project: Hibernate3
        Type: New Feature

    Reporter: Steven
    Priority: Minor


There is no way to use a named query to perform deletions. SessionImpl.delete() only accepts hql strings for queries. There should be a delete method that accepts either a query ex: SessionImpl.delete(SessionImpl.getNamedQuery("stored.query.name")) or the name of a stored procedure SessionImpl.delete("stored.query.name").

Abstraction by use of named queries is a good goal as it keeps the queries out of the DAO logic.

-- 
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-1895) HqlSqlWalker throws NullPointerException with explicit joins and component mapping

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

HqlSqlWalker throws NullPointerException with explicit joins and component mapping
----------------------------------------------------------------------------------

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

    Versions: 3.1.3    
 Environment: Oracle 9i, Hibernate 3.1.3
    Reporter: Victor Suarez
    Priority: Minor


HqlSqlWalker throws a NPE if a explicit join is used with fields that are mapped with component mapping. If explicit join is removed and implicit join is used, the HQL works fine. This kind of problem didn't occur with Hibernate2.

Examples (hbm below): 
The query:
String query = "FROM " + Pais.class.getName() + " AS pais JOIN pais.metaInfo AS minfo WHERE minfo.activo = true";

fails with this stacktrace:

Exception in thread "main" java.lang.NullPointerException
   at org.hibernate.hql.ast.HqlSqlWalker.createFromJoinElement(HqlSqlWalker.java:317)
   at org.hibernate.hql.antlr.HqlSqlBaseWalker.joinElement(HqlSqlBaseWalker.java:3268)
   at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromElement(HqlSqlBaseWalker.java:3060)
   at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromElementList(HqlSqlBaseWalker.java:2938)
   at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromClause(HqlSqlBaseWalker.java:688)
   at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:544)
   at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:281)
   at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:229)
   at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:218)
   at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:158)
   at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:109)
   at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:75)
   at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:54)
   at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:71)
   at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:133)
   at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:112)
   at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1583)


This one works fine:
String query = "FROM " + Pais.class.getName() + " AS pais WHERE pais.metaInfo.activo = true";

With this behaviour, HQL seems not to be totally transparent to mappings.


Mapping file:
<hibernate-mapping>
   <class name="Pais" table="Paises" lazy="true">
      <id name="id" type="long" column="id">
         <generator class="increment"/>
      </id>
      <component name="metaInfo" class="MetaInfo">
         <property name="usuarioAlta" column="usuarioAltaMetaInfo" type="string" not-null="false"/>
         <property name="fechaBaja" column="fechaBajaMetaInfo" type="timestamp" not-null="false"/>
         <property name="fechaAlta" column="fechaAltaMetaInfo" type="timestamp" not-null="false"/>
         <property name="activo" column="activoMetaInfo" type="boolean" not-null="false"/>
         <property name="usuarioBaja" column="usuarioBajaMetaInfo" type="string" not-null="false"/>
      </component>
      <property name="nombre" column="nombre" type="string" not-null="true"/>
      <property name="codigo" column="codigo" type="string" not-null="false"/>
      
      <set name="localidades" access="field" inverse="true"
         cascade="all-delete-orphan" lazy="true" batch-size="5">
         <key column="pais" />
         <one-to-many class="Localidad"/>
      </set>

      <set name="provincias" access="field" inverse="true"
         cascade="all-delete-orphan" lazy="true" batch-size="5">
         <key column="pais" />
         <one-to-many class="Provincia"/>
      </set>
      
      <property name="codAS400" type="string" not-null="false"/>
   </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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1894) moving child between parents in tree-like structure

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

moving child between parents in tree-like structure
---------------------------------------------------

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

  Components: core  
    Versions: 3.1.3    
 Environment: HSQLDB 1.8.0.4
    Reporter: Aaron Digulla
 Attachments: parentchild.zip

After asking in the forum, I was directed here. I'm not sure if the bug is in Hibernate or in my code. If it's in my code, I'd suggest to change this bug report into an enhancement request and add my code to the test suite of Hibernate as an example.

Basically, I have a tree-like structure and I want to move a node between parents. Here is the implementation of Node.setParent():

    public void setParent(Node parent)
    {
	if (this.parent != null)
	    this.parent.getChildren().remove(this);
	
        this.parent = parent;
        
	if (this.parent != null)
	    this.parent.getChildren().add(this);
    }

When I try this, I get:

org.hibernate.ObjectDeletedException: deleted object would be re-saved by cascade (remove deleted object from associations): [org.hibernate.parentchild.Node#2]

in Session.flush().

I tried many different ways to implement this (see the test case) but in the end, the only solution I found was to clone the child, delete it manually(!) and create a new object.

This issue was discussed in the forum: http://forum.hibernate.org/viewtopic.php?t=961777

This might be a regression from 3.0 (see issue HHH-273)

-- 
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-879) Enable joining the same association twice with Criteria

[Aleksei V. (JIRA) <no...@at...>]

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

Aleksei Valikov commented on HHH-879:
-------------------------------------

The best solution I have found so far is to implement an analog to Criteria API which translates queries formulated with objects into HQL queries.
Almoust 1:1 with Criteria API, but produces HQL rather than SQL.

> Enable joining the same association twice with Criteria
> -------------------------------------------------------
>
>          Key: HHH-879
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-879
>      Project: Hibernate3
>         Type: Improvement

>   Components: core
>     Reporter: Vladimir Bayanov

>
>
> Make double joining the same association with Criteria.createCriteria possible. See: http://forum.hibernate.org/viewtopic.php?t=931249

-- 
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-1893) SYSDATE and SYSTIMESTAMP not working well with Hibernate 3.1.3 and Oracle 10.2.0.1

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

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

Christian Bauer commented on HHH-1893:
--------------------------------------

This is of course not a bug Next time, please do the search on the forum fi=
rst, as I did just now.=20

http://forum.hibernate.org/viewtopic.php?t=3D941520&highlight=3Dsysdate+cre=
atesqlquery



> SYSDATE and SYSTIMESTAMP not working well with Hibernate 3.1.3 and Oracle=
 10.2.0.1
> -------------------------------------------------------------------------=
---------
>
>          Key: HHH-1893
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/H=
HH-1893
>      Project: Hibernate3
>         Type: Bug

>   Components: query-sql
>     Versions: 3.1.3
>     Reporter: Nestor Bosc=C3=A1n
>     Priority: Minor

>
>
> Trying to use sysdate or systimestamp in SQL Queries with Oracle database=
.=20
> If I use sysdate Hibernate is not retrieving the hour, minute, second par=
t. I always get 12:00:00pm=20
> If I use systimestamp I get the following exception:=20
> org.hibernate.MappingException: No Dialect mapping for JDBC type: -101=20
> at org.hibernate.dialect.TypeNames.get(TypeNames.java:56)=20
> at org.hibernate.dialect.TypeNames.get(TypeNames.java:81)=20
> at org.hibernate.dialect.Dialect.getHibernateTypeName(Dialect.java:192)=
=20
> at org.hibernate.loader.custom.CustomLoader.getHibernateType(CustomLoader=
.java:161)=20
> at org.hibernate.loader.custom.CustomLoader.autoDiscoverTypes(CustomLoade=
r.java:131)=20
> at org.hibernate.loader.Loader.getResultSet(Loader.java:1678)=20
> at org.hibernate.loader.Loader.doQuery(Loader.java:662)=20
> at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loa=
der.java:224)=20
> at org.hibernate.loader.Loader.doList(Loader.java:2145)=20
> at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2029)=20
> at org.hibernate.loader.Loader.list(Loader.java:2024)=20
> at org.hibernate.loader.custom.CustomLoader.list(CustomLoader.java:111)=
=20
> at org.hibernate.impl.SessionImpl.listCustomQuery(SessionImpl.java:1655)=
=20
> at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:1=
42)=20
> at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:164)=20
> at org.hibernate.impl.AbstractQueryImpl.uniqueResult(AbstractQueryImpl.ja=
va:749)=20
> Hibernate version: 3.1.3=20
> Code between sessionFactory.openSession() and session.close():=20
> Session session =3D null;=20
> Date date;=20
> try=20
> {=20
> session =3D sessionFactory.openSession ();=20
> date =3D (Date) session.createSQLQuery ("SELECT SYSDATE CURRENT_DATE FROM=
 DUAL").uniqueResult ();=20
> }=20
> finally=20
> {=20
> try=20
> {=20
> if (session !=3D null) session.close ();=20
> }=20
> catch (HibernateException e2) {}=20
> }=20
> System.out.println (new SimpleDateFormat ("hh:mm:ss").format (date));=20
> Name and version of the database you are using: Oracle 10.2.0.1

--=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-1893) SYSDATE and SYSTIMESTAMP not working well with Hibernate 3.1.3 and Oracle 10.2.0.1

[<no...@at...>]

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

Nestor Bosc=C3=A1n commented on HHH-1893:
------------------------------------

I know this is not a support portal. But this is not a support question, TH=
IS IS A BUG in Hibernate 3.1.3 and I'm posting this bug in hope that somebo=
dy in the future can fix it so Hibernate can be a better product.

> SYSDATE and SYSTIMESTAMP not working well with Hibernate 3.1.3 and Oracle=
 10.2.0.1
> -------------------------------------------------------------------------=
---------
>
>          Key: HHH-1893
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/H=
HH-1893
>      Project: Hibernate3
>         Type: Bug

>   Components: query-sql
>     Versions: 3.1.3
>     Reporter: Nestor Bosc=C3=A1n
>     Priority: Minor

>
>
> Trying to use sysdate or systimestamp in SQL Queries with Oracle database=
.=20
> If I use sysdate Hibernate is not retrieving the hour, minute, second par=
t. I always get 12:00:00pm=20
> If I use systimestamp I get the following exception:=20
> org.hibernate.MappingException: No Dialect mapping for JDBC type: -101=20
> at org.hibernate.dialect.TypeNames.get(TypeNames.java:56)=20
> at org.hibernate.dialect.TypeNames.get(TypeNames.java:81)=20
> at org.hibernate.dialect.Dialect.getHibernateTypeName(Dialect.java:192)=
=20
> at org.hibernate.loader.custom.CustomLoader.getHibernateType(CustomLoader=
.java:161)=20
> at org.hibernate.loader.custom.CustomLoader.autoDiscoverTypes(CustomLoade=
r.java:131)=20
> at org.hibernate.loader.Loader.getResultSet(Loader.java:1678)=20
> at org.hibernate.loader.Loader.doQuery(Loader.java:662)=20
> at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loa=
der.java:224)=20
> at org.hibernate.loader.Loader.doList(Loader.java:2145)=20
> at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2029)=20
> at org.hibernate.loader.Loader.list(Loader.java:2024)=20
> at org.hibernate.loader.custom.CustomLoader.list(CustomLoader.java:111)=
=20
> at org.hibernate.impl.SessionImpl.listCustomQuery(SessionImpl.java:1655)=
=20
> at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:1=
42)=20
> at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:164)=20
> at org.hibernate.impl.AbstractQueryImpl.uniqueResult(AbstractQueryImpl.ja=
va:749)=20
> Hibernate version: 3.1.3=20
> Code between sessionFactory.openSession() and session.close():=20
> Session session =3D null;=20
> Date date;=20
> try=20
> {=20
> session =3D sessionFactory.openSession ();=20
> date =3D (Date) session.createSQLQuery ("SELECT SYSDATE CURRENT_DATE FROM=
 DUAL").uniqueResult ();=20
> }=20
> finally=20
> {=20
> try=20
> {=20
> if (session !=3D null) session.close ();=20
> }=20
> catch (HibernateException e2) {}=20
> }=20
> System.out.println (new SimpleDateFormat ("hh:mm:ss").format (date));=20
> Name and version of the database you are using: Oracle 10.2.0.1

--=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: (EJB-184) Add EM property for FlushMode

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

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

Emmanuel Bernard updated EJB-184:
---------------------------------

    Fix Version: 3.2.0

> Add EM property for FlushMode
> -----------------------------
>
>          Key: EJB-184
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-184
>      Project: Hibernate Entity Manager
>         Type: New Feature

>   Components: EntityManager
>     Reporter: Christian Bauer
>     Priority: Blocker
>      Fix For: 3.2.0

>
>
> Add a "flushmode.application" property for createEntityManager() and sync this name with the Glassfish team.

-- 
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: (EJB-184) Add EM property for FlushMode

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

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

    Resolution: Fixed

org.hibernate.flushMode
Takes either a FlushMode object, a FlushModeType object or a String

> Add EM property for FlushMode
> -----------------------------
>
>          Key: EJB-184
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-184
>      Project: Hibernate Entity Manager
>         Type: New Feature

>   Components: EntityManager
>     Reporter: Christian Bauer
>     Priority: Blocker
>      Fix For: 3.2.0

>
>
> Add a "flushmode.application" property for createEntityManager() and sync this name with the Glassfish team.

-- 
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: (EJB-184) Add EM property for FlushMode

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

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

Emmanuel Bernard updated EJB-184:
---------------------------------

    Summary: Add EM property for FlushMode  (was: Add EM property for FlushModeType.APPLICATION)

> Add EM property for FlushMode
> -----------------------------
>
>          Key: EJB-184
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-184
>      Project: Hibernate Entity Manager
>         Type: New Feature

>   Components: EntityManager
>     Reporter: Christian Bauer
>     Priority: Blocker

>
>
> Add a "flushmode.application" property for createEntityManager() and sync this name with the Glassfish team.

-- 
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-1887) SortedSet broken in 3.2.0.cr3

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

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1887?page=all ]
     
Steve Ebersole resolved HHH-1887:
---------------------------------

    Resolution: Duplicate
     Assign To: Steve Ebersole

> SortedSet broken in 3.2.0.cr3
> -----------------------------
>
>          Key: HHH-1887
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1887
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.2.0.cr3
>  Environment: Hibernate 3.2.0.cr3, any database
>     Reporter: Daan Van Heghe
>     Assignee: Steve Ebersole

>
>
> the comparator for a SortedSet is no longer called in 3.2.0.cr3, works fine in 3.2.0.cr2.

-- 
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-1893) SYSDATE and SYSTIMESTAMP not working well with Hibernate 3.1.3 and Oracle 10.2.0.1

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

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1893?p=
age=3Dall ]
    =20
Christian Bauer resolved HHH-1893:
----------------------------------

    Resolution: Rejected

Stay on the user forum, this is not a support portal.


> SYSDATE and SYSTIMESTAMP not working well with Hibernate 3.1.3 and Oracle=
 10.2.0.1
> -------------------------------------------------------------------------=
---------
>
>          Key: HHH-1893
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/H=
HH-1893
>      Project: Hibernate3
>         Type: Bug

>   Components: query-sql
>     Versions: 3.1.3
>     Reporter: Nestor Bosc=C3=A1n
>     Priority: Minor

>
>
> Trying to use sysdate or systimestamp in SQL Queries with Oracle database=
.=20
> If I use sysdate Hibernate is not retrieving the hour, minute, second par=
t. I always get 12:00:00pm=20
> If I use systimestamp I get the following exception:=20
> org.hibernate.MappingException: No Dialect mapping for JDBC type: -101=20
> at org.hibernate.dialect.TypeNames.get(TypeNames.java:56)=20
> at org.hibernate.dialect.TypeNames.get(TypeNames.java:81)=20
> at org.hibernate.dialect.Dialect.getHibernateTypeName(Dialect.java:192)=
=20
> at org.hibernate.loader.custom.CustomLoader.getHibernateType(CustomLoader=
.java:161)=20
> at org.hibernate.loader.custom.CustomLoader.autoDiscoverTypes(CustomLoade=
r.java:131)=20
> at org.hibernate.loader.Loader.getResultSet(Loader.java:1678)=20
> at org.hibernate.loader.Loader.doQuery(Loader.java:662)=20
> at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loa=
der.java:224)=20
> at org.hibernate.loader.Loader.doList(Loader.java:2145)=20
> at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2029)=20
> at org.hibernate.loader.Loader.list(Loader.java:2024)=20
> at org.hibernate.loader.custom.CustomLoader.list(CustomLoader.java:111)=
=20
> at org.hibernate.impl.SessionImpl.listCustomQuery(SessionImpl.java:1655)=
=20
> at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:1=
42)=20
> at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:164)=20
> at org.hibernate.impl.AbstractQueryImpl.uniqueResult(AbstractQueryImpl.ja=
va:749)=20
> Hibernate version: 3.1.3=20
> Code between sessionFactory.openSession() and session.close():=20
> Session session =3D null;=20
> Date date;=20
> try=20
> {=20
> session =3D sessionFactory.openSession ();=20
> date =3D (Date) session.createSQLQuery ("SELECT SYSDATE CURRENT_DATE FROM=
 DUAL").uniqueResult ();=20
> }=20
> finally=20
> {=20
> try=20
> {=20
> if (session !=3D null) session.close ();=20
> }=20
> catch (HibernateException e2) {}=20
> }=20
> System.out.println (new SimpleDateFormat ("hh:mm:ss").format (date));=20
> Name and version of the database you are using: Oracle 10.2.0.1

--=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] Resolved: (HHH-1710) persistent collections with property-ref to secondary tables cannot be joined in HQL

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

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1710?page=all ]
     
Steve Ebersole resolved HHH-1710:
---------------------------------

    Resolution: Fixed

> persistent collections with property-ref to secondary tables cannot be joined in HQL
> ------------------------------------------------------------------------------------
>
>          Key: HHH-1710
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1710
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.2.0 cr1
>     Reporter: Maarten Winkels
>     Assignee: Steve Ebersole
>      Fix For: 3.2.0.ga
>  Attachments: joinsetpropertyref.patch, joinsetpropertyref.zip
>
>
> I have an entity that is split over two tables, with a <join ... /> in the mapping. This entity has a <set .../> which has a <key ... property-ref="aProperty"/>. The "aProperty" is mapped to the joined table.
> When querying using HQL and join fetching the collection, Hibernate generates a faulty join statement. It atempts to join on the correct column (the one indicated in the property-ref) but on the wrong table (the primary table in stead of the joined table).
> The attached testcase shows the situation.

-- 
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-1892) finish HHH-1789 for ordered and sorted collections

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

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1892?page=all ]
     
Steve Ebersole resolved HHH-1892:
---------------------------------

    Resolution: Fixed

> finish HHH-1789 for ordered and sorted collections
> --------------------------------------------------
>
>          Key: HHH-1892
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1892
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.2.0.cr3
>     Reporter: Steve Ebersole
>     Assignee: Steve Ebersole
>      Fix For: 3.2.0.ga

>
>
> Fix for HHH-1789 caused sorted and ordered sets and maps to stop working...

-- 
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-1893) SYSDATE and SYSTIMESTAMP not working well with Hibernate 3.1.3 and Oracle 10.2.0.1

[<no...@at...>]

SYSDATE and SYSTIMESTAMP not working well with Hibernate 3.1.3 and Oracle 1=
0.2.0.1
---------------------------------------------------------------------------=
-------

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

  Components: query-sql =20
    Versions: 3.1.3   =20
    Reporter: Nestor Bosc=C3=A1n
    Priority: Minor


Trying to use sysdate or systimestamp in SQL Queries with Oracle database.=
=20

If I use sysdate Hibernate is not retrieving the hour, minute, second part.=
 I always get 12:00:00pm=20

If I use systimestamp I get the following exception:=20

org.hibernate.MappingException: No Dialect mapping for JDBC type: -101=20
at org.hibernate.dialect.TypeNames.get(TypeNames.java:56)=20
at org.hibernate.dialect.TypeNames.get(TypeNames.java:81)=20
at org.hibernate.dialect.Dialect.getHibernateTypeName(Dialect.java:192)=20
at org.hibernate.loader.custom.CustomLoader.getHibernateType(CustomLoader.j=
ava:161)=20
at org.hibernate.loader.custom.CustomLoader.autoDiscoverTypes(CustomLoader.=
java:131)=20
at org.hibernate.loader.Loader.getResultSet(Loader.java:1678)=20
at org.hibernate.loader.Loader.doQuery(Loader.java:662)=20
at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loade=
r.java:224)=20
at org.hibernate.loader.Loader.doList(Loader.java:2145)=20
at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2029)=20
at org.hibernate.loader.Loader.list(Loader.java:2024)=20
at org.hibernate.loader.custom.CustomLoader.list(CustomLoader.java:111)=20
at org.hibernate.impl.SessionImpl.listCustomQuery(SessionImpl.java:1655)=20
at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:142=
)=20
at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:164)=20
at org.hibernate.impl.AbstractQueryImpl.uniqueResult(AbstractQueryImpl.java=
:749)=20

Hibernate version: 3.1.3=20

Code between sessionFactory.openSession() and session.close():=20

Session session =3D null;=20
Date date;=20

try=20
{=20
session =3D sessionFactory.openSession ();=20
date =3D (Date) session.createSQLQuery ("SELECT SYSDATE CURRENT_DATE FROM D=
UAL").uniqueResult ();=20
}=20
finally=20
{=20
try=20
{=20
if (session !=3D null) session.close ();=20
}=20
catch (HibernateException e2) {}=20
}=20

System.out.println (new SimpleDateFormat ("hh:mm:ss").format (date));=20



Name and version of the database you are using: Oracle 10.2.0.1

--=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-1710) persistent collections with property-ref to secondary tables cannot be joined in HQL

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

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

Steve Ebersole updated HHH-1710:
--------------------------------

        Summary: persistent collections with property-ref to secondary tables cannot be joined in HQL  (was: Allow set (or any collection) property-ref to property on joined-table to be join-fetched with HQL.)
           type: Bug  (was: Improvement)
    Fix Version: 3.2.0.ga

> persistent collections with property-ref to secondary tables cannot be joined in HQL
> ------------------------------------------------------------------------------------
>
>          Key: HHH-1710
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1710
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.2.0 cr1
>     Reporter: Maarten Winkels
>     Assignee: Steve Ebersole
>      Fix For: 3.2.0.ga
>  Attachments: joinsetpropertyref.patch, joinsetpropertyref.zip
>
>
> I have an entity that is split over two tables, with a <join ... /> in the mapping. This entity has a <set .../> which has a <key ... property-ref="aProperty"/>. The "aProperty" is mapped to the joined table.
> When querying using HQL and join fetching the collection, Hibernate generates a faulty join statement. It atempts to join on the correct column (the one indicated in the property-ref) but on the wrong table (the primary table in stead of the joined table).
> The attached testcase shows the situation.

-- 
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-1892) finish HHH-1789 for ordered and sorted collections

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

finish HHH-1789 for ordered and sorted collections
--------------------------------------------------

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

  Components: core  
    Versions: 3.2.0.cr3    
    Reporter: Steve Ebersole
 Assigned to: Steve Ebersole 
     Fix For: 3.2.0.ga


Fix for HHH-1789 caused sorted and ordered sets and maps to stop working...

-- 
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-227) remove reflection optimizer

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

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

Martin Schulz commented on HHH-227:
-----------------------------------

Can someone kindly patch the distributed properties template files, or does that require yet another new bug?

diff -rbu hibernate-3.2-orig/etc/hibernate.properties hibernate-3.2.0cr3/etc/hibernate.properties
--- hibernate-3.2-orig/etc/hibernate.properties 2006-07-06 11:37:46.000000000 -0400
+++ hibernate-3.2.0cr3/etc/hibernate.properties 2006-07-10 11:48:04.000000000 -0400
@@ -374,7 +374,7 @@
 #hibernate.use_identifer_rollback true


-## enable bytecode reflection optimizer (disabled by default)
+## enable CGLIB reflection optimizer (disabled by default)

 #hibernate.bytecode.use_reflection_optimizer true

diff -rbu hibernate-3.2-orig/etc/hibernate.properties.template hibernate-3.2.0cr3/etc/hibernate.properties.template
--- hibernate-3.2-orig/etc/hibernate.properties.template        2006-07-06 11:37:46.000000000 -0400
+++ hibernate-3.2.0cr3/etc/hibernate.properties.template        2006-07-10 11:48:08.000000000 -0400
@@ -359,9 +359,9 @@
 #hibernate.use_identifer_rollback true


-## enable CGLIB reflection optimizer (enabled by default)
+## enable CGLIB reflection optimizer (disabled by default)

-#hibernate.cglib.use_reflection_optimizer false
+#hibernate.bytecode.use_reflection_optimizer true



> remove reflection optimizer
> ---------------------------
>
>          Key: HHH-227
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-227
>      Project: Hibernate3
>         Type: Improvement

>   Components: core
>     Reporter: Juozas Baliuka
>     Assignee: amit bhayani
>     Priority: Minor
>      Fix For: 3.2.0 cr1
>  Attachments: Environment.java
>
>
> Probably it is a good time to drop "reflection_optimizer" (or to dissable it by default), SUN JVM generates code since jdk 1.4.2 to optimize native calls in reflection itself, double code generation just wastes memory (cglib is bit faster, but difference is too trivial to be usefull for data access).
> This stuff confuses users.

-- 
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-446) The is no possibility to specify embed-xml on key-many-to-one tag

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

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

Martin Schulz commented on HHH-446:
-----------------------------------

oops. wrong bug. sorry.

> The is no possibility to specify embed-xml on key-many-to-one tag
> -----------------------------------------------------------------
>
>          Key: HHH-446
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-446
>      Project: Hibernate3
>         Type: Improvement

>   Components: core
>     Versions: 3.0.2
>  Environment: MySQL 
>     Reporter: Markus Jessenitschnig
>     Priority: Minor

>
>
> It is not possible to specify embed-xml="false" on key-many-to-one tags within composite-id tag like it is possible for many-to-one relations.

-- 
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-446) The is no possibility to specify embed-xml on key-many-to-one tag

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

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

Martin Schulz commented on HHH-446:
-----------------------------------

Can someone kindly patch the distributed properties and template files as follows:

diff -rbu hibernate-3.2-orig/etc/hibernate.properties hibernate-3.2.0cr3/etc/hibernate.properties
--- hibernate-3.2-orig/etc/hibernate.properties 2006-07-06 11:37:46.000000000 -0400
+++ hibernate-3.2.0cr3/etc/hibernate.properties 2006-07-10 11:48:04.000000000 -0400
@@ -374,7 +374,7 @@
 #hibernate.use_identifer_rollback true


-## enable bytecode reflection optimizer (disabled by default)
+## enable CGLIB reflection optimizer (disabled by default)

 #hibernate.bytecode.use_reflection_optimizer true

diff -rbu hibernate-3.2-orig/etc/hibernate.properties.template hibernate-3.2.0cr3/etc/hibernate.properties.template
--- hibernate-3.2-orig/etc/hibernate.properties.template        2006-07-06 11:37:46.000000000 -0400
+++ hibernate-3.2.0cr3/etc/hibernate.properties.template        2006-07-10 11:48:08.000000000 -0400
@@ -359,9 +359,9 @@
 #hibernate.use_identifer_rollback true


-## enable CGLIB reflection optimizer (enabled by default)
+## enable CGLIB reflection optimizer (disabled by default)

-#hibernate.cglib.use_reflection_optimizer false
+#hibernate.bytecode.use_reflection_optimizer true



> The is no possibility to specify embed-xml on key-many-to-one tag
> -----------------------------------------------------------------
>
>          Key: HHH-446
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-446
>      Project: Hibernate3
>         Type: Improvement

>   Components: core
>     Versions: 3.0.2
>  Environment: MySQL 
>     Reporter: Markus Jessenitschnig
>     Priority: Minor

>
>
> It is not possible to specify embed-xml="false" on key-many-to-one tags within composite-id tag like it is possible for many-to-one relations.

-- 
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] Assigned: (HHH-1710) Allow set (or any collection) property-ref to property on joined-table to be join-fetched with HQL.

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

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

Steve Ebersole reassigned HHH-1710:
-----------------------------------

    Assign To: Steve Ebersole

> Allow set (or any collection) property-ref to property on joined-table to be join-fetched with HQL.
> ---------------------------------------------------------------------------------------------------
>
>          Key: HHH-1710
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1710
>      Project: Hibernate3
>         Type: Improvement

>   Components: core
>     Versions: 3.2.0 cr1
>     Reporter: Maarten Winkels
>     Assignee: Steve Ebersole
>  Attachments: joinsetpropertyref.patch, joinsetpropertyref.zip
>
>
> I have an entity that is split over two tables, with a <join ... /> in the mapping. This entity has a <set .../> which has a <key ... property-ref="aProperty"/>. The "aProperty" is mapped to the joined table.
> When querying using HQL and join fetching the collection, Hibernate generates a faulty join statement. It atempts to join on the correct column (the one indicated in the property-ref) but on the wrong table (the primary table in stead of the joined table).
> The attached testcase shows the situation.

-- 
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