hibernate-issues — Hibernate JIRA Notifications

[Hibernate-issues] [Hibernate-JIRA] Resolved: (ANN-398) OneToOne ignoring FetchType.LAZY

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

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

    Resolution: Rejected

User forum has to be used for usage requests

> OneToOne ignoring FetchType.LAZY
> --------------------------------
>
>          Key: ANN-398
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-398
>      Project: Hibernate Annotations
>         Type: Bug

>   Components: binder
>     Versions: 3.2.0.cr1
>     Reporter: Diego Pires Plentz
>     Priority: Blocker

>
>
> With annotation OneToOne, Hibernate is ignoring FetchType.LAZY
> @Entity
> @Table(name = "estudante", schema = "ingres", uniqueConstraints = {})
> public class Estudante implements java.io.Serializable {
> 	private Integer cdEstudante;
> 	private EstEnderecoPais estEnderecoPais;
> 	// Property accessors
> 	@Id
> 	@Column(name = "cd_estudante", unique = true, nullable = true, insertable = true, updatable = true)
> 	public Integer getCdEstudante() {
> 		return this.cdEstudante;
> 	}
> 	public void setCdEstudante(Integer cdEstudante) {
> 		this.cdEstudante = cdEstudante;
> 	}
> 	@OneToOne(cascade = {CascadeType.ALL}, fetch = FetchType.LAZY)
> 	@PrimaryKeyJoinColumn
> 	public EstEnderecoPais getEstEnderecoPais() {
> 		return this.estEnderecoPais;
> 	}
> 	public void setEstEnderecoPais(EstEnderecoPais estEnderecoPais) {
> 		this.estEnderecoPais = estEnderecoPais;
> 	}
> }
> ************
> @Entity
> @Table(name = "est_endereco_pais", schema = "ingres", uniqueConstraints = {})
> public class EstEnderecoPais implements java.io.Serializable {
> 	private Integer cdEstudante;
> 	private Estudante estudante;
> 	@Id
> 	@Column(name = "cd_estudante", unique = true, nullable = false, insertable = true, updatable = true)
> 	public Integer getCdEstudante() {
> 		return this.cdEstudante;
> 	}
> 	public void setCdEstudante(Integer cdEstudante) {
> 		this.cdEstudante = cdEstudante;
> 	}
> 	@OneToOne(cascade = {}, fetch = FetchType.LAZY)
> 	@PrimaryKeyJoinColumn
> 	public Estudante getEstudante() {
> 		return this.estudante;
> 	}
> 	public void setEstudante(Estudante estudante) {
> 		this.estudante = estudante;
> 	}
> }

-- 
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-398) OneToOne ignoring FetchType.LAZY

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

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

Emmanuel Bernard commented on ANN-398:
--------------------------------------

hum not "usage request", "usage".

> OneToOne ignoring FetchType.LAZY
> --------------------------------
>
>          Key: ANN-398
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-398
>      Project: Hibernate Annotations
>         Type: Bug

>   Components: binder
>     Versions: 3.2.0.cr1
>     Reporter: Diego Pires Plentz
>     Priority: Blocker

>
>
> With annotation OneToOne, Hibernate is ignoring FetchType.LAZY
> @Entity
> @Table(name = "estudante", schema = "ingres", uniqueConstraints = {})
> public class Estudante implements java.io.Serializable {
> 	private Integer cdEstudante;
> 	private EstEnderecoPais estEnderecoPais;
> 	// Property accessors
> 	@Id
> 	@Column(name = "cd_estudante", unique = true, nullable = true, insertable = true, updatable = true)
> 	public Integer getCdEstudante() {
> 		return this.cdEstudante;
> 	}
> 	public void setCdEstudante(Integer cdEstudante) {
> 		this.cdEstudante = cdEstudante;
> 	}
> 	@OneToOne(cascade = {CascadeType.ALL}, fetch = FetchType.LAZY)
> 	@PrimaryKeyJoinColumn
> 	public EstEnderecoPais getEstEnderecoPais() {
> 		return this.estEnderecoPais;
> 	}
> 	public void setEstEnderecoPais(EstEnderecoPais estEnderecoPais) {
> 		this.estEnderecoPais = estEnderecoPais;
> 	}
> }
> ************
> @Entity
> @Table(name = "est_endereco_pais", schema = "ingres", uniqueConstraints = {})
> public class EstEnderecoPais implements java.io.Serializable {
> 	private Integer cdEstudante;
> 	private Estudante estudante;
> 	@Id
> 	@Column(name = "cd_estudante", unique = true, nullable = false, insertable = true, updatable = true)
> 	public Integer getCdEstudante() {
> 		return this.cdEstudante;
> 	}
> 	public void setCdEstudante(Integer cdEstudante) {
> 		this.cdEstudante = cdEstudante;
> 	}
> 	@OneToOne(cascade = {}, fetch = FetchType.LAZY)
> 	@PrimaryKeyJoinColumn
> 	public Estudante getEstudante() {
> 		return this.estudante;
> 	}
> 	public void setEstudante(Estudante estudante) {
> 		this.estudante = estudante;
> 	}
> }

-- 
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-398) OneToOne ignoring FetchType.LAZY

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

OneToOne ignoring FetchType.LAZY
--------------------------------

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

  Components: binder  
    Versions: 3.2.0.cr1    
    Reporter: Diego Pires Plentz
    Priority: Blocker


