hibernate-issues — Hibernate JIRA Notifications

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-244) Hibernate creates alias identifiers that are too long

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Kevin Yeung
    Created: Wed, 27 Aug 2003 4:53 AM
       Body:
I did a quick hack with cirrus.hibernate.helpers.StringHelper.suffix() to return the first 30 characters (or less). And it seems to work. Can anyone advise if I'm breaking anything?

Of course it'd be prudent to set the limit based on the dialect (Oracle has a limit of 30 so I'm hardcoding it for myself).
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-244


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-244
    Summary: Hibernate creates alias identifiers that are too long
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.2

   Assignee: 
   Reporter: Mark Woon

    Created: Mon, 11 Aug 2003 1:17 AM
    Updated: Mon, 11 Aug 2003 5:21 AM
Environment: Oracle 9.0.2.

Description:
After switching to Hibernate 2 I find that Hibernate is still creating alias identifiers that are too long.

The HQL query that's causing it:
select freqInSs, freqInRae, freqInSs.allele
from DbVariantPosition as varPos,
DbVariantAllele as varAl,
DbAlleleFrequencyInSampleSet as freqInSs,
DbAlleleFrequencyInRaceAndEthnicity as freqInRae
where varPos.goldenPathPosition = ?
and varPos.id != ?
order by freqInSs, freqInRae

The SQL query that gets generated:
select dballele2_.alleleFreqInSampleSetsId as alleleFreqInSampleSetsId0_, dballele3_.alleleFreqInSSRaceEthnicityId as alleleFreqInSSRaceEthnicityId1_, dballele2_.variantPositionId as variantP2_0_, dballele2_.sampleSetId as sampleSe3_0_, dballele2_.allele as allele0_, dballele2_.totalObserved as totalObs5_0_, dballele2_.frequency as frequency0_, dballele3_.alleleFreqInSampleSetId as alleleFr2_1_, dballele3_.racialClassId as racialCl3_1_, dballele3_.ethnicClassId as ethnicCl4_1_, dballele3_.totalObserved as totalObs5_1_, dballele3_.frequency as frequency1_, dballele2_.alleleFreqInSampleSetsId as x0_0_, dballele3_.alleleFreqInSSRaceEthnicityId as x1_0_, dballele2_.allele as x2_0_ from VariantPositions dbvarian0_, VariantAlleles dbvarian1_, AlleleFreqInSampleSets dballele2_, AlleleFreqInSSRaceEthnicity dballele3_ where (dbvarian0_.goldenPathPosition=? )and(dbvarian0_.variantPositionId!=? ) order by  dballele2_.alleleFreqInSampleSetsId , dballele3_.alleleFreqInSSRaceEthnicityId


The offending alias identifier is "alleleFreqInSSRaceEthnicityId1_" which is 31 characters long -- one more that Oracle's max identifier length.

Is this a known problem?  I can attach my mappings if it will help...


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-293) Seperating InterBase and Firebird dialects

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Reha CENANI
    Created: Wed, 27 Aug 2003 4:45 AM
       Body:
Regarding the Sequence value and string issues:

*** Common ***
supportsSequences() --> true

getCreateSequenceString(String sequenceName) -->
"CREATE GENERATOR " + sequenceName

getSequenceNextValString(String sequenceName) -->
"SELECT GEN_ID(" + sequenceName + ", 1) FROM RDB$DATABASE"

*** For Firebird: ***
getDropSequenceString(String sequenceName) -->
"DROP GENERATOR " + sequenceName

*** For InterBase: ***
getDropSequenceString(String sequenceName) -->
"DELETE FROM RDB$GENERATORS WHERE RDB$GENERATOR_NAME = '" + sequenceName.toUpperCase() + "'"


---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-293


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-293
    Summary: Seperating InterBase and Firebird dialects
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: Reha CENANI

    Created: Tue, 26 Aug 2003 6:46 AM
    Updated: Tue, 26 Aug 2003 6:46 AM

Description:
At the begining, opensource Firebird (or FirebirdSQL) was based on the same source code of commercial InterBase. But during past three years, lots of improvements are done to the Firebird. Recent versions of these DBMSs have different features and statement syntaxes. 

For example, their select offset/limit statement syntaxes are not compatible. Hibernate's recent InterbaseDialect select limit/offset feature is based on the Firebird's select statement syntax.

So, in order to prevent incompabilities and confussion, in addition to the InterbaseDialect, adding a new FirebirdDialect and seperating Firebird and InterBase features will be very helpfull.





---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-293) Seperating InterBase and Firebird dialects

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Reha CENANI
    Created: Wed, 27 Aug 2003 2:45 AM
       Body:
Regarding the select limit issues, please find below the explanations from their documentations.

*** For Firebird: ***
SELECT [FIRST (<integer expr m>)] [SKIP (<integer expr n>)] ...

Retrieves the first m rows of the selected output set. The optional SKIP clause will cause the first n rows to be discarded and return an output set of m rows starting at n + 1. In the simplest form, m and n are integers but any Firebird expression that evaluates to an integer is valid. Parentheses are required for expression arguments and optional otherwise.

bindLimitParametersFirst() --> true
bindLimitParametersInReverseOrder() --> true


*** For InterBase: ***
SELECT ... [ROWS <value> [TO <upper_value>] [BY <step_value>] [PERCENT] [WITH TIES]]

* <value> is the total number of rows to return if used by itself
* <value> is the starting row number to return if used with TO
* <value> is the percent if used with PERCENT
* <upper_value> is the last row or highest percent to return
* If <step_value> = n, returns every n'th row, or n percent rows
* PERCENT causes all previous ROWS values to be interpreted as percents
* WITH TIES returns additional duplicate rows when the last value in the ordered sequence is the same as values in subsequent rows of the result set; must be used in conjunction with ORDER BY

bindLimitParametersFirst() --> false
bindLimitParametersInReverseOrder() --> false


