hibernate-issues — Hibernate JIRA Notifications

[Hibernate-issues] [Hibernate-JIRA] Commented: (ANN-336) @OrderBy and @CollectionOfElements support (Sylvain Vieujot)

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

    [ http://opensource.atlassian.com/projects/hibernate/browse/ANN-336?page=comments#action_23353 ] 

Emmanuel Bernard commented on ANN-336:
--------------------------------------

some more support but no unit tests, simple elements are not covered

> @OrderBy and @CollectionOfElements support (Sylvain Vieujot)
> ------------------------------------------------------------
>
>          Key: ANN-336
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-336
>      Project: Hibernate Annotations
>         Type: Improvement

>   Components: binder
>     Reporter: Emmanuel Bernard
>      Fix For: 3.2.0

>
>
> No unit test though

-- 
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-336) @OrderBy and @CollectionOfElements support (Sylvain Vieujot)

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

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

Emmanuel Bernard updated ANN-336:
---------------------------------

      Component: binder
        Summary: @OrderBy and @CollectionOfElements support (Sylvain Vieujot)  (was: @OrderBy and @ColectionOfElements support)
    Fix Version: 3.2.0
    Description: No unit test though

> @OrderBy and @CollectionOfElements support (Sylvain Vieujot)
> ------------------------------------------------------------
>
>          Key: ANN-336
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-336
>      Project: Hibernate Annotations
>         Type: Improvement

>   Components: binder
>     Reporter: Emmanuel Bernard
>      Fix For: 3.2.0

>
>
> No unit test though

-- 
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-689) The query task

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

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

Dave Minter commented on HBX-689:
---------------------------------

Not verified against latest svn yet - although the suspicious looking code *is* in the latest QueryExporter.java from subversion.

I'll try and get my act together and test against svn source asap.

> The query task 
> ---------------
>
>          Key: HBX-689
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-689
>      Project: Hibernate Tools
>         Type: Bug

>   Components: ant
>     Versions: 3.1.beta5
>  Environment: Hibernate 3.1.3, against HSQL DB.
>     Reporter: Dave Minter
>     Priority: Minor
>  Attachments: trace.txt
>
>
> Running the following query task against my database:
> <htools destdir="${sql}">
>    <classpath refid="classpath.apps"/>
>    <annotationconfiguration configurationfile="${src}/hibernate.cfg.xml"/>
>    <query destfile="sql.log">from Note</query>
> </htools>
> Fails with the attached lavish stack trace. The cause of the problem appears to be a single character typo in:
> org.hibernate.tool.hbm2x.QueryExporter on line 47 where a variable "iter" is used instead of "iter1".
> There also appears to be a bug preventing the nested <hql> tasks from working, but I'm uncertain if that's an artifact of this problem or a separate issue.

-- 
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-689) The query task

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

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

Max Rydahl Andersen commented on HBX-689:
-----------------------------------------

have you verified this against latest svn or jbosside release?

> The query task 
> ---------------
>
>          Key: HBX-689
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-689
>      Project: Hibernate Tools
>         Type: Bug

>   Components: ant
>     Versions: 3.1.beta5
>  Environment: Hibernate 3.1.3, against HSQL DB.
>     Reporter: Dave Minter
>     Priority: Minor
>  Attachments: trace.txt
>
>
> Running the following query task against my database:
> <htools destdir="${sql}">
>    <classpath refid="classpath.apps"/>
>    <annotationconfiguration configurationfile="${src}/hibernate.cfg.xml"/>
>    <query destfile="sql.log">from Note</query>
> </htools>
> Fails with the attached lavish stack trace. The cause of the problem appears to be a single character typo in:
> org.hibernate.tool.hbm2x.QueryExporter on line 47 where a variable "iter" is used instead of "iter1".
> There also appears to be a bug preventing the nested <hql> tasks from working, but I'm uncertain if that's an artifact of this problem or a separate issue.

-- 
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-689) The query task

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

The query task 
---------------

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

  Components: ant  
    Versions: 3.1.beta5    
 Environment: Hibernate 3.1.3, against HSQL DB.
    Reporter: Dave Minter
    Priority: Minor
 Attachments: trace.txt

Running the following query task against my database:
<htools destdir="${sql}">
   <classpath refid="classpath.apps"/>
   <annotationconfiguration configurationfile="${src}/hibernate.cfg.xml"/>
   <query destfile="sql.log">from Note</query>
</htools>

Fails with the attached lavish stack trace. The cause of the problem appears to be a single character typo in:
org.hibernate.tool.hbm2x.QueryExporter on line 47 where a variable "iter" is used instead of "iter1".

There also appears to be a bug preventing the nested <hql> tasks from working, but I'm uncertain if that's an artifact of this problem or a separate issue.

-- 
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-1556) unique constraint error with increment generator, updating two database instances

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

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

Christy Pang commented on HB-1556:
----------------------------------

I am planning to upgrade to  Hibrenate 3.1.3 because of this issue, 

Are there any issues I should be aware of to upgrade from 2.1.8 to Hibernate 3.1.3?

Thanks
Christy

> unique constraint error with increment generator, updating two database instances
> ---------------------------------------------------------------------------------
>
>          Key: HB-1556
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-1556
>      Project: Hibernate2
>         Type: Bug