With annotation OneToOne, Hibernate is ignoring FetchType.LAZY

@Entity
@Table(name = "estudante", schema = "ingres", uniqueConstraints = {})
public class Estudante implements java.io.Serializable {

	private Integer cdEstudante;
	private EstEnderecoPais estEnderecoPais;

	// Property accessors
	@Id
	@Column(name = "cd_estudante", unique = true, nullable = true, insertable = true, updatable = true)
	public Integer getCdEstudante() {
		return this.cdEstudante;
	}

	public void setCdEstudante(Integer cdEstudante) {
		this.cdEstudante = cdEstudante;
	}

	@OneToOne(cascade = {CascadeType.ALL}, fetch = FetchType.LAZY)
	@PrimaryKeyJoinColumn
	public EstEnderecoPais getEstEnderecoPais() {
		return this.estEnderecoPais;
	}

	public void setEstEnderecoPais(EstEnderecoPais estEnderecoPais) {
		this.estEnderecoPais = estEnderecoPais;
	}
}

************

@Entity
@Table(name = "est_endereco_pais", schema = "ingres", uniqueConstraints = {})
public class EstEnderecoPais implements java.io.Serializable {

	private Integer cdEstudante;

	private Estudante estudante;

	@Id
	@Column(name = "cd_estudante", unique = true, nullable = false, insertable = true, updatable = true)
	public Integer getCdEstudante() {
		return this.cdEstudante;
	}

	public void setCdEstudante(Integer cdEstudante) {
		this.cdEstudante = cdEstudante;
	}

	@OneToOne(cascade = {}, fetch = FetchType.LAZY)
	@PrimaryKeyJoinColumn
	public Estudante getEstudante() {
		return this.estudante;
	}

	public void setEstudante(Estudante estudante) {
		this.estudante = estudante;
	}
}

-- 
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-397) Incomplete AnnotationException at org.hibernate.cfg.annotations.TableBinder

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

Incomplete AnnotationException at org.hibernate.cfg.annotations.TableBinder
---------------------------------------------------------------------------

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

  Components: binder  
    Versions: 3.2.0.cr1    
    Reporter: Diego Pires Plentz


When a mapped class has the wrong number of fk collumns, an exception is throwed, but it doesnt say nothing about what class is mapped wrongly.

					//implicit case, we hope PK and FK columns are in the same order
					if ( columns.length != referencedEntity.getIdentifier().getColumnSpan() ) {
						throw new AnnotationException(
								"A Foreign key refering " + referencedEntity.getEntityName()
										+ " has the wrong number of column. should be " + referencedEntity.getIdentifier()
										.getColumnSpan()
						);
					}

Can become something like this...

					//implicit case, we hope PK and FK columns are in the same order
					if ( columns.length != referencedEntity.getIdentifier().getColumnSpan() ) {
						throw new AnnotationException(
								associatedClass.getEntityName() +
								" has a foreign key refering " + referencedEntity.getEntityName()
										+ " with the wrong number of column. should be " + referencedEntity.getIdentifier()
										.getColumnSpan()
						);
					}

-- 
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-1479) Incompatibility of Hibernate 3.1 and JTOpen JDBC drivers for IBM AS/400

[scott m g. (JIRA) <no...@at...>]

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

scott m gardner commented on HHH-1479:
--------------------------------------

One work around is to go back version 3.0.5. It still works in that release. That is what we are doing now.


> Incompatibility of Hibernate 3.1 and JTOpen JDBC drivers for IBM AS/400
> -----------------------------------------------------------------------
>
>          Key: HHH-1479
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1479
>      Project: Hibernate3
>         Type: Patch

>     Versions: 3.1
>  Environment: Hibernate 3.1
> JDBC driver: JTOpen (for IBM AS/400) http://jt400.sourceforge.net
>     Reporter: Davide Rogora

>
>
> Hello,
> I've noticed that from version 3.1 Hibernate, when calling JDBC driver for INSERT statement, uses the following prepareStatement method:
> prepareStatement(String sql, String[] columnNames)
> instead of the following
> prepareStatement(String sql, int autoGeneratedKeys)
> used since versione 3.0.x
> the problem is that JDBC driver for AS/400 (project JTOpen on sourceforge: http://jt400.sourceforge.net) doesn't support the method prepareStatement(String sql, String[] columnNames) so it's not possible to use Hibernate 3.1 with AS/400
> I've also noticed that other open source drivers that support this method (for example MySQL Jdbcconnector or JTDS for Ms-SQLServer) have implemented it using a workaround; infact they call the "old" prepareStatement(String sql, int autoGeneratedKeys) method ignoring the content of the columnNames array.
> Here is the source of the jtds implementation:
> -------------------------------------------------------------------------------
>     public PreparedStatement prepareStatement(String sql, String[] columnNames)
>             throws SQLException {
>         if (columnNames == null) {
>             throw new SQLException(
>                                   Messages.get("error.generic.nullparam", "prepareStatement"),"HY092");
>         } else if (columnNames.length != 1) {
>             throw new SQLException(
>                                   Messages.get("error.generic.needcolname", "prepareStatement"),"HY092");
>         }
>         return prepareStatement(sql, JtdsStatement.RETURN_GENERATED_KEYS);
>     }
> -------------------------------------------------------------------------------
> So I'm asking to the Hibernate team if it's possible to use the old method prepareStatement(String sql, int autoGeneratedKeys) in the future releases of Hibernate.
> Thanks,
> Davide Rogora.

-- 
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-1479) Incompatibility of Hibernate 3.1 and JTOpen JDBC drivers for IBM AS/400

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

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