---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-293


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-293
    Summary: Seperating InterBase and Firebird dialects
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: Reha CENANI

    Created: Tue, 26 Aug 2003 6:46 AM
    Updated: Tue, 26 Aug 2003 6:46 AM

Description:
At the begining, opensource Firebird (or FirebirdSQL) was based on the same source code of commercial InterBase. But during past three years, lots of improvements are done to the Firebird. Recent versions of these DBMSs have different features and statement syntaxes. 

For example, their select offset/limit statement syntaxes are not compatible. Hibernate's recent InterbaseDialect select limit/offset feature is based on the Firebird's select statement syntax.

So, in order to prevent incompabilities and confussion, in addition to the InterbaseDialect, adding a new FirebirdDialect and seperating Firebird and InterBase features will be very helpfull.





---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-184) Connection Timeout Exception using MySQL and DBCP

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Maarten Coene
    Created: Wed, 27 Aug 2003 2:00 AM
       Body:
Please reopen this issue ...

>(a) you can work around this using DBCP connection validation 

No, this won't work because DBCP tries to activate the Connection before it's being validated. But activating the Connection when autoCommit is false throws an Exception (only with MySQL and after 8 hours of inactivity) in the borrowObject() method of the pool which is propagated as an SQLException in the getConnection() method of the PoolingDataSource. 

>(b) calling setAutocommit() is expensive for some (most?) DBs 

I didn't notice any performance degradation of my application. Also, hibernate sets the autoCommit option in the C3P0ConnectionProvider almost the same way as I proposed in the patch. Why not doing it the same way for both the C3P0ConnectionProvider an the DBCPConnectionProvider?

>(c) this should really be addressed by patching the MySQL driver, NOT Hibernate! 

I agree and these patches are already submitted to MySQL (not by me, but by others). But in the meantime I cannot use the "official" hibernate builds because of this issue which can be solved easily. 

Maarten Coene
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-184


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-184
    Summary: Connection Timeout Exception using MySQL and DBCP
       Type: Patch

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2

   Assignee: 
   Reporter: Maarten Coene

    Created: Fri, 11 Jul 2003 9:21 AM
    Updated: Tue, 26 Aug 2003 11:51 PM
Environment: Linux

Description:
Hi,

The MySQL database closes by default it connections after 8 hours. If these connections are pooled, a "Connetion Timeout" exception will be thrown if you try to access the connection. The best way to solve this is to add ?autoReconnect=true to the jdbc url.

But this doesn't work with Hibernate and DBCP.

The reason is that this option only works if the autoCommit attribute is set to true and the DBCPConnectionProvider of Hibernate sets this to false by default. I've created a patch to fix this problem.

thx
Maarten Coene