>   Components: core
>     Versions: 2.1.8
>  Environment: Hibernate 2.1.8, Oracle 9i, Tomcat
>     Reporter: Dwight Harm

>
>
> I'm updating two different instances of Oracle while running under Tomcat. The increment generator is using the highest value from the first instance when it generates a new key for the same table in the second instance. This results in a unique key constraint violation.
> Running a simplified test program in batch works, and Hibernate debug shows 2 calls that fetch the first free id (one for each db):
> id.IncrementGenerator::getNext(76): first free id: 123461
> But the real app, running under Tomcat, only shows one such trace. In this case, the first update, to db#1, runs under an http-processor thread; that generates the "first free id" trace. Later, a worker thread running a Quartz-scheduled task opens both db#1 and db#2, and adds a new "Offer" to db#2. No "first free id" trace appears. I've included a condensed version of the failing task's code below.
> Hibernate version: 2.1.8
> database: Oracle 9i
> Mapping documents:
> <hibernate-mapping package="com.xyz.admin.data">
> <class name="Offer" table="OFFER">
> <id name="id" type="java.lang.Long">
> <column name="OFFER_ID" sql-type="number" not-null="true"/>
> <generator class="increment"/>
> </id>
> Code from openSession() to failure:
> localSessionFactory = _hibernateEnvironments.getLocalSessionFactory();
> localSession = localSessionFactory.openSession();
> localTransaction = localSession.beginTransaction();
> localSession.update(_offerJob); // re-associate this with our session
> _offerJob.setMessage( "initializing" );
> targetSessionFactory = _hibernateEnvironments.getSessionFactory( _offerJob.getTargetEnvironmentName() );
> targetSession = targetSessionFactory.openSession();
> offers = _offerJob.getDeployableOffers();
> for (Iterator iter = offers.iterator(); iter.hasNext(); ) {
> DeployableOffer deployOffer = (DeployableOffer)iter.next();
> Offer sourceOffer = deployOffer.getOffer();
> Long sourceId = sourceOffer.getId();
> // it seemed necessary to do a 'get' here to avoid LazyInitialization errors later.
> sourceOffer = (Offer)localSession.get(Offer.class, sourceId);
> <calls method:>
> _targetSessionFactory = targetSession.getSessionFactory();
> Offer targetOffer = null;
> sourceOffer.setSynchronizationKey(syncKey);
> ClassMetadata offerMetadata = _targetSessionFactory.getClassMetadata( Offer.class );
> Transaction targetTransaction = targetSession.beginTransaction();
> targetOffer = (Offer)offerMetadata.instantiate(null);
> targetOffer.setSynchronizationKey(syncKey);
> /* ... update targetOffer fields... */
> targetOffer.setWebStatus(...);
> targetSession.saveOrUpdate( targetOffer );
> targetTransaction.commit();
> /* update of target offer fails here due to unique key constraint violation on Offer_id */
> stack trace:
> * ERROR 10:23:49.671 [Promotion Admin_Worker-2] deploy.OfferSynchronizer::synchronizeOffer(225): error synchronizing;
> net.sf.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
> at net.sf.hibernate.exception.ErrorCodeConverter.convert(ErrorCodeConverter.java:73)
> at net.sf.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29)
> at net.sf.hibernate.impl.BatcherImpl.convert(BatcherImpl.java:328)
> at net.sf.hibernate.impl.BatcherImpl.executeBatch(BatcherImpl.java:135)
> at net.sf.hibernate.impl.BatcherImpl.prepareStatement(BatcherImpl.java:61)
> at net.sf.hibernate.impl.BatcherImpl.prepareStatement(BatcherImpl.java:58)
> at net.sf.hibernate.impl.BatcherImpl.prepareBatchStatement(BatcherImpl.java:111)
> at net.sf.hibernate.persister.EntityPersister.insert(EntityPersister.java:454)
> at net.sf.hibernate.persister.EntityPersister.insert(EntityPersister.java:436)
> at net.sf.hibernate.impl.ScheduledInsertion.execute(ScheduledInsertion.java:37)
> at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2449)
> at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2435)
> at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2392)
> at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:2261)
> at net.sf.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:61)
> at com.xyz.promotion.admin.deploy.OfferSynchronizer.synchronizeOffer(OfferSynchronizer.java:214)
> at com.xyz.promotion.admin.deploy.OfferDeployer.execute(OfferDeployer.java:156)
> at com.xyz.promotion.admin.deploy.DeployQuartzJob.execute(DeployQuartzJob.java:72)
> at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
> at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
> Caused by: java.sql.BatchUpdateException: ORA-00001: unique constraint (TSI.SYS_C002728) violated
> at oracle.jdbc.dbaccess.DBError.throwBatchUpdateException(DBError.java:459)
> at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:3907)
> at com.mchange.v2.sql.filter.FilterPreparedStatement.executeBatch(FilterPreparedStatement.java:260)
> at net.sf.hibernate.impl.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:54)
> at net.sf.hibernate.impl.BatcherImpl.executeBatch(BatcherImpl.java:128)
> ... 16 more
> Debug level Hibernate log excerpt:
> * DEBUG 12:32:34.968 [http-9980-Processor24] id.IncrementGenerator::getNext(62): fetching initial value: select max(OFFER_ID) from OFFER
> * DEBUG 12:32:34.984 [http-9980-Processor24] id.IncrementGenerator::getNext(76): first free id: 123462
> [the above occurs during creation of new Offer on db#1]
> * DEBUG 12:33:01.437 [http-9980-Processor24] id.SequenceGenerator::generate(76): Sequence identifier generated: 124
> * INFO 12:34:14.109 [Promotion Admin_Worker-1] deploy.DeployQuartzJob::execute(60): Deploy Job executing
> * INFO 12:34:14.234 [Promotion Admin_Worker-1] deploy.OfferDeployer::execute(151): processing offerid=123462
> * WARN 12:34:15.093 [Promotion Admin_Worker-1] util.JDBCExceptionReporter::logExceptions(57): SQL Error: 1, SQLState: 23000
> * ERROR 12:34:15.109 [Promotion Admin_Worker-1] util.JDBCExceptionReporter::logExceptions(58): ORA-00001: unique constraint (TSI.SYS_C002728) violated

-- 
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-688) hbm2java is not generating the @Version annotation for the <version ...> element

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