Charles McGuire commented on HHH-1479:
--------------------------------------

We ran smack into this problem this week, too.

Any suggestions about how to work around this, short of stepping down to Hibernate 2?

> Incompatibility of Hibernate 3.1 and JTOpen JDBC drivers for IBM AS/400
> -----------------------------------------------------------------------
>
>          Key: HHH-1479
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1479
>      Project: Hibernate3
>         Type: Patch

>     Versions: 3.1
>  Environment: Hibernate 3.1
> JDBC driver: JTOpen (for IBM AS/400) http://jt400.sourceforge.net
>     Reporter: Davide Rogora

>
>
> Hello,
> I've noticed that from version 3.1 Hibernate, when calling JDBC driver for INSERT statement, uses the following prepareStatement method:
> prepareStatement(String sql, String[] columnNames)
> instead of the following
> prepareStatement(String sql, int autoGeneratedKeys)
> used since versione 3.0.x
> the problem is that JDBC driver for AS/400 (project JTOpen on sourceforge: http://jt400.sourceforge.net) doesn't support the method prepareStatement(String sql, String[] columnNames) so it's not possible to use Hibernate 3.1 with AS/400
> I've also noticed that other open source drivers that support this method (for example MySQL Jdbcconnector or JTDS for Ms-SQLServer) have implemented it using a workaround; infact they call the "old" prepareStatement(String sql, int autoGeneratedKeys) method ignoring the content of the columnNames array.
> Here is the source of the jtds implementation:
> -------------------------------------------------------------------------------
>     public PreparedStatement prepareStatement(String sql, String[] columnNames)
>             throws SQLException {
>         if (columnNames == null) {
>             throw new SQLException(
>                                   Messages.get("error.generic.nullparam", "prepareStatement"),"HY092");
>         } else if (columnNames.length != 1) {
>             throw new SQLException(
>                                   Messages.get("error.generic.needcolname", "prepareStatement"),"HY092");
>         }
>         return prepareStatement(sql, JtdsStatement.RETURN_GENERATED_KEYS);
>     }
> -------------------------------------------------------------------------------
> So I'm asking to the Hibernate team if it's possible to use the old method prepareStatement(String sql, int autoGeneratedKeys) in the future releases of Hibernate.
> Thanks,
> Davide Rogora.

-- 
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-1932) filter condition "(:param = true)" fails since "true" is parsed as this_.true

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

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

Josh Moore updated HHH-1932:
----------------------------

    Attachment: patch

Patch with the same information.

> filter condition "(:param = true)" fails since "true" is parsed as this_.true  
> -------------------------------------------------------------------------------
>
>          Key: HHH-1932
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1932
>      Project: Hibernate3
>         Type: Bug

>   Components: query-criteria
>     Versions: 3.2.0.cr2
>  Environment: Hibernate 3.2.cr2 AND
> URL: http://anonhibernate.labs.jboss.com/trunk/Hibernate3
> Revision: 10132
>     Reporter: Josh Moore
>  Attachments: DynamicFilterTest.java, Product.hbm.xml, defs.hbm.xml, patch
>
>
> A filter of the form (see attached defs.hbm.xml):
> 	<filter-def name="isOwner" condition=" ( :isOwner = true ) ">
> 		<filter-param name="isOwner" type="java.lang.Boolean"/>
> 	</filter-def>
> fails with the following exception thrown from attached testcase (modified DynamicFilterTest) :
> org.hibernate.exception.SQLGrammarException: could not execute query
> 	at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67)
> 	at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
> 	at org.hibernate.loader.Loader.doList(Loader.java:2147)
> 	at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2028)
> 	at org.hibernate.loader.Loader.list(Loader.java:2023)
> 	at org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:95)
> 	at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1569)
> 	at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:283)
> 	at org.hibernate.impl.CriteriaImpl.uniqueResult(CriteriaImpl.java:305)
> 	at org.hibernate.test.filter.DynamicFilterTest.testBooleanFilterOnCriteria(DynamicFilterTest.java:441)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at junit.framework.TestCase.runTest(TestCase.java:154)
> 	at org.hibernate.test.TestCase.runTest(TestCase.java:162)
> 	at junit.framework.TestCase.runBare(TestCase.java:127)
> 	at org.hibernate.test.TestCase.runBare(TestCase.java:401)
> 	at junit.framework.TestResult$1.protect(TestResult.java:106)
> 	at junit.framework.TestResult.runProtected(TestResult.java:124)
> 	at junit.framework.TestResult.run(TestResult.java:109)
> 	at junit.framework.TestCase.run(TestCase.java:118)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:208)
> 	at junit.framework.TestSuite.run(TestSuite.java:203)
> 	at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
> 	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
> Caused by: java.sql.SQLException: Column not found: THIS_.TRUE in statement [select this_.PROD_ID as PROD1_2_1_, this_.name as name2_1_, this_.STOCK_NUM as STOCK3_2_1_, this_.eff_start_dt as eff4_2_1_, this_.eff_end_dt as eff5_2_1_, categories2_.PROD_ID as PROD1_3_, category3_.CAT_ID as CAT2_3_, category3_.CAT_ID as CAT1_6_0_, category3_.name as name6_0_, category3_.eff_start_dt as eff3_6_0_, category3_.eff_end_dt as eff4_6_0_ from PRODUCT this_ left outer join PROD_CAT categories2_ on this_.PROD_ID=categories2_.PROD_ID left outer join CATEGORY category3_ on categories2_.CAT_ID=category3_.CAT_ID where  ( ? = this_.true ) and this_.PROD_ID=?]
> 	at org.hsqldb.jdbc.Util.throwError(Unknown Source)
> 	at org.hsqldb.jdbc.jdbcPreparedStatement.<init>(Unknown Source)
> 	at org.hsqldb.jdbc.jdbcConnection.prepareStatement(Unknown Source)
> 	at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:497)
> 	at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:415)
> 	at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:139)
> 	at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1561)
> 	at org.hibernate.loader.Loader.doQuery(Loader.java:661)
> 	at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224)
> 	at org.hibernate.loader.Loader.doList(Loader.java:2144)
> 	... 27 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-1932) filter condition "(:param = true)" fails since "true" is parsed as this_.true

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