Index: DBCPConnectionProvider.java
===================================================================
RCS file: /cvsroot/hibernate/Hibernate2/src/net/sf/hibernate/connection/DBCPConnectionProvider.java,v
retrieving revision 1.8
diff -u -r1.8 DBCPConnectionProvider.java
--- DBCPConnectionProvider.java	25 Apr 2003 03:40:31 -0000	1.8
+++ DBCPConnectionProvider.java	11 Jul 2003 14:12:09 -0000
@@ -42,6 +42,7 @@
 		try {
 			final Connection c = ds.getConnection();
 			if (isolation!=null) c.setTransactionIsolation( isolation.intValue() );
+                        c.setAutoCommit(false);
 			return c;
 		}
 		catch (SQLException sqle) {
@@ -56,6 +57,7 @@
 	
 	public void closeConnection(Connection conn) throws SQLException {
 		try {
+                        conn.setAutoCommit(true);
 			conn.close();
 		}
 		catch (SQLException sqle) {
@@ -119,7 +121,7 @@
 			// the "real" Connections created by the ConnectionFactory with
 			// the classes that implement the pooling functionality.
 			String validationQuery = props.getProperty(Environment.DBCP_VALIDATION_QUERY);
-			new PoolableConnectionFactory(connectionFactory, connectionPool, statementPool, validationQuery, false, false);
+			new PoolableConnectionFactory(connectionFactory, connectionPool, statementPool, validationQuery, false, true);
 			
 			// Finally, we create the PoolingDriver itself,
 			// passing in the object pool we created.



---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-51) Full feature support of DBCP and validation query bugfix

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Tue, 26 Aug 2003 11:58 PM

There are too many extra properties here. We don't need them all!
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-51


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-51
    Summary:  Full feature support of DBCP and validation query bugfix
       Type: Patch

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2

   Assignee: Gavin King
   Reporter: Max Rydahl Andersen

    Created: Sat, 3 May 2003 10:33 AM
    Updated: Tue, 26 Aug 2003 11:58 PM

Description:
Full feature support of DBCP and validation query bugfix
The following patch extends Hibernate 1.2.4 to support 
all features of the DBCP connection pool. 

Added configuration parameters: 

# connection pool 
hibernate.dbcp.testOnBorrow true 
hibernate.dbcp.testOnReturn false 
hibernate.dbcp.timeBetweenEvictionRunsMillis 900000 
hibernate.dbcp.numTestsPerEvictionRun 10 
hibernate.dbcp.minEvictableIdleTimeMillis 1800000 
hibernate.dbcp.testWhileIdle true 

# prepared statement cache 
hibernate.dbcp.ps.testOnBorrow true 
hibernate.dbcp.ps.testOnReturn false 
hibernate.dbcp.ps.timeBetweenEvictionRunsMillis 900000 
hibernate.dbcp.ps.numTestsPerEvictionRun 10 
hibernate.dbcp.ps.minEvictableIdleTimeMillis 1800000 
hibernate.dbcp.ps.testWhileIdle true 

Bug fixed: 
Although it was possible to configure a validation 
query for the pool, this query was never executed, 
because the DBCP properties "testOnBorrow" or 
"testOnReturn" were never enabled by Hibernate

http://sourceforge.net/tracker/index.php?func=detail&aid=729870&group_id=40712&atid=428710


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-184) Connection Timeout Exception using MySQL and DBCP

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Tue, 26 Aug 2003 11:51 PM

I'm rejecting this because

(a) you can work around this using DBCP connection validation
(b) calling setAutocommit() is expensive for some (most?) DBs
(c) this should really be addressed by patching the MySQL driver, NOT Hibernate!

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-184


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-184
    Summary: Connection Timeout Exception using MySQL and DBCP
       Type: Patch

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2

   Assignee: 
   Reporter: Maarten Coene

    Created: Fri, 11 Jul 2003 9:21 AM
    Updated: Tue, 26 Aug 2003 11:51 PM
Environment: Linux

Description:
Hi,

The MySQL database closes by default it connections after 8 hours. If these connections are pooled, a "Connetion Timeout" exception will be thrown if you try to access the connection. The best way to solve this is to add ?autoReconnect=true to the jdbc url.

But this doesn't work with Hibernate and DBCP.

The reason is that this option only works if the autoCommit attribute is set to true and the DBCPConnectionProvider of Hibernate sets this to false by default. I've created a patch to fix this problem.

thx
Maarten Coene



Index: DBCPConnectionProvider.java
===================================================================
RCS file: /cvsroot/hibernate/Hibernate2/src/net/sf/hibernate/connection/DBCPConnectionProvider.java,v
retrieving revision 1.8
diff -u -r1.8 DBCPConnectionProvider.java
--- DBCPConnectionProvider.java	25 Apr 2003 03:40:31 -0000	1.8
+++ DBCPConnectionProvider.java	11 Jul 2003 14:12:09 -0000
@@ -42,6 +42,7 @@
 		try {
 			final Connection c = ds.getConnection();
 			if (isolation!=null) c.setTransactionIsolation( isolation.intValue() );
+                        c.setAutoCommit(false);
 			return c;
 		}
 		catch (SQLException sqle) {
@@ -56,6 +57,7 @@
 	
 	public void closeConnection(Connection conn) throws SQLException {
 		try {
+                        conn.setAutoCommit(true);
 			conn.close();
 		}
 		catch (SQLException sqle) {
@@ -119,7 +121,7 @@
 			// the "real" Connections created by the ConnectionFactory with
 			// the classes that implement the pooling functionality.
 			String validationQuery = props.getProperty(Environment.DBCP_VALIDATION_QUERY);
-			new PoolableConnectionFactory(connectionFactory, connectionPool, statementPool, validationQuery, false, false);
+			new PoolableConnectionFactory(connectionFactory, connectionPool, statementPool, validationQuery, false, true);
 			
 			// Finally, we create the PoolingDriver itself,
 			// passing in the object pool we created.



---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Assigned: (HB-155) Optimistic locking by columns' original values

[<leg...@at...>]

Message:

   The following issue has been re-assigned.

   Assignee: Gavin King (mailto:ga...@in...)
   Assigner: Gavin King (mailto:ga...@in...)
       Date: Tue, 26 Aug 2003 1:41 PM
    Comment:
I plan to implement this soon.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-155


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-155
    Summary: Optimistic locking by columns' original values
       Type: New Feature

     Status: Assigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: Gavin King
   Reporter: TURIN ACCOUNT

    Created: Tue, 8 Jul 2003 3:36 PM
    Updated: Tue, 26 Aug 2003 1:41 PM

Description:
 Ability to support optimistic locking by columns' original values.  When UPDATE statements
are generated, in addition to the primary key, the WHERE clause includes either all of the
columns' original values, or just the changed columns' original values.  This allows
optimistic locking without requiring the datamodel to have a "timestamp" or "version"
column.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-14) Problem in ReverseGenerator (sequence generator class)

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Tue, 26 Aug 2003 1:37 PM

ReverseGenerator is deprecated.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-14


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-14
    Summary: Problem in ReverseGenerator (sequence generator class)
       Type: Bug

     Status: Closed
   Priority: Minor
 Resolution: WON'T FIX

    Project: Hibernate2
   Versions:
             2.0rc2

   Assignee: 
   Reporter: Max Rydahl Andersen

    Created: Sat, 3 May 2003 10:03 AM
    Updated: Tue, 26 Aug 2003 1:37 PM

Description:
Problem in sequence generator class.

The ReverseGenerator tool generate wrong wml 
configuration for the generator tag and DOCTYPE. 

The generated doctype still refers to 1.1, it should 
rever to 2.0. 

Apparently, generator tag is modified in 2.0 when 
sequence is used as the generator class. In 2.0, the 
param tag expects a 'name' attribute while in 1.0 the 
name was specified as the normal text attribute. 
Failing to configure that parameter correclty, 
generates a NullPointerException in the 
configure.buildSessionFactory(). 

(original: http://sourceforge.net/tracker/index.php?func=detail&aid=720678&group_id=40712&atid=428708)


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-178) Serialization of SessionFactory fails with Tomcat context reload

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Tue, 26 Aug 2003 1:36 PM

This is expected. The "serialized" SessionFactory is in fact just a name; it doesn't serialize the whole state. You need to rebuild the factory if you restart.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-178


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-178
    Summary: Serialization of SessionFactory fails with Tomcat context reload
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.0.2
   Versions:
             2.0.1

   Assignee: 
   Reporter: TURIN ACCOUNT

    Created: Thu, 10 Jul 2003 6:35 PM
    Updated: Tue, 26 Aug 2003 1:36 PM
Environment: Linux, Tomcat 4.1.24, JDK 1.4.1, tested with current CVS

Description:
When Tomcat reloads an app context, the SessionFactory and its Sessions are loaded from the HttpSession files. I thought this would be fixed with the "null" in the UUIDGenerator fix, but it still throws an Exception on context restart. Everything else works fine, so no showstopper.

StandardManager[]: Seeding random number generator class java.security.SecureRandom

StandardManager[]: Seeding of random number generator has been completed

APP -  WARN - SessionFactoryObjectFactory - Not found: ff808081f64e8ea500f64e8ea78e0000
APP -  WARN - SessionFactoryObjectFactory - Not found: null

StandardManager[] IOException while loading persisted sessions: java.io.InvalidObjectException: Could not find a SessionFactory named: null
java.io.InvalidObjectException: Could not find a SessionFactory named: null
        at net.sf.hibernate.impl.SessionFactoryImpl.readResolve(SessionFactoryImpl.java:526)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at java.io.ObjectStreamClass.invokeReadResolve(ObjectStreamClass.java:911)
        at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1655)
        at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
        at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
        at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:452)
        at net.sf.hibernate.impl.SessionImpl.readObject(SessionImpl.java:348)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:824)
        at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1746)
        at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
        at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
        at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
        at org.apache.catalina.session.StandardSession.readObject(StandardSession.java:1369)
        at org.apache.catalina.session.StandardSession.readObjectData(StandardSession.java:864)
        at org.apache.catalina.session.StandardManager.load(StandardManager.java:440)
        at org.apache.catalina.session.StandardManager.start(StandardManager.java:655)
        at org.apache.catalina.core.StandardContext.reload(StandardContext.java:2572)
        at org.apache.catalina.loader.WebappLoader$WebappContextNotifier.run(WebappLoader.java:1369)
        at java.lang.Thread.run(Thread.java:536)