hbm2java is not generating the @Version annotation for the <version ...> element
--------------------------------------------------------------------------------

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

  Components: hbm2java  
    Versions: 3.1.beta5    
    Reporter: Sean Dawson


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

Given a mapping file:

----
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
<!-- Generated Jun 13, 2006 3:27:21 PM by Hibernate Tools 3.1.0.beta5 -->
<hibernate-mapping>
    <class name="Sample" table="Sample">
        <id name="id" type="java.lang.Long">
            <column name="id" />
            <generator class="native" />
        </id>
        <version name="version" column="version"/>
        <property name="value" column="value" type="string"/>
    </class>
</hibernate-mapping>
----

the following ejb is generated (via hbm2java, ejb3="true", jdk5="true":

----
// default package
// Generated Jun 16, 2006 3:23:35 PM by Hibernate Tools 3.1.0.beta5


import javax.persistence.Column;
import javax.persistence.Entity;
import javax.persistence.GeneratedValue;
import javax.persistence.Id;
import javax.persistence.Table;

/**
 * Sample generated by hbm2java
 */
@Entity
@Table(name="Sample"
)
public class Sample  implements java.io.Serializable {

    // Fields    

     private Long id;
     private Integer version;
     private String value;

     // Constructors

    /** default constructor */
    public Sample() {
    }

    /** full constructor */
    public Sample(String value) {
       this.value = value;
    }
    
   
    // Property accessors
     @Id @GeneratedValue
    
    @Column(name="id", unique=false, nullable=false, insertable=true, updatable=true)
    public Long getId() {
        return this.id;
    }
    
    public void setId(Long id) {
        this.id = id;
    }
    
    @Column(name="version", unique=false, nullable=false, insertable=true, updatable=true)
    public Integer getVersion() {
        return this.version;
    }
    
    public void setVersion(Integer version) {
        this.version = version;
    }
    
    @Column(name="value", unique=false, nullable=true, insertable=true, updatable=true)
    public String getValue() {
        return this.value;
    }
    
    public void setValue(String value) {
        this.value = value;
    }
}
-----

There should be a @Version annotation on the version property!

-- 
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-1820) Lazy loading problem when property-ref is used for collections

[Ben H. (JIRA) <no...@at...>]

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

Ben Hall commented on HHH-1820:
-------------------------------

We've encountered this problem in our web application while using DB2 for z/OS 7.0.

However, we haven't seen this problem running against HSQLDB, either while running unit tests or in our application.


> Lazy loading problem when property-ref is used for collections
> --------------------------------------------------------------
>
>          Key: HHH-1820
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1820
>      Project: Hibernate3
>         Type: Bug

>     Versions: 3.1.3
>  Environment: Oracle 8.1.7
>     Reporter: Jakub Mendys

>
>
> Consider mapping 
> 	<class name="MedDRATerm" table="MBROW_MEDDRA_TERMS" mutable="false"
> 		batch-size="50">
> 		<cache usage="read-only" region="dictionary" />
> 		<id name="medDRATermId" type="long" column="TERM_ID">
> 			<generator class="assigned" />
> 		</id>
> 		<map name="termNames" table="MBROW_TERM_NAMES" lazy="true"
> 			batch-size="50">
> 			<cache usage="read-only" region="dictionary" />
> 			<key column="MEDDRA_CODE" property-ref="medDRACode" />
> 			<index column="LANGUAGE_ID"
> 				type="com.roche.dss.meddra.dao.type.LanguageType" />
> 			<element column="NAME" type="string" />
> 		</map>
> 		<property name="medDRACode" column="MEDDRA_CODE"
> 			type="com.roche.dss.meddra.dao.type.MedDRACodeType" />
> 	</class>
> 	<class name="MedDRATermInstance" table="MBROW_MEDDRA_TREES"
> 		mutable="false">
> 		<cache usage="read-only" region="dictionary" />
> 		<id name="medDRATermInstanceId" type="long" column="NODE_ID">
> 			<generator class="assigned" />
> 		</id>
> 		<many-to-one name="medDRATerm" class="MedDRATerm"
> 			column="TERM_ID" fetch="join" not-null="true" insert="false"
> 			update="false" />
> 	</class>
> When you execute a query:
> from MedDRATermInstance i where i.version=:versionId and i.medDRATerm in (:terms)
> and then using the _same session_ you will iterate over returned collection and will call session.get(id) for returned records it is very likely that for _SOME_ (random??) of objects when you will try to access its properties you will get following exception thrown:
> 2006-06-07 19:25:11,942 ERROR org.hibernate.LazyInitializationException - failed to lazily initialize a collection of role: com.roche.dss.meddra.model.MedDRATerm.termNames, no session or session was
> losed
> org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: com.roche.dss.meddra.model.MedDRATerm.termNames, no session or session was closed
>         at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:358)
>         at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationExceptionIfNotConnected(AbstractPersistentCollection.java:350)
>         at org.hibernate.collection.AbstractPersistentCollection.readElementByIndex(AbstractPersistentCollection.java:151)
>         at org.hibernate.collection.PersistentMap.get(PersistentMap.java:127)
> Calling session.clear() before session.get() helps to workaround this but causes all the records to be fethed again from the database.