filter condition "(:param = true)" fails since "true" is parsed as this_.true  
-------------------------------------------------------------------------------

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

  Components: query-criteria  
    Versions: 3.2.0.cr2    
 Environment: Hibernate 3.2.cr2 AND
URL: http://anonhibernate.labs.jboss.com/trunk/Hibernate3
Revision: 10132

    Reporter: Josh Moore
 Attachments: DynamicFilterTest.java, Product.hbm.xml, defs.hbm.xml

A filter of the form (see attached defs.hbm.xml):

	<filter-def name="isOwner" condition=" ( :isOwner = true ) ">
		<filter-param name="isOwner" type="java.lang.Boolean"/>
	</filter-def>

fails with the following exception thrown from attached testcase (modified DynamicFilterTest) :

org.hibernate.exception.SQLGrammarException: could not execute query
	at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67)
	at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
	at org.hibernate.loader.Loader.doList(Loader.java:2147)
	at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2028)
	at org.hibernate.loader.Loader.list(Loader.java:2023)
	at org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:95)
	at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1569)
	at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:283)
	at org.hibernate.impl.CriteriaImpl.uniqueResult(CriteriaImpl.java:305)
	at org.hibernate.test.filter.DynamicFilterTest.testBooleanFilterOnCriteria(DynamicFilterTest.java:441)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at junit.framework.TestCase.runTest(TestCase.java:154)
	at org.hibernate.test.TestCase.runTest(TestCase.java:162)
	at junit.framework.TestCase.runBare(TestCase.java:127)
	at org.hibernate.test.TestCase.runBare(TestCase.java:401)
	at junit.framework.TestResult$1.protect(TestResult.java:106)
	at junit.framework.TestResult.runProtected(TestResult.java:124)
	at junit.framework.TestResult.run(TestResult.java:109)
	at junit.framework.TestCase.run(TestCase.java:118)
	at junit.framework.TestSuite.runTest(TestSuite.java:208)
	at junit.framework.TestSuite.run(TestSuite.java:203)
	at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
Caused by: java.sql.SQLException: Column not found: THIS_.TRUE in statement [select this_.PROD_ID as PROD1_2_1_, this_.name as name2_1_, this_.STOCK_NUM as STOCK3_2_1_, this_.eff_start_dt as eff4_2_1_, this_.eff_end_dt as eff5_2_1_, categories2_.PROD_ID as PROD1_3_, category3_.CAT_ID as CAT2_3_, category3_.CAT_ID as CAT1_6_0_, category3_.name as name6_0_, category3_.eff_start_dt as eff3_6_0_, category3_.eff_end_dt as eff4_6_0_ from PRODUCT this_ left outer join PROD_CAT categories2_ on this_.PROD_ID=categories2_.PROD_ID left outer join CATEGORY category3_ on categories2_.CAT_ID=category3_.CAT_ID where  ( ? = this_.true ) and this_.PROD_ID=?]
	at org.hsqldb.jdbc.Util.throwError(Unknown Source)
	at org.hsqldb.jdbc.jdbcPreparedStatement.<init>(Unknown Source)
	at org.hsqldb.jdbc.jdbcConnection.prepareStatement(Unknown Source)
	at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:497)
	at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:415)
	at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:139)
	at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1561)
	at org.hibernate.loader.Loader.doQuery(Loader.java:661)
	at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224)
	at org.hibernate.loader.Loader.doList(Loader.java:2144)
	... 27 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] Updated: (HHH-1931) verify that the instrument tasks actually work

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

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

Steve Ebersole updated HHH-1931:
--------------------------------

    Attachment: InstrumentBugTest.zip

test bundle (minus libs)

> verify that the instrument tasks actually work
> ----------------------------------------------
>
>          Key: HHH-1931
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1931
>      Project: Hibernate3
>         Type: Task

>   Components: core
>     Reporter: Steve Ebersole
>     Assignee: Scott Marlow
>  Attachments: InstrumentBugTest.zip
>
>
> It appears they may not in all cases.

-- 
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-1931) verify that the instrument tasks actually work

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

verify that the instrument tasks actually work
----------------------------------------------

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

  Components: core  
    Reporter: Steve Ebersole
 Assigned to: Scott Marlow 


It appears they may not in all cases.

-- 
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-708) hbm2hbmxml misorders version, property from annotations

[Nate F. (JIRA) <no...@at...>]