---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-151) Traversing several joined-subclasses in where clause leaves out inner joins

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Tue, 26 Aug 2003 1:33 PM

I am closing this, because there was never enough information to reproduce this.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-151


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-151
    Summary: Traversing several joined-subclasses in where clause leaves out inner joins
       Type: Bug

     Status: Closed
   Priority: Critical
 Resolution: CANNOT REPRODUCE

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: Gavin King
   Reporter: TURIN ACCOUNT

    Created: Tue, 8 Jul 2003 3:32 PM
    Updated: Tue, 26 Aug 2003 1:33 PM
Environment: WSAD 5.0.1, JDK 1.3.1, Oracle 9i, Windows 2000

Description:
Class-diagram:
 a-->b  a inherits from b
 a==b   a has relationship to b
 
 (Sorry, classnames are in Dutch)
 
 Persoon == Beroepsuitoefening
 Beroepsuitoefening <-- Jurist
 Jurist == Bevoegdheid
 Bevoegdheid <-- Beediging <-- Procureurschap
 
 If my query contains 'where jurist.persoon.naam like ?', the generated SQL looks like this
(which is OK):
 
 select count(*) as x0_0_ 
 from jurist persiste0_ 
 	inner join beroepsuitoefening persiste0__1 on persiste0_.beg_id=persiste0__1.id, 
 persoon persiste1_ 
 where (
 	(
 		persiste1_.naam like ?  
 		and persiste0__1.psn_id=persiste1_.id
 	)
 )
 
 
 However, if I start one level deeper in the hierarchy ('where
procureurschap.jurist.persoon.naam like ?') the SQL query looks like this:
 
 select count(*) as x0_0_ 
 from procureurschap persiste0_ 
 	inner join beediging persiste0__1 on persiste0_.bvh_id=persiste0__1.bvh_id 
 	inner join bevoegdheid persiste0__2 on persiste0_.bvh_id=persiste0__2.id, 
 jurist persiste1_, 
 persoon persiste2_ 
 
 where (
 	(
 		persiste2_.naam=?  
 		and persiste0__2.beg_id=persiste1_.beg_id 
 		and persiste1__1.psn_id=persiste2_.id
 	)
 )
 
 [Queries are indented to show outline]
 
 As you can see, the last clause references persiste1__1, which isn't listed in the from
clause. It's intended to, because the pattern matches with the previous example (_1 begin
the first innerjoin for persiste1_). It should be an alias for beroepsuitoefening just as it
is in the previous example.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-272) crashes in buildSessionFactory

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Tue, 26 Aug 2003 1:32 PM

I am closing this, since there is no more response from the user, and it is unlikely to be a Hibernate bug.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-272


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-272
    Summary: crashes in buildSessionFactory
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: CANNOT REPRODUCE

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.2

   Assignee: 
   Reporter: dirk ooms

    Created: Mon, 18 Aug 2003 3:55 PM
    Updated: Tue, 26 Aug 2003 1:32 PM
Environment: eclipse, mysql, cglib-1.0

Description:
Since I am an Hibernate-beginner, this could be something trivial (in which case I apologize). I wanted to port my simple example program (reading the entries from a single table) from hibernate1.2 to hibernate2(.0.2), but it does not work anymore (I did follow the Hibernate2 Porting Guidelines).

Program stops with this:

INFO: Mapping class: persistent.Animal -> Animals
Aug 18, 2003 9:53:49 PM net.sf.hibernate.cfg.Configuration secondPassCompile
INFO: processing one-to-many association mappings
Aug 18, 2003 9:53:49 PM net.sf.hibernate.cfg.Configuration secondPassCompile
INFO: processing foreign key constraints


Trace:

Thread [main] (Suspended (exception IllegalStateException))
  KeyFactoryGenerator(CodeGenerator).<init>(String, Class, ClassLoader) line: 127
  KeyFactoryGenerator.<init>(String, Class, ClassLoader) line: 93
  KeyFactory.create(Class, ClassLoader) line: 114
  SessionFactoryImpl.<clinit>() line: 297
  Configuration.buildSessionFactory() line: 627
  DbTest.main(String[]) line: 31


mapping file:

<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
  "-//Hibernate/Hibernate Mapping DTD//EN"
  "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd">

<hibernate-mapping>
  <class name="persistent.Animal" table="Animals">
    <id name="id" unsaved-value="null">
      <generator class="assigned"/>
    </id>
    <property name="patientNumber"/>
    <property name="name"/>
    <property name="sex"/>
    <property name="sterilized"/>
  </class>
</hibernate-mapping>


part of my test program:

public static void main(String[] args) {
	try {
		Configuration cfg = new Configuration();
		cfg.addClass(persistent.Animal.class);
		SessionFactory sf = cfg.buildSessionFactory();
                ...

Is this Hibernate related or is it something in cglib?







---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-186) Problem in SQL generation with ".class" queries + "iterate()"

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Tue, 26 Aug 2003 1:29 PM

We will track this via HB-281
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-186


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-186
    Summary: Problem in SQL generation with ".class" queries + "iterate()"
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: DUPLICATE

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: Fabio Tudone

    Created: Sat, 12 Jul 2003 2:50 AM
    Updated: Tue, 26 Aug 2003 1:29 PM
Environment: Windows 2000, WSAD 5 JVM (IBM 1.3)

Description:
I'm having a strange problem in Hibernate 2.0.1 when using the session.createQuery() + query.iterate() APIs. My mapping is the following: 
 
<?xml version="1.0" encoding="UTF-8"?> 
<!DOCTYPE hibernate-mapping PUBLIC "--//Hibernate/Hibernate Mapping DTD//EN" "hibernate-mapping-2.0.dtd"> 
 
 <hibernate-mapping auto-import="false" default-cascade="save-update"> 
 
 <class name="test.model.Super"> 
 <composite-id> 
 <key-property name="id"/> 
 </composite-id> 
 
 <property name="superAttr"/> 
 
 <joined-subclass name="test.model.Sub1"> 
 <key> 
 <column name="id"/> 
 </key> 
 
 <property name="sub1Attr"/> 
 </joined-subclass> 
 
 <joined-subclass name="test.model.Sub2"> 
 <key> 
 <column name="id"/> 
 </key> 
 
 <property name="sub2Attr"/> 
 </joined-subclass> 
 </class> 
</hibernate-mapping> 
 
 
The following code works perfectly: 
 
 
... 
Transaction t = s.beginTransaction(); 
 
 List l = s.find("from test.model.Super o where o.class = test.model.Sub1"); 
 
t.commit(); 
... 
 
 
On the other hand, the following code hangs: 
 
 
... 
Transaction t = s.beginTransaction(); 
 
 Query q = s.createQuery("from test.model.Super o where o.class = test.model.Sub1"); 
 Iterator it = q.iterate(); 
 
 while (it.hasNext()) { 
 Object o = it.next(); 
 } 
 
t.commit(); 
... 
 
 
The following SQL select query is generated by Hibernate upon the q.iterate() call: 
 
 
select super0_.id as x0_0_ from Super super0_ where (case when super0__1.id is not null then 1 when super0__2.id is not null then 2 when super0_.id is not null then 0 end=0 ) 
 
 
And the following exception is thrown by Oracle: 
 
 
[ERROR] JDBCExceptionReporter - -Could not execute query <java.sql.SQLException: ORA-00904: "SUPER0__2"."ID": invalid identifier 
>java.sql.SQLException: ORA-00904: "SUPER0__2"."ID": invalid identifier 
 
 at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134) 
 at oracle.jdbc.oci8.OCIDBAccess.check_error(OCIDBAccess.java:2321) 
 at oracle.jdbc.oci8.OCIDBAccess.parseExecuteDescribe(OCIDBAccess.java:1255) 
 at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:2391) 
 at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2672) 
 at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:589) 
 at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:527) 
 at net.sf.hibernate.impl.BatcherImpl.getResultSet(BatcherImpl.java:62) 
 at net.sf.hibernate.loader.Loader.getResultSet(Loader.java:539) 
 at net.sf.hibernate.hql.QueryTranslator.iterate(QueryTranslator.java:789) 
 at net.sf.hibernate.impl.SessionImpl.iterate(SessionImpl.java:1422) 
 at net.sf.hibernate.impl.QueryImpl.iterate(QueryImpl.java:64) 
 at test.query.TestQueryIter.main(TestQueryIter.java:58) 
 
java.sql.SQLException: ORA-00904: "SUPER0__2"."ID": invalid identifier 
 at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134) 
 at oracle.jdbc.oci8.OCIDBAccess.check_error(OCIDBAccess.java:2321) 
 at oracle.jdbc.oci8.OCIDBAccess.parseExecuteDescribe(OCIDBAccess.java:1255) 
 at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:2391) 
 at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2672) 
 at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:589) 
 at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:527) 
 at net.sf.hibernate.impl.BatcherImpl.getResultSet(BatcherImpl.java:62) 
 at net.sf.hibernate.loader.Loader.getResultSet(Loader.java:539) 
 at net.sf.hibernate.hql.QueryTranslator.iterate(QueryTranslator.java:789) 
 at net.sf.hibernate.impl.SessionImpl.iterate(SessionImpl.java:1422) 
 at net.sf.hibernate.impl.QueryImpl.iterate(QueryImpl.java:64) 
 at test.query.TestQueryIter.main(TestQueryIter.java:58) 
rethrown as net.sf.hibernate.JDBCException: Could not execute query: ORA-00904: "SUPER0__2"."ID": invalid identifier 
 at net.sf.hibernate.impl.SessionImpl.iterate(SessionImpl.java:1425) 
 at net.sf.hibernate.impl.QueryImpl.iterate(QueryImpl.java:64) 
 at test.query.TestQueryIter.main(TestQueryIter.java:58) 
 
 



---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-253) Filter with "elements(this.employees)" clause

[<leg...@at...>]

Message:

   The following issue has been closed.

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-253


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-253
    Summary: Filter with "elements(this.employees)" clause
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2
   Versions:
             2.1 beta 1

   Assignee: 
   Reporter: Alessandro Vernet

    Created: Tue, 12 Aug 2003 2:20 PM
    Updated: Tue, 26 Aug 2003 1:28 PM

Description:
I am doing a:

session.filter(regions, "where ? in elements(this.employees)", employee, Hibernate.entity(Employee.class));

Where Region.hbm.xml defines employees as:

<hibernate-mapping>
    <class name="bean.Region" table="owf_region" mutable="false">
        ...
        <set name="employees" table="owf_employee_region">
            <key column="region_id"/>
            <many-to-many class="bean.Employee" column="employee_id"/> 
        </set>
    </class>
</hibernate-mapping>

I get:

net.sf.hibernate.QueryException: could not resolve property: employees [where ? in elements(this.employees)]
	at net.sf.hibernate.persister.AbstractPropertyMapping.getPropertyType(AbstractPropertyMapping.java:33)
	at net.sf.hibernate.hql.PathExpressionParser.getPropertyType(PathExpressionParser.java:242)
	at net.sf.hibernate.hql.PathExpressionParser.token(PathExpressionParser.java:122)
	at net.sf.hibernate.hql.WhereParser.doPathExpression(WhereParser.java:333)
	at net.sf.hibernate.hql.WhereParser.doToken(WhereParser.java:365)
	at net.sf.hibernate.hql.WhereParser.token(WhereParser.java:250)
	at net.sf.hibernate.hql.ClauseParser.token(ClauseParser.java:87)
	at net.sf.hibernate.hql.PreprocessingParser.end(PreprocessingParser.java:142)
	at net.sf.hibernate.hql.ParserHelper.parse(ParserHelper.java:30)
	at net.sf.hibernate.hql.QueryTranslator.compile(QueryTranslator.java:148)
	at net.sf.hibernate.hql.QueryTranslator.compile(QueryTranslator.java:135)
	at net.sf.hibernate.hql.FilterTranslator.compile(FilterTranslator.java:25)
	at net.sf.hibernate.impl.SessionFactoryImpl.getFilter(SessionFactoryImpl.java:269)
	at net.sf.hibernate.impl.SessionImpl.getFilterTranslator(SessionImpl.java:3149)
	at net.sf.hibernate.impl.SessionImpl.filter(SessionImpl.java:3169)
	at net.sf.hibernate.impl.SessionImpl.filter(SessionImpl.java:3109)

I expected this to work. Pretty much the same HQL works just fine when used in a session.createQuery(), e.g.:

session.createQuery("from Region as r where ? in elements(r.employees)").setEntity(0, employee).list()

Alex


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Assigned: (HB-284) Add <meta attribute="extends"> to <composite-id> for hbm2java

[<leg...@at...>]

Message:

   The following issue has been re-assigned.

   Assignee: Max Rydahl Andersen (mailto:xa...@xa...)
   Assigner: Gavin King (mailto:ga...@in...)
       Date: Tue, 26 Aug 2003 1:26 PM
    Comment:
another one for you, Max
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-284


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-284
    Summary: Add <meta attribute="extends"> to <composite-id> for hbm2java
       Type: Improvement

     Status: Assigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             toolset
   Versions:
             2.0.2

   Assignee: Max Rydahl Andersen
   Reporter: Eric Fenderbosch

    Created: Fri, 22 Aug 2003 1:23 PM
    Updated: Tue, 26 Aug 2003 1:26 PM
Environment: N/A

Description:
  <class
      name="com.fedex.cc.objectlib.tariff.TariffAccessorialState"
      table="TARIFF_ACCESSORIAL">
    <meta attribute="extends">PersistentState</meta>
    <composite-id name="id" class="com.fedex.cc.objectlib.tariff.TariffAccessorialIdentity">
      <key-property name="seqId" column="SEQ_ID" type="long"/>
      <key-property name="tariffId" column="TARIFF_ID" type="long"/>
      <meta attribute="extends">PersistentIdentity</meta>
    </composite-id>
<!-- ... --->
  </class>

This would generate 2 classes:
public class TariffAccessorialState extends PersistentState { ... }
public class TariffAccessorialIdentity extends PersistentIdentity { ... }
Note that TariffAccessorialIdentity extends PersistentIdentity not PersistentState.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-289) using alias with id that isn't primary key causes where clauses to swap out to primary key name

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Tue, 26 Aug 2003 1:25 PM

As per Hibernate documentation this is correct and expected.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-289


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-289
    Summary: using alias with id that isn't primary key causes where clauses to swap out to primary key name
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 1

   Assignee: 
   Reporter: Mark Proctor

    Created: Mon, 25 Aug 2003 6:55 PM
    Updated: Tue, 26 Aug 2003 1:25 PM
Environment: Windows XP, Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)

Description:
if I have  the following mapping file(note how I use "id" as name for a normal column, and guid as the primary key):
<hibernate-mapping>
    <class name="Revision" table="Revision">
    <id name="guid" type="java.lang.String" column="guid">
      <generator class="uuid.hex"/>
    </id>
    <property name="id" column="id" type="java.lang.String"/>
    <property name="version" column="version" type="long"/>
    <property name="fromDate" column="fromDate" type="java.util.Date"/>
    <property name="toDate" column="toDate" type="java.util.Date"/>
  </class>
</hibernate-mapping>

and I try the following query:
from com.domain.package.Revision as rev where rev.id=? and rev.toDate is null
I get id swapped out to guid, as shown in the SQL below:
select revision0_.guid as guid, revision0_.id as id, revision0_.version as version, revision0_.fromDate as fromDate, revision0_.toDate as toDate from Revision revision0_ where revision0_.guid=? )and(revision0_.toDate is null )

It works correctly  when aliases are not used, note how I have to use the table name directly on the where clauses, as you cant use the object name:
from com.domain.package.Revision where Revision.id=? and Revision.toDate is null

this gives the sql:
select revision0_.guid as guid, revision0_.id as id, revision0_.version as version, revision0_.fromDate as fromDate, revision0_.toDate as toDate from Revision revision0_ where (Revision.id=? )and(Revision.toDate is null )



---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-290) Allow component in IS NULL HQL

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Gavin King
    Created: Tue, 26 Aug 2003 1:24 PM
       Body:
Actually, you CAN always name each property of a component or composite id (even in the case of an association).