-- 
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-1844) schemaExport does not create column for formula-generated property

[Michel G. (JIRA) <no...@at...>]

schemaExport does not create column for formula-generated property
------------------------------------------------------------------

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

    Versions: 3.1.3    
 Environment: Hibernate 3.1.3, Oracle 10g, JDK 1.5.0._06, WinXp
    Reporter: Michel Gomis


When running schemaExport in "create" mode, Hibernate does not create column DEMANDE.numero
In "update" mode or without <formula> element, it works fine.

<hibernate-mapping>
	<class name="Demande" table="DEMANDE">
		<id name="id">
			<generator class="hilo" />
		</id>
		<property name="numero" type="integer" not-null="true" generated="insert">
			<formula>SELECT MAX(numero) +1</formula>
		</property>
	</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-1843) lazy loading doesn't work inside <component ...>

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

lazy loading doesn't work inside <component ...>
------------------------------------------------

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

 Environment: Postgresl, Hibernate3
    Reporter: J=C3=BCrgen Rose


1. setting property lazy=3D"true" on a component has no effect at all

2. any many-to-one property within that component with lazy=3D"no-proxy" is=
 fetched right away, which leads to n+1 Selects

Example:

class User {
    ...
}

class MetaData {
    Date creationTime;
    User creationUser;
    Date modificateionTime;
    User modificationUser;
    ...
}

class Foo {
    String attr1;
    String attr2;
    MetaData metaData;
    ...
}=20

<class name=3D"Foo" table=3D"foo">
    <property name=3D"attr1" column=3D"attr1" />
    <property name=3D"attr1" column=3D"attr1" />
  =20
    <component name=3D"metaData" class=3D"MetaData" lazy=3D"true">
        <many-to-one name=3D"creationUser" class=3D"User" column=3D"creatio=
n_user" not-found=3D"ignore" fetch=3D"select" lazy=3D"no-proxy"></many-to-o=
ne>
        <property name=3D"creationTime" type=3D"timestamp" column=3D"creati=
on_time" />
        <many-to-one name=3D"modificationUser" class=3D"User" column=3D"mod=
ification_user" not-found=3D"ignore" fetch=3D"select" lazy=3D"no-proxy"></m=
any-to-one>
        <property name=3D"modificationTime" type=3D"timestamp" column=3D"mo=
dification_time" />
    </component>
</class>=20

This makes it unusable for us, therefore it is even a major issue.

--=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: (EJB-181) ExplodedJarVisitor and paths with white spaces

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

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

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

Fixed in SVN, please test.

> ExplodedJarVisitor and paths with white spaces
> ----------------------------------------------
>
>          Key: EJB-181
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-181
>      Project: Hibernate Entity Manager
>         Type: Bug

>   Components: EntityManager
>     Versions: 3.2.0.cr1
>  Environment: Sun's JRE 1.5.0_06; Tomcat 5.5.17; Windows XP Professional.
>     Reporter: Alexandrino Lucas
>     Assignee: Emmanuel Bernard
>      Fix For: 3.2.0

>
> Original Estimate: 15 minutes
>         Remaining: 15 minutes
>
> org.hibernate.ejb.packaging.ExplodedJarVisitor.doProcessElements() has the same problem and solution as issue EJB-178.

-- 
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-374) Map - OneToMany w or w/o join table creates bad sql

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

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

Emmanuel Bernard updated ANN-374:
---------------------------------

    Fix Version:     (was: 3.2.0.cr1)

> Map - OneToMany w or w/o join table creates bad sql
> ---------------------------------------------------
>
>          Key: ANN-374
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-374
>      Project: Hibernate Annotations
>         Type: Improvement