hbm2hbmxml misorders version,property from annotations
------------------------------------------------------

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

  Components: ant  
    Versions: 3.2beta6    
 Environment: Hibernate Tools 3.2.0.beta6a
    Reporter: Nate Franzen
 Attachments: hibernate.bugreport.zip

Creating the mapping files from the annotations puts the xml elements in an invalid order:
<class>
<id/>
<property/>
<version/>
<property/>
</class> 

see also http://forum.hibernate.org/viewtopic.php?t=962308

The attached files reproduce the problem.
Step 1: set the hibernatetools.dir property to the correct value
Step 2: set the xerces.path property to the correct value
run "ant -f hibernate.build.xml"



-- 
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-396) NotNull validator doesn't work

[Celso G. B. Jr (JIRA) <no...@at...>]

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

Celso Gomes Barreto Jr commented on ANN-396:
--------------------------------------------

It's a pity that we can't rely on Hibernate calling Hibernate Validator just before an insert or update operation :(
Well, at least no with NotNull constraints.

Could you please post the key for the original bug this one duplicates so that we can watch it?


> NotNull validator doesn't work
> ------------------------------
>
>          Key: ANN-396
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-396
>      Project: Hibernate Annotations
>         Type: Bug

>     Versions: 3.2.0.cr1
>  Environment: Hibernate 3.2.0 CR2
> Hibernate Annotations 3.2.0 cr1
>     Reporter: Celso Gomes Barreto Jr
>     Priority: Critical

>
>
> Hibernate is throwing org.hibernate.PropertyValueException instead of org.hibernate.validator.InvalidStateException with @NotNull.
> A much better description from this problem (also a workaround) is avaiable at http://www.nearinfinity.com/blogs/page/jkunkle?entry=notnull_hibernate_annotation_validation_problems

-- 
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-1930) QuerySyntaxException "with-clause expressions did not reference from-clause element to which the with-clause was associated"

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

QuerySyntaxException "with-clause expressions did not reference from-clause element to which the with-clause was associated"
----------------------------------------------------------------------------------------------------------------------------

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

  Components: query-hql  
    Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2, 3.2.0.cr3    
    Reporter: Manfred Geiler


In Version 3.1.2 the following "EventManager" HQL query worked fine:

   select p from Person p join p.emailAddresses as email with email = 'xyz'

and produced an SQL query like this:

  select person0_.PERSON_ID as PERSON1_2_, person0_.age as age2_, person0_.firstname as firstname2_, person0_.lastname as lastname2_ 
   from PERSON person0_ 
   inner join PERSON_EMAIL_ADDR emailaddre1_ 
    on person0_.PERSON_ID=emailaddre1_.PERSON_ID and (emailaddre1_.EMAIL_ADDR='xyz')


>From Version 3.1.3 on this HQL throws the following QuerySyntaxException:
"with-clause expressions did not reference from-clause element to which the with-clause was associated"


-- 
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-396) NotNull validator doesn't work

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

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

Emmanuel Bernard commented on ANN-396:
--------------------------------------

there is an open bug with no workaround. It probably won't be fixed actually. The proper answer is to test your object graph before, in your business layer. This is very trivially done in JBoss Seam (an annotation on the business methods that need validation before beeing proceeded

> NotNull validator doesn't work
> ------------------------------
>
>          Key: ANN-396
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-396
>      Project: Hibernate Annotations
>         Type: Bug

>     Versions: 3.2.0.cr1
>  Environment: Hibernate 3.2.0 CR2
> Hibernate Annotations 3.2.0 cr1
>     Reporter: Celso Gomes Barreto Jr
>     Priority: Critical

>
>
> Hibernate is throwing org.hibernate.PropertyValueException instead of org.hibernate.validator.InvalidStateException with @NotNull.
> A much better description from this problem (also a workaround) is avaiable at http://www.nearinfinity.com/blogs/page/jkunkle?entry=notnull_hibernate_annotation_validation_problems

-- 
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: (HBX-638) null in parameter view

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

     [ http://opensource.atlassian.com/projects/hibernate/browse/HBX-638?page=all ]
     
Max Rydahl Andersen closed HBX-638:
-----------------------------------

    Fix Version: 3.2beta7
     Resolution: Fixed

done. There is now a checkbox after the value that if checkked will set null into query parameters.

> null in parameter view
> ----------------------
>
>          Key: HBX-638
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-638
>      Project: Hibernate Tools
>         Type: Improvement

>   Components: eclipse
>     Versions: 3.1beta4
>     Reporter: Max Rydahl Andersen
>      Fix For: 3.2beta7

>
>
> allow users to set NULL values for parameters in parameter view.

-- 
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-396) NotNull validator doesn't work

[Celso G. B. Jr (JIRA) <no...@at...>]

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

Celso Gomes Barreto Jr commented on ANN-396:
--------------------------------------------

Emmanuel

I saw your post on Jedd Kubkle blog saying that the workaround doesn't work on entities persisted by cascade. It's good to know this, I haven't test this situation.

I also saw that the status was changed to Duplicate. What is the original bug that this one duplicates? Is there any definitive workaround or else a true fix?

> NotNull validator doesn't work
> ------------------------------
>
>          Key: ANN-396
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-396
>      Project: Hibernate Annotations
>         Type: Bug

>     Versions: 3.2.0.cr1
>  Environment: Hibernate 3.2.0 CR2
> Hibernate Annotations 3.2.0 cr1
>     Reporter: Celso Gomes Barreto Jr
>     Priority: Critical