OTOH, this is a desirable feature, certainly.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-290


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-290
    Summary: Allow component in IS NULL HQL
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: Emmanuel Ligne

    Created: Tue, 26 Aug 2003 1:27 AM
    Updated: Tue, 26 Aug 2003 1:27 AM

Description:
Allow paths to components (or classes) in IS (not) NULL statement and
not only terminal properties. As long as component types are concerned,
testing "is null" corresponds to testing each column of the component
(or each column of the key for a class), based on the values returned
by the nullSafeSet(null) on the component or key type.

This would allow usage of multi-column ids, as for now these cannot
be used in HQL (cannot name each column as in composite-id).



---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-291) support for select for update request for oracle on queries

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Gavin King
    Created: Tue, 26 Aug 2003 1:22 PM
       Body:
ie. via Query.setLockMode()
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-291


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-291
    Summary: support for select for update request for oracle on queries
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: luc

    Created: Tue, 26 Aug 2003 2:38 AM
    Updated: Tue, 26 Aug 2003 2:38 AM

Description:
See the following post:





http://sourceforge.net/forum/forum.php?thread_id=922434&forum_id=128638


Thanks a lot


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-293) Seperating InterBase and Firebird dialects

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Gavin King
    Created: Tue, 26 Aug 2003 1:22 PM
       Body:
OK, so what I suggest is that we add a FirebirdDialect that (for now) extends InterbaseDialect. Would you please tell me exactly what differences there are; ie. what changes need to be made.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-293


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-293
    Summary: Seperating InterBase and Firebird dialects
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: Reha CENANI

    Created: Tue, 26 Aug 2003 6:46 AM
    Updated: Tue, 26 Aug 2003 6:46 AM

Description:
At the begining, opensource Firebird (or FirebirdSQL) was based on the same source code of commercial InterBase. But during past three years, lots of improvements are done to the Firebird. Recent versions of these DBMSs have different features and statement syntaxes. 

For example, their select offset/limit statement syntaxes are not compatible. Hibernate's recent InterbaseDialect select limit/offset feature is based on the Firebird's select statement syntax.

So, in order to prevent incompabilities and confussion, in addition to the InterbaseDialect, adding a new FirebirdDialect and seperating Firebird and InterBase features will be very helpfull.





---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-292) InterbaseDialect and limit parameters

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Tue, 26 Aug 2003 1:21 PM

Lets track this via HB-293
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-292


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-292
    Summary: InterbaseDialect and limit parameters
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: DUPLICATE

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: Reha CENANI

    Created: Tue, 26 Aug 2003 6:13 AM
    Updated: Tue, 26 Aug 2003 1:21 PM

Description:
InterbaseDialect sets limit and offset values in wrong order. Appending following lines to the InterbaseDialect.java will solve the issue.

    public boolean bindLimitParametersInReverseOrder() {
        return true;
    }





---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-284) Add <meta attribute="extends"> to <composite-id> for hbm2java

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Eric Fenderbosch
    Created: Tue, 26 Aug 2003 12:37 PM
       Body:
Turns out this is really easy.
I edited the DTD and pointed to a local copy and got it to work w/o any code changes.

Simple change
<!ELEMENT composite-id ( (key-property|key-many-to-one)+ )>
to
<!ELEMENT composite-id (meta*, (key-property|key-many-to-one)+ )>
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-284


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-284
    Summary: Add <meta attribute="extends"> to <composite-id> for hbm2java
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             toolset
   Versions:
             2.0.2

   Assignee: 
   Reporter: Eric Fenderbosch

    Created: Fri, 22 Aug 2003 1:23 PM
    Updated: Fri, 22 Aug 2003 1:23 PM
Environment: N/A

Description:
  <class
      name="com.fedex.cc.objectlib.tariff.TariffAccessorialState"
      table="TARIFF_ACCESSORIAL">
    <meta attribute="extends">PersistentState</meta>
    <composite-id name="id" class="com.fedex.cc.objectlib.tariff.TariffAccessorialIdentity">
      <key-property name="seqId" column="SEQ_ID" type="long"/>
      <key-property name="tariffId" column="TARIFF_ID" type="long"/>
      <meta attribute="extends">PersistentIdentity</meta>
    </composite-id>
<!-- ... --->
  </class>

This would generate 2 classes:
public class TariffAccessorialState extends PersistentState { ... }
public class TariffAccessorialIdentity extends PersistentIdentity { ... }
Note that TariffAccessorialIdentity extends PersistentIdentity not PersistentState.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-287) documentation error - all-delete-orphan/s

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Christian Bauer
       Date: Mon, 25 Aug 2003 3:12 AM

Fixed. You also should have edit permissions now.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-287


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-287
    Summary: documentation error - all-delete-orphan/s
       Type: Improvement

     Status: Closed
   Priority: Minor
 Resolution: FIXED

    Project: Hibernate2
   Versions:
             2.0.2

   Assignee: Christian Bauer
   Reporter: Will Glass-Husain

    Created: Sun, 24 Aug 2003 2:20 AM
    Updated: Mon, 25 Aug 2003 3:12 AM

Description:
I think the below text should read "all-delete-orphan".  At least, that's what worked in Hibernate 2.0.2.  Using "all-delete-orphans" gave me an error (invalid cascade type).  Nice new feature, BTW.

Quoting: 
http://hibernate.bluemars.net/116.html

I removed an object from a collection mapped with cascade="all" but the object was not deleted!
cascade="all" cascades the delete() operation from parent to child. If this is a one-to-many association, try using cascade="all-delete-orphans".





---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

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

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Simone Ricciardi
    Created: Tue, 26 Aug 2003 9:28 AM
       Body:
Unfortunately I've also gotten the same error, when the Query.iterate() is used instead of Query.list(). In this case (and this is more serious) the error also happens when the entity is being returned in the select clause (not only with select count(*)).
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-281


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-281
    Summary: ".class" with <joined-subclass> problem
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: Simone Ricciardi

    Created: Fri, 22 Aug 2003 2:38 AM
    Updated: Fri, 22 Aug 2003 2:38 AM