>   Components: binder
>     Versions: 3.1beta6
>  Environment: Hibernate 3.1 RC1, Annotations 3.1b6, Java 1.5.0_05
>     Reporter: Todd O
>     Assignee: Emmanuel Bernard
>  Attachments: KeyValue2.java, MyEntity2.java, TestKeyValue2.java
>
>
> Seems like there is a problem with mapping a Map using join table. 
> I have a relation like this:
> @OneToMany(cascade=CascadeType.ALL)
>     @MapKey(name="name")
>     public Map<String, KeyValue> getProps() {
>         return props;
>     }
> The correct tables are created and inserting data works fine. When loading, however, I get the error below.
> When using a join column, everything works fine:
> @OneToMany(cascade=CascadeType.ALL)
>     @MapKey(name="name")
>     @JoinColumn(name="myentity_id")
>     public Map<String, KeyValue> getProps() {
>         return props;
>     }
> Attached the two test classes.
> The error:
> ...
> Hibernate: select this_.id as id3_0_ from test_MyEntity this_
> Hibernate: select props0_.MyEntity_id as MyEntity1_1_, props0_.props_id as props2_1_, props0_.name as formula0_1_, keyvalue1_.id as id2_0_, keyvalue1_.val as val2_0_, keyvalue1_.name as name2_0_ from test_MyEntity_KeyValue props0_ left outer join test_KeyValue keyvalue1_ on props0_.props_id=keyvalue1_.id where props0_.MyEntity_id=?
> 15:11:49,078  WARN JDBCExceptionReporter:71 - SQL Error: 1054, SQLState: 42S22
> Exception in thread "main" 15:11:49,078 ERROR JDBCExceptionReporter:72 - null,  message from server: "Unknown column 'props0_.name' in 'field list'"
> org.hibernate.exception.SQLGrammarException: could not initialize a collection: [test.data.MyEntity.props#1]
> 	at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:65)
> 	at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
> 	at org.hibernate.loader.Loader.loadCollection(Loader.java:1923)
> 	at org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:71)
> 	at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:520)
> 	at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:60)
> 	at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1565)
> 	at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:344)
> 	at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86)
> 	at org.hibernate.collection.AbstractPersistentCollection.readElementByIndex(AbstractPersistentCollection.java:161)
> 	at org.hibernate.collection.PersistentMap.get(PersistentMap.java:127)
> 	at test.TestKeyValue.test(TestKeyValue.java:43)
> 	at test.TestKeyValue.main(TestKeyValue.java:57)
> Caused by: java.sql.SQLException: null,  message from server: "Unknown column 'props0_.name' in 'field list'"
> 	at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1876)
> 	at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1098)
> 	at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1192)
> 	at com.mysql.jdbc.Connection.execSQL(Connection.java:2051)
> 	at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1496)
> 	at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:137)
> 	at org.hibernate.loader.Loader.getResultSet(Loader.java:1676)
> 	at org.hibernate.loader.Loader.doQuery(Loader.java:662)
> 	at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:223)
> 	at org.hibernate.loader.Loader.loadCollection(Loader.java:1916)
> 	... 10 more

-- 
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-1319) Hibernate 3.1 does not analyze queries with a certain depth anymore

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

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

Thomas Klaeger commented on HHH-1319:
-------------------------------------

According to http://www.hibernate.org/250.html#A34 - "Hibernate 3.1: stricter checking of invalid queries" the queries shown above "worked purely by side effect in earlier versions".

The queries should be rewritten as

  select a from Dispo.Hibernate.Test.A as a join a.ptrB as b where b.ptrC.Oid >= :oid

and

  select cs from CurveSet cs join cs.contents co where co.curve.id = :curveId

IMHO the described behaviour is not a bug since it seems to be an intended change from earlier Hibernate versions, so this issue should be closed as "INVALID - WON'T FIX".

However: HIbernate could at least provide a less cryptic error message.

> Hibernate 3.1 does not analyze queries with a certain depth anymore
> -------------------------------------------------------------------
>
>          Key: HHH-1319
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1319
>      Project: Hibernate3
>         Type: Bug

>   Components: query-hql
>     Versions: 3.1
>  Environment: Linux, jdk 1.5, Hibernate 3.1, Oracle 10g
>     Reporter: Erik Heckert
>  Attachments: testcase.tar
>
>
> A query like the one
>     from Dispo.Hibernate.Test.A as a where a.ptrB.ptrC.Oid >= :oid
> leads to a NullPointerException when using Hibernate 3.1. The same query runs without a problem against Hibernate 3.0.5.
> When breaking down the where clause to "a.ptrB.Oid = ptrC.Oid and ptrC.Oid = :oid" the query works.
> The stack trace is:
>      [java] java.lang.NullPointerException
>      [java] 	at org.hibernate.hql.ast.tree.DotNode.getColumns(DotNode.java:97)
>      [java] 	at org.hibernate.hql.ast.tree.DotNode.initText(DotNode.java:210)
>      [java] 	at org.hibernate.hql.ast.tree.DotNode.resolve(DotNode.java:204)
>      [java] 	at org.hibernate.hql.ast.tree.FromReferenceNode.resolve(FromReferenceNode.java:94)
>      [java] 	at org.hibernate.hql.ast.tree.FromReferenceNode.resolve(FromReferenceNode.java:90)
>      [java] 	at org.hibernate.hql.ast.HqlSqlWalker.resolve(HqlSqlWalker.java:660)
>      [java] 	at org.hibernate.hql.antlr.HqlSqlBaseWalker.expr(HqlSqlBaseWalker.java:1213)
>      [java] 	at org.hibernate.hql.antlr.HqlSqlBaseWalker.exprOrSubquery(HqlSqlBaseWalker.java:4022)
>      [java] 	at org.hibernate.hql.antlr.HqlSqlBaseWalker.comparisonExpr(HqlSqlBaseWalker.java:3628)
>      [java] 	at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1756)
>      [java] 	at org.hibernate.hql.antlr.HqlSqlBaseWalker.whereClause(HqlSqlBaseWalker.java:774)
>      [java] 	at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:575)
>      [java] 	at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:279)
>      [java] 	at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:227)
>      [java] 	at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:218)
>      [java] 	at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:158)
>      [java] 	at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:105)
>      [java] 	at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:74)
>      [java] 	at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:53)
>      [java] 	at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:71)
>      [java] 	at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:108)
>      [java] 	at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:88)
>      [java] 	at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1540)
>      [java] 	at Dispo.Hibernate.Test.QueryABC.main(QueryABC.java:32)
> I'll attach the Java files I've used for this 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] Commented: (HHH-1566) SchemaValidator Complains about Oracle Date Columns

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

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

Keenan Ross commented on HHH-1566:
----------------------------------

The reported behavior differs based on which version of the Oracle JDBC driver you use. The most recent drivers (10.2) exercize this bug. It was introduced in the 9.2 drivers when Oracle changed the Column Metadata returned for a column of type DATE from javax.sql.Timestamp to javax.sql.Date, in the 9.2 drivers. You can read more about the change at: http://www.oracle.com/technology/tech/java/sqlj_jdbc/htdocs/jdbc_faq_0.htm#08_01

The suggested workaround, oracle.jdbc.V8Compatible=true, does indeed make the bug go away, but given the prevelance of the 10g drivers, we should fix it in the base configuration.

The bug is still present in the now current Hibernate releases:
    * Hibernate Core 3.2.0.CR2 (CR is Candidate for Release)
    * Hibernate Annotation 3.2.0.CR1
    * Hibernate Entity Manager 3.2.0.CR1
--keenan



> SchemaValidator Complains about Oracle Date Columns
> ---------------------------------------------------
>
>          Key: HHH-1566
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1566
>      Project: Hibernate3
>         Type: Bug

>     Versions: 3.1.1
>  Environment: Hibernate 3.1.1, Annotations 3.1B8, EntityManager 3.1B6, Oracle 10g 
>     Reporter: Keenan Ross

>
>
> In the EJB3 Persistence forum, http://forum.hibernate.org/viewtopic.php?t=956307#2295709, Emmanuel suggested submit a bug report for this issue:
> The SchemaValidator objects to a Oracle column declared with the DATE datatype and annotated as TemporalType.TIMESTAMP.
> The SchemaValidator complains:
>     javax.persistence.PersistenceException: org.hibernate.HibernateException: Wrong column type: LAST_UPDATE, expected: timestamp
> on a persistent property declared as
>     @Column(name="LAST_UPDATE", unique=false, nullable=false, insertable=true, updatable=true, length=7)
>     @Temporal(TemporalType.TIMESTAMP)
>     public Date getLastUpdate() {
>         return this.lastUpdate;
>     }
> with DDL
>     CREATE TABLE plate (..., last_update DATE NOT NULL, ...)
> In Oracle, the DATE datatype contains both date and time information, much like java.lang.Date, so a TIMESTAMP temporal type should be a valid mapping. Indeed it is the only valid mapping, because while attempts to use TemporalType.DATE or TemporalType.TIME in the above example pass the SchemaValidator, they yeild Java Dates that contain only the date or time portions, respectively.
> From a brief review of the Hibernate code, it seems that each Dialect maps to an appropriate type, potentially out of several, while the validator thinks that is the only valid mapping.
> --keenan

-- 
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: (ANN-375) @Email validator failed a valid email address

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

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

    Resolution: Fixed

> @Email validator failed a valid email address
> ---------------------------------------------
>
>          Key: ANN-375
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-375
>      Project: Hibernate Annotations
>         Type: Bug

>   Components: validator
>     Versions: 3.2.0.cr1
>  Environment: JBoss 4.0.4.GA
>     Reporter: Jeff Schnitzer
>     Assignee: Emmanuel Bernard
>      Fix For: 3.2.0

>
>
> @Email validation failed this email adddress:
> SRS0=aHFE=YF=pobox.com=fr...@bo...
> It looks valid to me.

-- 
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-375) @Email validator failed a valid email address

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

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

Emmanuel Bernard updated ANN-375:
---------------------------------

      Component: validator
    Fix Version: 3.2.0
        Version: 3.2.0.cr1
      Assign To: Emmanuel Bernard

> @Email validator failed a valid email address
> ---------------------------------------------
>
>          Key: ANN-375
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-375
>      Project: Hibernate Annotations
>         Type: Bug

>   Components: validator
>     Versions: 3.2.0.cr1
>  Environment: JBoss 4.0.4.GA
>     Reporter: Jeff Schnitzer
>     Assignee: Emmanuel Bernard
>      Fix For: 3.2.0

>
>
> @Email validation failed this email adddress:
> SRS0=aHFE=YF=pobox.com=fr...@bo...
> It looks valid to me.

-- 
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] Closed: (HHH-1831) Batch loading the same EntityKey (one side of manytoone ) more than once

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

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

    Fix Version: 3.2.0
     Resolution: Fixed
      Assign To: Steve Ebersole

Not quite the correct solution.  TheRightThing is to modify ManyToOneType to have it make sure it should be adding something to the batcj fetch queue before it actually does.  Adding that check in BatchFetchQueue.addBatchLoadableEntityKey() acutally causes unnecessary overhead to the other current caller of that method: DefaultLoadEventListener, where we already know for a fact that the entity is not associated with the session.

Added the necessary changes to ManyToOneType

> Batch loading the same EntityKey (one side of manytoone ) more than once
> ------------------------------------------------------------------------
>
>          Key: HHH-1831
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1831
>      Project: Hibernate3
>         Type: Improvement

>   Components: core
>     Versions: 3.1.1, 3.1.2, 3.1.3
>     Reporter: amit bhayani
>     Assignee: Steve Ebersole
>     Priority: Minor
>      Fix For: 3.2.0

>
>
> Within the same session, the same entity gets batch loaded multiple times. The ManyToOneType.scheduleBatchLoad calls BatchFetchQueue.addBatchLoadableEntityKey without checking to see if the entity already exists with the current PersistanceContext. Adding the extra condition "!context.containsEntity(key)" to the BatchFetchQueue.addBatchLoadableEntityKey method which seems to address the issue.
> public void addBatchLoadableEntityKey(EntityKey key) {
> if ( key.isBatchLoadable() && !context.containsEntity(key) ) {
> batchLoadableEntityKeys.put(key, MARKER);
> }
> }
> This will save few loops if we have large set of Entity being lodaded with each of them having manytoone relationship with other Entity.

-- 
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-1842) composite primary key with identity column and foreign key

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

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

    Resolution: Rejected

http://forum.hibernate.org/


> composite primary key with identity column and foreign key
> ----------------------------------------------------------
>
>          Key: HHH-1842
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1842
>      Project: Hibernate3
>         Type: Bug

>   Components: metamodel
>     Versions: 3.1.3
>  Environment: Hibernate 3.1.3  DB2 os390
>     Reporter: James ODea

>
>
> I need to map a table (AddressTable below) that uses an identity column and an integer column as the composit primary key.  The integer column is a foreign key.  Is there an example of how to map this?
> ClientTable
> CLIENT_KEY  INTEGER <PK> IDENTITY
> AddressTable
> CLIENT_KEY INTEGER <PK FK> NOT NULL
> ADDRESS_KEY INTEGER <PK> IDENTITY

-- 
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] Closed: (HHH-1840) Wrong value for tuplizer@entity-mode in mapping DTD

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

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1840?p=
age=3Dall ]
    =20
Steve Ebersole closed HHH-1840:
-------------------------------

    Resolution: Duplicate

3.1rc3 is really old you know ;)

> Wrong value for tuplizer@entity-mode in mapping DTD
> ---------------------------------------------------
>
>          Key: HHH-1840
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/H=
HH-1840
>      Project: Hibernate3
>         Type: Bug

>     Versions: 3.1 rc3
>     Reporter: C=C3=A9dric Chantepie
>  Attachments: dtd.patch
>
>
> Enumeration of values for attribute 'entity-mode' of element 'tuplizer' (=
pojo|dom4j|dynamic-map) does not match constants of class EntityMode.
> For exemple, EntityMode.POJO.toString()equals("POJO") and so HbmBinder.lo=
cateTuplizerDefinition cannot work (in this pojo case it does "POJO".equals=
("pojo") in fact).
> The easiest way to fix that should be to change values in DTD if there is=
 no particular reason to change values in classes.

--=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: (HHH-1842) composite primary key with identity column and foreign key

[James O. (JIRA) <no...@at...>]

composite primary key with identity column and foreign key
----------------------------------------------------------

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

  Components: metamodel  
    Versions: 3.1.3    
 Environment: Hibernate 3.1.3  DB2 os390
    Reporter: James ODea


I need to map a table (AddressTable below) that uses an identity column and an integer column as the composit primary key.  The integer column is a foreign key.  Is there an example of how to map this?

ClientTable
CLIENT_KEY  INTEGER <PK> IDENTITY


AddressTable
CLIENT_KEY INTEGER <PK FK> NOT NULL
ADDRESS_KEY INTEGER <PK> IDENTITY

-- 
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: (ANN-120) Map, OneToMany, join table or @ManyToMany does not work

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

    [ http://opensource.atlassian.com/projects/hibernate/browse/ANN-120?page=comments#action_23342 ] 

Emmanuel Bernard commented on ANN-120:
--------------------------------------

Hi Todd, can you open a new case with that. I'm pretty sure this is not the same problem

> Map, OneToMany, join table or @ManyToMany does not work
> -------------------------------------------------------
>
>          Key: ANN-120
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-120
>      Project: Hibernate Annotations
>         Type: Improvement

>   Components: binder
>     Versions: 3.1beta6
>  Environment: Hibernate 3.1 RC1, Annotations 3.1b6, Java 1.5.0_05
>     Reporter: Mattias Arbin
>     Assignee: Emmanuel Bernard
>      Fix For: 3.2.0.cr1
>  Attachments: KeyValue.java, KeyValue2.java, MyEntity.java, MyEntity2.java, TestKeyValue.java, TestKeyValue2.java
>
>
> Seems like there is a problem with mapping a Map using join table. 
> I have a relation like this:
> @OneToMany(cascade=CascadeType.ALL)
>     @MapKey(name="name")
>     public Map<String, KeyValue> getProps() {
>         return props;
>     }
> The correct tables are created and inserting data works fine. When loading, however, I get the error below.
> When using a join column, everything works fine:
> @OneToMany(cascade=CascadeType.ALL)
>     @MapKey(name="name")
>     @JoinColumn(name="myentity_id")
>     public Map<String, KeyValue> getProps() {
>         return props;
>     }
> Attached the two test classes.
> The error:
> ...
> Hibernate: select this_.id as id3_0_ from test_MyEntity this_
> Hibernate: select props0_.MyEntity_id as MyEntity1_1_, props0_.props_id as props2_1_, props0_.name as formula0_1_, keyvalue1_.id as id2_0_, keyvalue1_.val as val2_0_, keyvalue1_.name as name2_0_ from test_MyEntity_KeyValue props0_ left outer join test_KeyValue keyvalue1_ on props0_.props_id=keyvalue1_.id where props0_.MyEntity_id=?
> 15:11:49,078  WARN JDBCExceptionReporter:71 - SQL Error: 1054, SQLState: 42S22
> Exception in thread "main" 15:11:49,078 ERROR JDBCExceptionReporter:72 - null,  message from server: "Unknown column 'props0_.name' in 'field list'"
> org.hibernate.exception.SQLGrammarException: could not initialize a collection: [test.data.MyEntity.props#1]
> 	at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:65)
> 	at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
> 	at org.hibernate.loader.Loader.loadCollection(Loader.java:1923)
> 	at org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:71)
> 	at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:520)
> 	at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:60)
> 	at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1565)
> 	at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:344)
> 	at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86)
> 	at org.hibernate.collection.AbstractPersistentCollection.readElementByIndex(AbstractPersistentCollection.java:161)
> 	at org.hibernate.collection.PersistentMap.get(PersistentMap.java:127)
> 	at test.TestKeyValue.test(TestKeyValue.java:43)
> 	at test.TestKeyValue.main(TestKeyValue.java:57)
> Caused by: java.sql.SQLException: null,  message from server: "Unknown column 'props0_.name' in 'field list'"
> 	at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1876)
> 	at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1098)
> 	at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1192)
> 	at com.mysql.jdbc.Connection.execSQL(Connection.java:2051)
> 	at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1496)
> 	at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:137)
> 	at org.hibernate.loader.Loader.getResultSet(Loader.java:1676)
> 	at org.hibernate.loader.Loader.doQuery(Loader.java:662)
> 	at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:223)
> 	at org.hibernate.loader.Loader.loadCollection(Loader.java:1916)
> 	... 10 more

-- 
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-1841) Second-level cache entity "evict" when having two entities (mapped) representing the same DB row.

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

Second-level cache entity "evict" when having two entities (mapped) representing the same DB row.
-------------------------------------------------------------------------------------------------

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

    Versions: 3.1.3    
 Environment: Hibernate 3.1.3 & MySQL 4.1.x (unimportant)
    Reporter: Karol Bucek
    Priority: Minor


This is "simple" to understand, I am not sure if it makes sense to handle this in Hibernate.

Let's propose we have two different entites A and B (extends A) mapped over the same DB table (using polymorphism="explicit") thus having a "light" representation of the data in the table. Now if the second-level cache is enabled (we are caching A instances) and Hibernate performs an update(B) operation while the "same" A (meaning with the same identifier thus representing the same row) was cached before, the A instance will stay in the cache and thus will represent the "old" data until it expires (old is evicted by hand using the SessionFactory). 


-- 
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-1840) Wrong value for tuplizer@entity-mode in mapping DTD

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

Wrong value for tuplizer@entity-mode in mapping DTD
---------------------------------------------------

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

    Versions: 3.1 rc3   =20
    Reporter: C=C3=A9dric Chantepie
 Attachments: dtd.patch

Enumeration of values for attribute 'entity-mode' of element 'tuplizer' (po=
jo|dom4j|dynamic-map) does not match constants of class EntityMode.
For exemple, EntityMode.POJO.toString()equals("POJO") and so HbmBinder.loca=
teTuplizerDefinition cannot work (in this pojo case it does "POJO".equals("=
pojo") in fact).

The easiest way to fix that should be to change values in DTD if there is n=
o particular reason to change values in classes.

--=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: (HHH-1839) rename FlushMode.NEVER -> FlushMode.MANUAL

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

rename FlushMode.NEVER -> FlushMode.MANUAL
------------------------------------------

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

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


Initialy, just deprecate FlushMode.NEVER and add a new FlushMode.MANUAL...

-- 
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] Closed: (HHH-1839) rename FlushMode.NEVER -> FlushMode.MANUAL

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

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

    Resolution: Fixed

> rename FlushMode.NEVER -> FlushMode.MANUAL
> ------------------------------------------
>
>          Key: HHH-1839
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1839
>      Project: Hibernate3
>         Type: Task

>   Components: core
>     Reporter: Steve Ebersole
>     Assignee: Steve Ebersole
>     Priority: Trivial
>      Fix For: 3.2.0

>
>
> Initialy, just deprecate FlushMode.NEVER and add a new FlushMode.MANUAL...

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