>
>
> Hibernate is throwing org.hibernate.PropertyValueException instead of org.hibernate.validator.InvalidStateException with @NotNull.
> A much better description from this problem (also a workaround) is avaiable at http://www.nearinfinity.com/blogs/page/jkunkle?entry=notnull_hibernate_annotation_validation_problems

-- 
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-1929) Parenthesis removal without honouring order in HQL query

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

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1929?page=all ]
     
Max Rydahl Andersen closed HHH-1929:
------------------------------------

    Resolution: Rejected

as requested by the user ;)

> Parenthesis removal without honouring order in HQL query
> --------------------------------------------------------
>
>          Key: HHH-1929
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1929
>      Project: Hibernate3
>         Type: Bug

>   Components: query-hql
>     Versions: 3.1.3, 3.2.0.cr3
>  Environment: Hibernate 3.1.3 and Hibernate 3.2.0.cr3, MySQL 5.0.22 community edition, Tomcat 5.5.17, Eclipse 3.2, WTP 1.5.0.2
>     Reporter: James Andrews
>     Priority: Critical

>
>
> Parenthesis in the where clause of a HQL query are being removed in the produced SQL query, modifying the results from those intended.
> The HQL used is as follows:
> select inv from Involvement inv
> left outer join inv.outcomes out
> where	 (
> 	out.type.needsDate = true
> 	and out.dateFinished <= now()
> ) or (
> 	out is null
> 	and inv.charge is not null
> ) or (
> 	out.dateCreated = (
> 		select	max(out2.dateCreated)
> 		from	Outcome out2
> 		where	out2.involvementId = inv.id
> 	) and out.type.terminal = false
> )
> group by inv.id
> And results in the following SQL:
> select
>   involvemen0_.involvementId as involvem1_2_,
>   involvemen0_.chargeId as chargeId2_,
>   involvemen0_.personId as personId2_,
>   involvemen0_.involvementTypeId as involvem4_2_ 
>  from
>   incident.involvement involvemen0_ 
>  left outer join
>   incident.outcome outcomes1_ 
>    on involvemen0_.involvementId=outcomes1_.involvementId,
>   incident.outcometype outcometyp2_ 
>  where
>   outcomes1_.typeId=outcometyp2_.typeId 
>   and (
>    outcometyp2_.needsDate=1 
>    and outcomes1_.dateFinished<=now() 
>    or (
>     outcomes1_.outcomeId is null
>    ) 
>    and (
>     involvemen0_.chargeId is not null
>    ) 
>    or outcomes1_.dateCreated=(
>     select
>      max(outcome3_.dateCreated) 
>     from
>      incident.outcome outcome3_ 
>     where
>      outcome3_.involvementId=involvemen0_.involvementId
>    ) 
>    and outcometyp2_.isTerminal=0
>   ) 
>  group by
>   involvemen0_.involvementId
> The initial subgroup of the clause is fine, however the ".charge is not null" and ".isTerminal = false" clauses are being promoted out of their subgroups, causing them to filter all results, rather than just those tuples with related criteria.
> This seems similar to issue HHH-377 and HHH-284, although it is not related to MySQL's issues with operator precedence, as the generated where clause does not fulfil the intent of the HQL where clause for any precedence rules.

-- 
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-1929) Parenthesis removal without honouring order in HQL query

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

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

James Andrews commented on HHH-1929:
------------------------------------

Eek, my apologies, the where clause is in fact equivelant through precedence, my mistake, I don't seem to be able to cancel or close this issue though.


> Parenthesis removal without honouring order in HQL query
> --------------------------------------------------------
>
>          Key: HHH-1929
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1929
>      Project: Hibernate3
>         Type: Bug

>   Components: query-hql
>     Versions: 3.1.3, 3.2.0.cr3
>  Environment: Hibernate 3.1.3 and Hibernate 3.2.0.cr3, MySQL 5.0.22 community edition, Tomcat 5.5.17, Eclipse 3.2, WTP 1.5.0.2
>     Reporter: James Andrews
>     Priority: Critical

>
>
> Parenthesis in the where clause of a HQL query are being removed in the produced SQL query, modifying the results from those intended.
> The HQL used is as follows:
> select inv from Involvement inv
> left outer join inv.outcomes out
> where	 (
> 	out.type.needsDate = true
> 	and out.dateFinished <= now()
> ) or (
> 	out is null
> 	and inv.charge is not null
> ) or (
> 	out.dateCreated = (
> 		select	max(out2.dateCreated)
> 		from	Outcome out2
> 		where	out2.involvementId = inv.id
> 	) and out.type.terminal = false
> )
> group by inv.id
> And results in the following SQL:
> select
>   involvemen0_.involvementId as involvem1_2_,
>   involvemen0_.chargeId as chargeId2_,
>   involvemen0_.personId as personId2_,
>   involvemen0_.involvementTypeId as involvem4_2_ 
>  from
>   incident.involvement involvemen0_ 
>  left outer join
>   incident.outcome outcomes1_ 
>    on involvemen0_.involvementId=outcomes1_.involvementId,
>   incident.outcometype outcometyp2_ 
>  where
>   outcomes1_.typeId=outcometyp2_.typeId 
>   and (
>    outcometyp2_.needsDate=1 
>    and outcomes1_.dateFinished<=now() 
>    or (
>     outcomes1_.outcomeId is null
>    ) 
>    and (
>     involvemen0_.chargeId is not null
>    ) 
>    or outcomes1_.dateCreated=(
>     select
>      max(outcome3_.dateCreated) 
>     from
>      incident.outcome outcome3_ 
>     where
>      outcome3_.involvementId=involvemen0_.involvementId
>    ) 
>    and outcometyp2_.isTerminal=0
>   ) 
>  group by
>   involvemen0_.involvementId
> The initial subgroup of the clause is fine, however the ".charge is not null" and ".isTerminal = false" clauses are being promoted out of their subgroups, causing them to filter all results, rather than just those tuples with related criteria.
> This seems similar to issue HHH-377 and HHH-284, although it is not related to MySQL's issues with operator precedence, as the generated where clause does not fulfil the intent of the HQL where clause for any precedence rules.

-- 
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-1929) Parenthesis removal without honouring order in HQL query

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

Parenthesis removal without honouring order in HQL query
--------------------------------------------------------

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

  Components: query-hql  
    Versions: 3.1.3, 3.2.0.cr3    
 Environment: Hibernate 3.1.3 and Hibernate 3.2.0.cr3, MySQL 5.0.22 community edition, Tomcat 5.5.17, Eclipse 3.2, WTP 1.5.0.2
    Reporter: James Andrews
    Priority: Critical


Parenthesis in the where clause of a HQL query are being removed in the produced SQL query, modifying the results from those intended.


The HQL used is as follows:


select inv from Involvement inv
left outer join inv.outcomes out
where	 (
	out.type.needsDate = true
	and out.dateFinished <= now()
) or (
	out is null
	and inv.charge is not null
) or (
	out.dateCreated = (
		select	max(out2.dateCreated)
		from	Outcome out2
		where	out2.involvementId = inv.id
	) and out.type.terminal = false
)
group by inv.id


And results in the following SQL:


select
  involvemen0_.involvementId as involvem1_2_,
  involvemen0_.chargeId as chargeId2_,
  involvemen0_.personId as personId2_,
  involvemen0_.involvementTypeId as involvem4_2_ 
 from
  incident.involvement involvemen0_ 
 left outer join
  incident.outcome outcomes1_ 
   on involvemen0_.involvementId=outcomes1_.involvementId,
  incident.outcometype outcometyp2_ 
 where
  outcomes1_.typeId=outcometyp2_.typeId 
  and (
   outcometyp2_.needsDate=1 
   and outcomes1_.dateFinished<=now() 
   or (
    outcomes1_.outcomeId is null
   ) 
   and (
    involvemen0_.chargeId is not null
   ) 
   or outcomes1_.dateCreated=(
    select
     max(outcome3_.dateCreated) 
    from
     incident.outcome outcome3_ 
    where
     outcome3_.involvementId=involvemen0_.involvementId
   ) 
   and outcometyp2_.isTerminal=0
  ) 
 group by
  involvemen0_.involvementId


The initial subgroup of the clause is fine, however the ".charge is not null" and ".isTerminal = false" clauses are being promoted out of their subgroups, causing them to filter all results, rather than just those tuples with related criteria.

This seems similar to issue HHH-377 and HHH-284, although it is not related to MySQL's issues with operator precedence, as the generated where clause does not fulfil the intent of the HQL where clause for any precedence rules.


-- 
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-484) order-by not applied to collections fetched by OuterJoinLoader

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

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

Nguyen Hau Giang commented on HHH-484:
--------------------------------------

When querying by Criteria with join-fetch or left-join-alias.
order-by of collection mappings is prior to order-by specified in Criteria.
Please see HHH-1928

> order-by not applied to collections fetched by OuterJoinLoader
> --------------------------------------------------------------
>
>          Key: HHH-484
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-484
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.0.4
>     Reporter: Gavin King
>     Assignee: Gavin King
>      Fix For: 3.0.4

>
>
> Currently, the collection order-by is not applied when we fetch a collection using OuterJoinLoader (ie. from get()/load()/criteria query).

-- 
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-594) order-by mapping for collections overrides order by in HQL

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

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

Nguyen Hau Giang commented on HHH-594:
--------------------------------------

I met the same problem when querying by Criteria with join-fetch or left-join-alias.
Please see HHH-1928

> order-by mapping for collections overrides order by in HQL
> ----------------------------------------------------------
>
>          Key: HHH-594
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-594
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.0.4
>  Environment: Hibernate v3.0.4, Oracle 8i
>     Reporter: Jim Reed
>     Assignee: Gavin King
>      Fix For: 3.1 beta 1

>
>
> In Hibernate v2.1 if you included an order-by in the mapping for a collection, that order by would automatically be concatenated onto any order by clause in your HQL.  This allows you to sort your list of Hibernate objects and also sort the collections within those objects.  In Hibernate v3.0, however, the order-by clause in the mapping for a collection completely overrides an order by for your HQL.
> Example:
> Mapping file:
> <hibernate-mapping package="com.mycompany.hibernate">
> 	<class name="Client" table="CLIENT">
> 		<id
> 			column="CLIENT_ID"
> 			name="id"
> 			type="integer"
> 		>
> 			<generator class="vm" />
> 		</id>
> 		<property
> 			column="NAME"
> 			length="255"
> 			name="name"
> 			not-null="true"
> 			type="string"
> 		 />
> 		<set
> 			name="contactSet"
> 			inverse="true"
> 			lazy="true"
> 			order-by="LAST_NAME asc"
> 		>
> 		<key column="CLIENT_ID" />
> 		<one-to-many class="Contact" />
> 		</set>
> 	</class>
> </hibernate-mapping>
> HQL:
> from com.mycompany.hibernate.Client c, c.contactSet cs
> order by c.name
> Hibernate v2.1 SQL:
> select c1.name,c2.first_name,c2.lastname
> from client c1, contact c2
> order by c1.name, c2.last_name
> Hibernate v3.0 SQL:
> select c1.name,c2.first_name,c2.lastname
> from client c1, contact c2
> order by c2.last_name

-- 
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-1928) order-by mapping for collections overrides order by in Criteria

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

order-by mapping for collections overrides order by in Criteria
---------------------------------------------------------------

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

  Components: query-criteria  
    Versions: 3.2.0.cr3    
    Reporter: Nguyen Hau Giang
 Attachments: testcase.zip

relating to:
   HHH-594(order-by mapping for collections overrides order by in HQL)
   HHH-484(order-by not applied to collections fetched by OuterJoinLoader)

Mapping(pseudo code):
	<class name="Master">
		<id name="id" />		
		<set name="details" order-by="DISP_NO">
			<one-to-many class="Detail" />
		</set>
	</class>

	<class name="Detail">
		<id name="id" />
		<property name="dispNo" />
		<many-to-one name="master" class="Master" />
	</class>

Same problem as in HHH-594, but instead of querying by HQL, when query by Criteria using join-fetch:
		session.createCriteria(Master.class)//
				.setFetchMode("details", FetchMode.JOIN)//
				.addOrder(Order.asc("id"))//
				.list();

order-by mapping for collection overrides order by in Criteria:
    from
        Master this_ 
    left outer join
        Detail details2_ 
            on this_.id=details2_.ID 
    order by
        details2_.DISP_NO,
        this_.id asc

or when creating left-join alias:
		session.createCriteria(Master.class)//
				.createAlias("details", "D", Criteria.LEFT_JOIN)//
				.addOrder(Order.asc("id"))//
				.list();
generated SQL:
    from
        Master this_ 
    left outer join
        Detail d1_ 
            on this_.id=d1_.ID 
    order by
        d1_.DISP_NO,
        this_.id asc

The order property specified in Criteria should be prior to order of collection mapping. 
I think this problem should be fixed as with HQL in HHH-594.
For details, please see attached 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] Resolved: (HHH-1903) Incorrect classpath for starting HSQL in Hibernate Reference PDF

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

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

    Resolution: Won't Fix

This is in current subversion: "Now start the database by running <literal>java -classpath ../lib/hsqldb.jar org.hsqldb.Server</literal> in this data directory."

> Incorrect classpath for starting HSQL in Hibernate Reference PDF
> ----------------------------------------------------------------
>
>          Key: HHH-1903
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1903
>      Project: Hibernate3
>         Type: Bug

>   Components: documentation
>     Versions: 3.1.1
>  Environment: N/A
>     Reporter: Jack C. Holt

>
>
> In the last paragraph on page 4 the following sentence, "Now start the database by running java -classpath lib/hsqldb.jar org.hsqldb.Server in this
> data directory", is incorrect.  The following error appears when you try it from the data directory (as the document states you should do).
>         Exception in thread "main" java.lang.NoClassDefFoundError: org/hsqldb/Server
> The sentence should read "Now start the database by running java -classpath ../lib/hsqldb.jar org.hsqldb.Server in this
> data directory."

-- 
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-1906) Incorrect code in Hibernate 3.1.1 Reference PDF

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

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

    Resolution: Won't Fix

1. That is why the tutorial includes that statement just before the code snippet: "you might have to modify some of the previous methods to return that identifier"

2. The included tutorial source code includes this modified code ready for copy/paste.

3. The missing } has been fixed.


> Incorrect code in Hibernate 3.1.1 Reference PDF
> -----------------------------------------------
>
>          Key: HHH-1906
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1906
>      Project: Hibernate3
>         Type: Bug

>   Components: documentation
>     Versions: 3.1.1, 3.1.2, 3.1.3
>  Environment: N/A
>     Reporter: Jack C. Holt

>
>
> the last code snippet in section 1.3.3 on page 13 shows the following code: 
>     Long eventId = mgr.createAndStoreEvent("My Event", new Date());
>     Long personId = mgr.createAndStorePerson("Foo", "Bar");
> Both methods are defined as returning void, not Long. Therefore, the code causes a compiler error.
> The code snippet is also missing a closing "}".

-- 
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-396) NotNull validator doesn't work

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

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

    Resolution: Duplicate

The workaround does not work

> NotNull validator doesn't work
> ------------------------------
>
>          Key: ANN-396
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-396
>      Project: Hibernate Annotations
>         Type: Bug

>     Versions: 3.2.0.cr1
>  Environment: Hibernate 3.2.0 CR2
> Hibernate Annotations 3.2.0 cr1
>     Reporter: Celso Gomes Barreto Jr
>     Priority: Critical

>
>
> Hibernate is throwing org.hibernate.PropertyValueException instead of org.hibernate.validator.InvalidStateException with @NotNull.
> A much better description from this problem (also a workaround) is avaiable at http://www.nearinfinity.com/blogs/page/jkunkle?entry=notnull_hibernate_annotation_validation_problems

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