Environment: windows 2000

Description:
I've acknowledged an error that happens using "select count (*) ..." 
together to a where clause "... where alias.class = ClassName ". 

Suppose to have two classes: 

public class Foo
{
String id;
String attr1;

public String getId(){ return id; }
public void setId(String id){ this.id = id; }
public String getAttr1(){ return attr1; }
public void setAttr1(String attr1){ this.attr1 = attr1; }
}

public class Bar extends Foo
{
String attr2;

public String getAttr2(){ return attr2; }
public void setAttr2(String attr2){ this.attr2 = attr2; }
}

and the corresponding mapping file: 

<hibernate-mapping>
<class name="test.persistents.Foo" table="Foo">
<id name="id" type="string">
<column name="id" length="32"/>
<generator class="uuid.hex"/>
</id>
<property name="attr1" column="attr1" type="string"/>

<joined-subclass name="test.persistents.Bar" table="Bar">
<key column="foo_id"/>
<property name="attr2" column="attr2" type="string"/>
</joined-subclass>
</class>
</hibernate-mapping>

When I try to make the following query: 

Query query = session.createQuery("select count(*) from Foo foo where foo.class = Foo"); 

I get an error of this type:

java.sql.SQLException: General error, message from server: "Unknown table 'foo0__1' in where clause"
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1651)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:889)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:956)
at com.mysql.jdbc.Connection.execSQL(Connection.java:1874)
at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1538)
at com.p6spy.engine.logging.P6LogPreparedStatement.executeQuery(P6LogPreparedStatement.java:171)
at net.sf.hibernate.impl.BatcherImpl.getResultSet(BatcherImpl.java:71)
at net.sf.hibernate.loader.Loader.getResultSet(Loader.java:551)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:140)
at net.sf.hibernate.loader.Loader.find(Loader.java:620)
at net.sf.hibernate.hql.QueryTranslator.find(QueryTranslator.java:928)
at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1343)
at net.sf.hibernate.impl.QueryImpl.list(QueryImpl.java:76)
at test.Test.main(Test.java:42)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)

while if I perform the same query without the select count(*) (select foo from Foo foo where foo.class = Foo) 
all works fine.
Comparing the two queries produced by hibernate in both cases, 
it seems that the error derives from the lack of the "left outer join" with the Bar table in the "from" clause:

with select count(*):
select count(*) as x0_0_ 
from Foo foo0_ 
where (case when foo0__1.foo_id is not null then 1 when foo0_.id is not null then 0 end=0 )

without select count(*):
select foo0_.id as id, 
case when foo0__1.foo_id is not null then 1 
when foo0_.id is not null then 0 end 
as clazz_, 
foo0_.attr1 as attr10_, 
foo0__1.attr2 as attr21_ 
from Foo foo0_ left outer join Bar foo0__1 on foo0_.id=foo0__1.foo_id 
where (case when foo0__1.foo_id is not null then 1 when foo0_.id is not null then 0 end=0 )

in fact the query should be the following:
select count(*) as x0_0_ 
from Foo foo0_ left outer join Bar foo0__1 on foo0_.id=foo0__1.foo_id 
where (case when foo0__1.foo_id is not null then 1 when foo0_.id is not null then 0 end=0 )


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HB-293) Seperating InterBase and Firebird dialects

[<leg...@at...>]

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-293


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-293
    Summary: Seperating InterBase and Firebird dialects
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: Reha CENANI

    Created: Tue, 26 Aug 2003 6:46 AM
    Updated: Tue, 26 Aug 2003 6:46 AM

Description:
At the begining, opensource Firebird (or FirebirdSQL) was based on the same source code of commercial InterBase. But during past three years, lots of improvements are done to the Firebird. Recent versions of these DBMSs have different features and statement syntaxes. 

For example, their select offset/limit statement syntaxes are not compatible. Hibernate's recent InterbaseDialect select limit/offset feature is based on the Firebird's select statement syntax.

So, in order to prevent incompabilities and confussion, in addition to the InterbaseDialect, adding a new FirebirdDialect and seperating Firebird and InterBase features will be very helpfull.





---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HB-292) InterbaseDialect and limit parameters

[<leg...@at...>]

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-292


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-292
    Summary: InterbaseDialect and limit parameters
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: Reha CENANI

    Created: Tue, 26 Aug 2003 6:13 AM
    Updated: Tue, 26 Aug 2003 6:13 AM

Description:
InterbaseDialect sets limit and offset values in wrong order. Appending following lines to the InterbaseDialect.java will solve the issue.

    public boolean bindLimitParametersInReverseOrder() {
        return true;
    }





---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-277) hbm2java generates wrong import with BinaryBlobType

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Max Rydahl Andersen
       Date: Mon, 25 Aug 2003 12:17 PM

got it ;)
Is now fixed in cvs
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-277


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-277
    Summary: hbm2java generates wrong import with BinaryBlobType 
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Hibernate2
 Components: 
             toolset
   Fix Fors:
             2.1

   Assignee: Max Rydahl Andersen
   Reporter: Thomas Jenny

    Created: Thu, 21 Aug 2003 4:31 AM
    Updated: Mon, 25 Aug 2003 12:17 PM
Environment: Hibernate 2.0.2, Hibernate extensions 2.0

Description:
in the mapping file, the following property is defined:

<property
    name="cryptedPassword"
    type="package.BinaryBlobType"
    column="CRYPTED_PASSWORD"
    length="4000"
    />

I'm using the class BinaryBlobType almost as defined at
http://hibernate.bluemars.net/73.html (imports adjusted to 
Hibernate 2)

hbm2java generates the following import:

import byte[];
...

When I remove the import, the code compiles and runs fine; 
but our automatic build cycle is currently broken because of 
this ...



---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira