hibernate-issues — Hibernate JIRA Notifications

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-380) Use ResultSet.getGeneratedKeys() when supported by JDBC driver

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

The following comment has been added to this issue:

     Author: John Kristian
    Created: Wed, 5 Nov 2003 7:04 PM
       Body:
Re: Can you add your records in a pre-insert trigger?

Microsoft SQL Server does not support pre-insert triggers. :-(
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-380
    Summary: Use ResultSet.getGeneratedKeys() when supported by JDBC driver
       Type: Improvement

     Status: Assigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1

   Assignee: Gavin King
   Reporter: David Morris

    Created: Sat, 4 Oct 2003 1:02 AM
    Updated: Wed, 5 Nov 2003 1:36 PM
Environment: JDBC 3.0 Drivers with 1.4 JDKs. MySql and DB2 both have JDBC drivers that support get generated keys.

Description:
Retrieve ResultSet of natively generated keys after inserting records into databases that provide this support. Performance is genrally better with this technique. The code change should be backward compatable with 1.3 JREs and older JDBC drivers.


---------------------------------------------------------------------
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-139) Relax rowcount to be > instead of equal to account for triggers.

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

The following comment has been added to this issue:

     Author: John Kristian
    Created: Wed, 5 Nov 2003 6:51 PM
       Body:
See also http://forum.hibernate.org/old//890970.html
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-139
    Summary: Relax rowcount to be > instead of equal to account for triggers.
       Type: Improvement

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: Gavin King
   Reporter: Don Eddleman

    Created: Tue, 17 Jun 2003 10:15 AM
    Updated: Tue, 4 Nov 2003 5:48 PM
Environment: All OSs, SQLServer and more than likely any other DB that supports triggers.

Description:
Within the NonBatchingBatcher class the check for row count to determine success should be relaxed to rowCount >= expected so that any triggers defined on tables affected by the insert/update will not cause a txn to fail just because they fired.


---------------------------------------------------------------------
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-139) Relax rowcount to be > instead of equal to account for triggers.

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

The following comment has been added to this issue:

     Author: John Kristian
    Created: Wed, 5 Nov 2003 6:41 PM
       Body:
With NetDirect's JSQLConnect driver, one can avoid this problem by setting the driver property lastUpdateCount=true (which prevents triggers from affecting the returned row count).  For doco see http://www.j-netdirect.com/JSQLConnect/TechnicalReference.html#ConnectSettings
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-139
    Summary: Relax rowcount to be > instead of equal to account for triggers.
       Type: Improvement

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: Gavin King
   Reporter: Don Eddleman

    Created: Tue, 17 Jun 2003 10:15 AM
    Updated: Tue, 4 Nov 2003 5:48 PM
Environment: All OSs, SQLServer and more than likely any other DB that supports triggers.

Description:
Within the NonBatchingBatcher class the check for row count to determine success should be relaxed to rowCount >= expected so that any triggers defined on tables affected by the insert/update will not cause a txn to fail just because they fired.


---------------------------------------------------------------------
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-454) Session.createSQLQuery(sql)

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

The following comment has been added to this issue:

     Author: Gavin King
    Created: Wed, 5 Nov 2003 6:33 PM
       Body:
Something that hadn't occured to me before was that we could get column types from the ResultSetMetadata. I think this would be quite portable. Perhaps we should even use this instead of the dialect-specific-SQL-functions approach.

I can't believe I never considered this before....
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-454
    Summary: Session.createSQLQuery(sql)
       Type: New Feature

     Status: Unassigned
   Priority: Trivial

    Project: Hibernate2
   Versions:
             2.1 beta 5

   Assignee: 
   Reporter: Alexey Kaigorodov

    Created: Tue, 4 Nov 2003 9:15 PM
    Updated: Tue, 4 Nov 2003 9:15 PM

Description:
Session.createSQLQuery(sql) without returning some entity.
I.e. add the possibility to execute any SELECT through Hibernate API without use JDBC API.
Will useful be for uniform access to data.

--
With best regards,
Alex Kaigorodov


---------------------------------------------------------------------
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] Updated: (HB-380) Use ResultSet.getGeneratedKeys() when supported by JDBC driver

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

The following issue has been updated:

    Updater: John Kristian (mailto:jkr...@do...)
       Date: Wed, 5 Nov 2003 1:36 PM
    Comment:
genKeyMS.zip (attached) combines getgeneratedkeys3.patch with HB-437.  This combination would be better than getgeneratedkeys3.patch, from my point of view.

In genKeyMS.patch, I renamed the configuration property to hibernate.jdbc.use_getGeneratedKeys, clarified the `diff` and removed what appeared to be an extraneous change.
    Changes:
             Attachment changed to genKeyMS.zip
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-380&page=history

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-380
    Summary: Use ResultSet.getGeneratedKeys() when supported by JDBC driver
       Type: Improvement

     Status: Assigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1

   Assignee: Gavin King
   Reporter: David Morris

    Created: Sat, 4 Oct 2003 1:02 AM
    Updated: Wed, 5 Nov 2003 1:36 PM
Environment: JDBC 3.0 Drivers with 1.4 JDKs. MySql and DB2 both have JDBC drivers that support get generated keys.

Description:
Retrieve ResultSet of natively generated keys after inserting records into databases that provide this support. Performance is genrally better with this technique. The code change should be backward compatable with 1.3 JREs and older JDBC drivers.


---------------------------------------------------------------------
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-453) ClassCastException in ReadWriteCache.afterUpdate

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

The following comment has been added to this issue:

     Author: John Kristian
    Created: Wed, 5 Nov 2003 11:05 AM
       Body:
It's not cache configuration, in my case.  The test case that exposed this bug evicts cache entries (by calling the SessionFactory.evict methods).  Why?  It makes database changes that cause triggers (in the database) to change other tables that are cached by Hibernate, and it needs to see the results (not stale cache entries).

I have an extensive test suite, but I can't publish it (it's the intellectual property of my employer).  Anyway, it's too large and platform-dependent for the Hibernate team's use.  I'll think about developing something more suitable, but it seems like a project that would exceed my time budget for Hibernate improvements.  Sorry.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-453
    Summary: ClassCastException in ReadWriteCache.afterUpdate
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.1 rc1
   Versions:
             2.1 rc1

   Assignee: 
   Reporter: John Kristian

    Created: Tue, 4 Nov 2003 4:37 PM
    Updated: Tue, 4 Nov 2003 5:57 PM
Environment: Windows XP, WebLogic 8.1 SP1, Microsoft SQL Server

Description:
Hibernate 2.1 beta 6 propagates an AssertionFailure and logs error.log (attached).  This did not occur with 2.1 beta 5.

notlock.patch (attached) solves this problem for me.


---------------------------------------------------------------------
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-380) Use ResultSet.getGeneratedKeys() when supported by JDBC driver

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

The following comment has been added to this issue:

     Author: David Morris
    Created: Wed, 5 Nov 2003 10:57 AM
       Body:
I meant to say pre-insert trigger.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-380
    Summary: Use ResultSet.getGeneratedKeys() when supported by JDBC driver
       Type: Improvement

     Status: Assigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1

   Assignee: Gavin King
   Reporter: David Morris

    Created: Sat, 4 Oct 2003 1:02 AM
    Updated: Tue, 4 Nov 2003 12:06 AM
Environment: JDBC 3.0 Drivers with 1.4 JDKs. MySql and DB2 both have JDBC drivers that support get generated keys.

Description:
Retrieve ResultSet of natively generated keys after inserting records into databases that provide this support. Performance is genrally better with this technique. The code change should be backward compatable with 1.3 JREs and older JDBC drivers.


---------------------------------------------------------------------
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-443) JRE incompatibility, gives no persister for : java.lang.Boolean

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

The following comment has been added to this issue:

     Author: Sunil Reddy
    Created: Wed, 5 Nov 2003 10:36 AM
       Body:
Hi Gavin,
Thanks for the information, the getFormula/setFormula method was overloaded for Sun's JRE with a isFormula()/isAggregation() method which caused the problem. By renaming the isXXX() methods, i got rid of the problem,
Thanks,

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-443
    Summary: JRE incompatibility, gives no persister for : java.lang.Boolean
       Type: Bug

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

    Project: Hibernate2
   Versions:
             2.0.3

   Assignee: 
   Reporter: Sunil Reddy

    Created: Fri, 31 Oct 2003 1:26 PM
    Updated: Fri, 31 Oct 2003 6:31 PM
Environment: Windows 2000, going against DB2 7.0, Hibernate 2.0.3, Websphere 5.0, Sun JDK 1.3.1_01.

Description:
Topic: JRE incompatibility, gives no persister for : java.lang.Long

Hi Gavin,
Thanks for your reply, i think Hibernate is excellent, i am struggling with this problem whole week, i have tried everything from recompile hibernate to traversing trees but the bug exists whenever i switch from Ibm jre to Sun jre. I don't know where i am making a mistake, here is a recreation of the problem :

Classes : 
"Derivation" is a choice of "Aggregation" or "Formula", which are lists of "Item". "Aggregation" has method attribute of type min or max. "Item" can be a "Constant" or "Operator". DTD is as follows : 

<!ELEMENT Derivation (Formula | Aggregation)>
<!ATTLIST Derivation
	Type (aggregation | formula) #REQUIRED
>
<!ELEMENT Aggregation (Item+)>
<!ATTLIST Aggregation
	Method (max | min) #REQUIRED
>
<!ELEMENT Formula (Item+)>
<!ELEMENT Item EMPTY>
<!ATTLIST Item
	Type (constant | operator | reference) #REQUIRED
	Value CDATA #REQUIRED
>

Derivation.java :
public String getType ()			//can be aggregation or formula
public void setType (String enumValue) 
public Formula getFormula ()
public void setFormula (Formula obj)
public void setFormula (XmlElement xml)
public Aggregation getAggregation () 
public void setAggregation (Aggregation obj) 
public void setAggregation (XmlElement xml)

Aggregation.java :
public String getMethod () 			//can be max or min
public void setMethod (String enumValue) 
public java.util.List getItem () 
public void setItem (java.util.List newList) 

Formula.java
public java.util.List getItem () 
public void setItem (java.util.List newList) 

Item.java
public String getType ()			//can be constant or operator
public void setType (String enumValue) 

//building session factory
	Properties prop = new Properties();
	prop.load( new FileInputStream("hibernate.properties") );
	Configuration cfg = new Configuration();
	cfg.addClass(example.Aggregation.class);
	cfg.addClass(example.Derivation.class);
	cfg.addClass(example.Formula.class);
	cfg.addClass(example.Item.class);
	cfg.setProperties(prop);
	sessionFactory = cfg.buildSessionFactory();
//main
	SampleApp sa = new SampleApp();
	sa.session = sessionFactory.openSession();
	Derivation d = (Derivation) obj;	//created this object with sample data shown below
	sa.session.save(d);		
	sa.session.flush();
	sa.session.connection().commit();
	sa.session.close();
//sample data 
<Derivation Type="aggregation">
	<Aggregation Method="max">
		<Item Type="constant" Value="5"/>
		<Item Type="constant" Value="24"/>
		<Item Type="constant" Value="18"/>
	</Aggregation>
</Derivation>

//exception i get with Sun 1.3.1_01 or 1.3.1_09 or 1.4.2 versions but not with Ibm jre is
13:59:37,846 DEBUG SessionImpl:413 - opened session
13:59:37,846 DEBUG SessionImpl:656 - saving [example.Derivation#<null>]
13:59:37,846 DEBUG Cascades:336 - processing cascades for: example.Derivation
13:59:37,846 DEBUG Cascades:87 - cascading to saveOrUpdate()
net.sf.hibernate.MappingException: No persister for: java.lang.Boolean
	at net.sf.hibernate.impl.SessionFactoryImpl.getPersister(SessionFactoryImpl.java:420)
	at net.sf.hibernate.impl.SessionImpl.getPersister(SessionImpl.java:2302)
	at net.sf.hibernate.impl.SessionImpl.getPersister(SessionImpl.java:2309)
	at net.sf.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:1195)
	at net.sf.hibernate.engine.Cascades$4.cascade(Cascades.java:88)
	at net.sf.hibernate.engine.Cascades.cascade(Cascades.java:258)
	at net.sf.hibernate.engine.Cascades.cascade(Cascades.java:341)
	at net.sf.hibernate.impl.SessionImpl.doSave(SessionImpl.java:693)
	at net.sf.hibernate.impl.SessionImpl.save(SessionImpl.java:605)
	at example.SampleApp.main(SampleApp.java:89)


//Mappings for the above classes are :
<hibernate-mapping>
    <class name="example.Derivation" table="ex_derivation">
        <id name="id" type="long" column="id" unsaved-value="0">
             <generator class="native"/>
        </id>
        <property name="type"/>
        <many-to-one name="formula" class="example.Formula" column="formula_id" cascade="all"/>
        <many-to-one name="aggregation" class="example.Aggregation" column="aggregation_id" cascade="all"/>
    </class>
    <class name="example.Formula" table="ex_formula">
		<id name="id" type="long" column="id" unsaved-value="0">
			<generator class="native"/>
		</id>
		<list name="item" table="ex_item" cascade="all">
			<key column="formula_id"/>
			<index column="formula_index"/>
			<one-to-many class="example.Item"/>
		</list>
    </class>
    <class name="example.Aggregation" table="ex_aggregation">
		<id name="id" type="long" column="id" unsaved-value="0">
			<generator class="native"/>
		</id>
		<property name="method"/>
		<list name="item" table="ex_item" cascade="all">
			<key column="aggregation_id"/>
			<index column="aggregation_index"/>
			<one-to-many class="example.Item"/>
		</list>
    </class>
    <class name="example.Item" table="ex_item">
        <id name="id" type="long" column="id" unsaved-value="0">
             <generator class="native"/>
        </id>
        <property name="type"/>
        <property name="value"/>
    </class>
</hibernate-mapping>



---------------------------------------------------------------------
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-458) Order on joined table columns in Criteria API

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Wed, 5 Nov 2003 6:33 AM

This is a dupe of HB-132
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-458
    Summary: Order on joined table columns in Criteria API
       Type: Improvement

     Status: Closed
   Priority: Major
 Resolution: DUPLICATE

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 5

   Assignee: 
   Reporter: Wouter van der Kamp

    Created: Wed, 5 Nov 2003 6:27 AM
    Updated: Wed, 5 Nov 2003 6:33 AM

Description:
I think it would be really usefull if the Criteria API also supported ordering on joined column tables, for instance:

List cats = sess.createCriteria(Cat.class)
    .createAlias("mate", "mate")
    .addOrder( Order.asc("mate.age") )
    .list();

I hope this could be developed soon!




---------------------------------------------------------------------
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-458) Order on joined table columns in Criteria API

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-458
    Summary: Order on joined table columns in Criteria API
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 5

   Assignee: 
   Reporter: Wouter van der Kamp

    Created: Wed, 5 Nov 2003 6:27 AM
    Updated: Wed, 5 Nov 2003 6:27 AM

Description:
I think it would be really usefull if the Criteria API also supported ordering on joined column tables, for instance:

List cats = sess.createCriteria(Cat.class)
    .createAlias("mate", "mate")
    .addOrder( Order.asc("mate.age") )
    .list();

I hope this could be developed soon!




---------------------------------------------------------------------
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-457) Documentation - Table 17.3 has an incorrect property name in it

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Wed, 5 Nov 2003 6:08 AM

I already fixed this in cvs
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-457
    Summary: Documentation - Table 17.3 has an incorrect property name in it
       Type: Bug

     Status: Closed
   Priority: Minor
 Resolution: DUPLICATE

    Project: Hibernate2
 Components: 
             toolset
   Versions:
             2.0.3

   Assignee: 
   Reporter: Joshua Davis

    Created: Wed, 5 Nov 2003 6:04 AM
    Updated: Wed, 5 Nov 2003 6:08 AM
Environment: Windows XP Pro, JDK 1.4.1_02, ANT 1.5.2

Description:
Found this while trying to get the ANT schema export task to work:

Table 17.3 in the documentation referrs to a property 'hibernate.connection.driver', which is incorrect.  The SchemaExport tool expects the property name to be 'hibernate.connection.driver_class'.   If 'hibernate.connection.driver_class' is not specified, the tool will fail.


---------------------------------------------------------------------
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-457) Documentation - Table 17.3 has an incorrect property name in it

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-457
    Summary: Documentation - Table 17.3 has an incorrect property name in it
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             toolset
   Versions:
             2.0.3

   Assignee: 
   Reporter: Joshua Davis

    Created: Wed, 5 Nov 2003 6:04 AM
    Updated: Wed, 5 Nov 2003 6:04 AM
Environment: Windows XP Pro, JDK 1.4.1_02, ANT 1.5.2

Description:
Found this while trying to get the ANT schema export task to work:

Table 17.3 in the documentation referrs to a property 'hibernate.connection.driver', which is incorrect.  The SchemaExport tool expects the property name to be 'hibernate.connection.driver_class'.   If 'hibernate.connection.driver_class' is not specified, the tool will fail.


---------------------------------------------------------------------
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-456) Select for update isn't supported for MS SQLServer

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

The following comment has been added to this issue:

     Author: Gavin King
    Created: Wed, 5 Nov 2003 4:00 AM
       Body:
please give an example of the syntax. I think we have discussed this before, but I forget what the correct syntax is now.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-456
    Summary: Select for update isn't supported for MS SQLServer
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Hibernate2

   Assignee: 
   Reporter: Dieter Bogdoll

    Created: Wed, 5 Nov 2003 3:51 AM
    Updated: Wed, 5 Nov 2003 3:51 AM
Environment: MS SQLServer 6.5, 7, 2000

Description:
MS SQLServer doesn't support the "FOR UPDATE" keyword within the SELECT statement.

But it is possible to create the same effect with table hints. 

Hibernate just add "FOR UPDATE" behind the select to lock objects. 
This has to be changed for the MS SQLServer. 
After each table name the correct table hints has to be written.


---------------------------------------------------------------------
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-456) Select for update isn't supported for MS SQLServer

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-456
    Summary: Select for update isn't supported for MS SQLServer
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Hibernate2

   Assignee: 
   Reporter: Dieter Bogdoll

    Created: Wed, 5 Nov 2003 3:51 AM
    Updated: Wed, 5 Nov 2003 3:51 AM
Environment: MS SQLServer 6.5, 7, 2000

Description:
MS SQLServer doesn't support the "FOR UPDATE" keyword within the SELECT statement.

But it is possible to create the same effect with table hints. 

Hibernate just add "FOR UPDATE" behind the select to lock objects. 
This has to be changed for the MS SQLServer. 
After each table name the correct table hints has to be written.


---------------------------------------------------------------------
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-455) Substitution of named parameters in SQL query

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

Message:

   The following issue has been re-assigned.

   Assignee: Max Rydahl Andersen (mailto:xa...@xa...)
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-455
    Summary: Substitution of named parameters in SQL query
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 5

   Assignee: Max Rydahl Andersen
   Reporter: Alexey Kaigorodov

    Created: Wed, 5 Nov 2003 2:46 AM
    Updated: Wed, 5 Nov 2003 2:55 AM

Description:
The substring between colon and the following space is considered the name of parameter. 
This incorrect in some cases e.g.

... (:bar=0 or foo=:bar) ...

For itself fix this in net.sf.hibernate.loader.SQLLoader
(attached)


--
With best regards,
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] Updated: (HB-455) Substitution of named parameters in SQL query

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

The following issue has been updated:

    Updater: Alexey Kaigorodov (mailto:a1...@ic...)
       Date: Wed, 5 Nov 2003 2:47 AM
    Changes:
             Attachment changed to SQLLoader.java
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-455&page=history

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-455
    Summary: Substitution of named parameters in SQL query
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 5

   Assignee: 
   Reporter: Alexey Kaigorodov

    Created: Wed, 5 Nov 2003 2:46 AM
    Updated: Wed, 5 Nov 2003 2:47 AM

Description:
The substring between colon and the following space is considered the name of parameter. 
This incorrect in some cases e.g.

... (:bar=0 or foo=:bar) ...

For itself fix this in net.sf.hibernate.loader.SQLLoader
(attached)


--
With best regards,
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] Created: (HB-455) Substitution of named parameters in SQL query

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-455
    Summary: Substitution of named parameters in SQL query
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 5

   Assignee: 
   Reporter: Alexey Kaigorodov

    Created: Wed, 5 Nov 2003 2:46 AM
    Updated: Wed, 5 Nov 2003 2:46 AM

Description:
The substring between colon and the following space is considered the name of parameter. 
This incorrect in some cases e.g.

... (:bar=0 or foo=:bar) ...

For itself fix this in net.sf.hibernate.loader.SQLLoader
(attached)


--
With best regards,
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] Commented: (HB-454) Session.createSQLQuery(sql)

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

The following comment has been added to this issue:

     Author: Max Rydahl Andersen
    Created: Wed, 5 Nov 2003 2:16 AM
       Body:
Remember that we just praised how getNamedQuery() now beautifull hides wether it is a sql or hql query that is about to be executed ?

I like that, but today if you have a scalar (or mixed) query then you won't be able to do that beautifull encapsulation ;)

So, it get's my vote - while my head is spinining on how the heck I should infer what the resulting rows types are....

HQL now it by parsing upfront - in sql I don't have that possibility...


Maybe I should just require that the user uses "select x as {person.name}, y as {person.age}, z as {cat.color} from ..."

Then a parse from "select" to "from" after tokens in brackets would "reveal" what the scalar types are....

What do you think ? 
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-454
    Summary: Session.createSQLQuery(sql)
       Type: New Feature

     Status: Unassigned
   Priority: Trivial

    Project: Hibernate2
   Versions:
             2.1 beta 5

   Assignee: 
   Reporter: Alexey Kaigorodov

    Created: Tue, 4 Nov 2003 9:15 PM
    Updated: Tue, 4 Nov 2003 9:15 PM

Description:
Session.createSQLQuery(sql) without returning some entity.
I.e. add the possibility to execute any SELECT through Hibernate API without use JDBC API.
Will useful be for uniform access to data.

--
With best regards,
Alex Kaigorodov


---------------------------------------------------------------------
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-380) Use ResultSet.getGeneratedKeys() when supported by JDBC driver

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

The following comment has been added to this issue:

     Author: John Kristian
    Created: Wed, 5 Nov 2003 1:54 AM
       Body:
It's a bug in the driver, I think; the driver appears to be using @@IDENTITY to implement getGeneratedKeys.  I filed a bug report with NetDirect; we'll see what they say.

I've unvoted for this patch, now that I understand it depends on a bleeding-edge feature of JDBC.

Um, what do you mean by "add your records in a pre-insert key?"  I don't understand.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-380
    Summary: Use ResultSet.getGeneratedKeys() when supported by JDBC driver
       Type: Improvement

     Status: Assigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1

   Assignee: Gavin King
   Reporter: David Morris

    Created: Sat, 4 Oct 2003 1:02 AM
    Updated: Tue, 4 Nov 2003 12:06 AM
Environment: JDBC 3.0 Drivers with 1.4 JDKs. MySql and DB2 both have JDBC drivers that support get generated keys.

Description:
Retrieve ResultSet of natively generated keys after inserting records into databases that provide this support. Performance is genrally better with this technique. The code change should be backward compatable with 1.3 JREs and older JDBC drivers.


---------------------------------------------------------------------
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-454) Session.createSQLQuery(sql)

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

The following comment has been added to this issue:

     Author: Gavin King
    Created: Wed, 5 Nov 2003 1:35 AM
       Body:
What is the value of this?? JDBC is a perfectly good API for executing SQL statements!
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-454
    Summary: Session.createSQLQuery(sql)
       Type: New Feature

     Status: Unassigned
   Priority: Trivial

    Project: Hibernate2
   Versions:
             2.1 beta 5

   Assignee: 
   Reporter: Alexey Kaigorodov

    Created: Tue, 4 Nov 2003 9:15 PM
    Updated: Tue, 4 Nov 2003 9:15 PM

Description:
Session.createSQLQuery(sql) without returning some entity.
I.e. add the possibility to execute any SELECT through Hibernate API without use JDBC API.
Will useful be for uniform access to data.

--
With best regards,
Alex Kaigorodov


---------------------------------------------------------------------
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-380) Use ResultSet.getGeneratedKeys() when supported by JDBC driver

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

The following comment has been added to this issue:

     Author: David Morris
    Created: Tue, 4 Nov 2003 9:36 PM
       Body:
It is a bug in the driver if you did not get back all generated keys. Here is the spec:

"Calling ResultSet.getMetaData on the ResultSet object returned by
getGeneratedKeys will produce a ResultSetMetaData object that can be used to determine the number, type and properties of the generated keys.
In some cases, such as in an insert select statement, more than one key may be returned. The ResultSet object returned by getGeneratedKeys will contain a row for each key that a statement generated. If no keys are generated, an empty result set will be returned.
The concurrency of the ResultSet object returned by getGeneratedKeys must be CONCUR_READ_ONLY. The type of the ResultSet object must be either TYPE_FORWARD_ONLY or TYPE_SCROLL_INSENSITIVE."

You should have received all keys generated with metadata describing the keys. I can see a problem with the spec because the metadata returned from a result set can't cover the results of more than one SQL statement and the specification says "the ResultSet object" infering that there is only one result set therefore one type.

That probably doesn't help much. As a workaround, can you add your records in a pre-insert key? it shouldn't be too bad except that you may need to delete a constraint (that could be moved to your trigger).
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-380
    Summary: Use ResultSet.getGeneratedKeys() when supported by JDBC driver
       Type: Improvement

     Status: Assigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1

   Assignee: Gavin King
   Reporter: David Morris

    Created: Sat, 4 Oct 2003 1:02 AM
    Updated: Tue, 4 Nov 2003 12:06 AM
Environment: JDBC 3.0 Drivers with 1.4 JDKs. MySql and DB2 both have JDBC drivers that support get generated keys.

Description:
Retrieve ResultSet of natively generated keys after inserting records into databases that provide this support. Performance is genrally better with this technique. The code change should be backward compatable with 1.3 JREs and older JDBC drivers.


---------------------------------------------------------------------
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-454) Session.createSQLQuery(sql)

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-454
    Summary: Session.createSQLQuery(sql)
       Type: New Feature

     Status: Unassigned
   Priority: Trivial

    Project: Hibernate2
   Versions:
             2.1 beta 5

   Assignee: 
   Reporter: Alexey Kaigorodov

    Created: Tue, 4 Nov 2003 9:15 PM
    Updated: Tue, 4 Nov 2003 9:15 PM

Description:
Session.createSQLQuery(sql) without returning some entity.
I.e. add the possibility to execute any SELECT through Hibernate API without use JDBC API.
Will useful be for uniform access to data.

--
With best regards,
Alex Kaigorodov


---------------------------------------------------------------------
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-380) Use ResultSet.getGeneratedKeys() when supported by JDBC driver

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

The following comment has been added to this issue:

     Author: John Kristian
    Created: Tue, 4 Nov 2003 7:26 PM
       Body:
getgeneratedkeys3.patch doesn't work with Microsoft SQL Server and NetDirect's JSQLConnect driver <http://www.j-netdirect.com/JSQLConnect/JSQLFeatures.html>, I find.  That is, Hibernate gets the identifier of a row inserted by a trigger, instead of the row whose insertion it requested.

Perhaps it's a bug in the driver, or perhaps I botched the patch.  I'm investigating.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-380
    Summary: Use ResultSet.getGeneratedKeys() when supported by JDBC driver
       Type: Improvement

     Status: Assigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1

   Assignee: Gavin King
   Reporter: David Morris

    Created: Sat, 4 Oct 2003 1:02 AM
    Updated: Tue, 4 Nov 2003 12:06 AM
Environment: JDBC 3.0 Drivers with 1.4 JDKs. MySql and DB2 both have JDBC drivers that support get generated keys.

Description:
Retrieve ResultSet of natively generated keys after inserting records into databases that provide this support. Performance is genrally better with this technique. The code change should be backward compatable with 1.3 JREs and older JDBC drivers.


---------------------------------------------------------------------
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-452) queries for <key-many-to-one>

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Tue, 4 Nov 2003 6:32 PM

This worked correctly for my using Hibernate 2.1. Its my bad, actually - I =
forgot to tell you that this functionality is new in 2.1.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?=
key=3DHB-452


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-452
    Summary: queries for <key-many-to-one>
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: DUPLICATE

    Project: Hibernate2
 Components:=20
             core
   Versions:
             2.0.3

   Assignee: Gavin King
   Reporter: Philippe Chal=C3=A9at

    Created: Tue, 4 Nov 2003 3:10 AM
    Updated: Tue, 4 Nov 2003 6:32 PM

Description:
Using composite key, there are some problem on query (see http://forum.hibe=
rnate.org/viewtopic.php?t=3D925205&highlight=3D)

The exception is :
could not resolve property type: piece.id.lot.id [from fr.infologic.stocks.=
modele.Mouv as mouv where mouv.piece.piecePK.lot.lotPK.prod =3D ? ]
=09at net.sf.hibernate.hql.PathExpressionParser.getPropertyType(PathExpress=
ionParser.java:235)

See attached zip file to reproduce the problem.

Philippe


---------------------------------------------------------------------
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] Updated: (HB-452) queries for <key-many-to-one>

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

The following issue has been updated:

    Updater: Gavin King (mailto:ga...@hi...)
       Date: Tue, 4 Nov 2003 6:25 PM
    Changes:
             summary changed from Composite key behaviour
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?=
key=3DHB-452&page=3Dhistory

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

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?=
key=3DHB-452


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-452
    Summary: queries for <key-many-to-one>
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components:=20
             core
   Versions:
             2.0.3

   Assignee: Gavin King
   Reporter: Philippe Chal=C3=A9at

    Created: Tue, 4 Nov 2003 3:10 AM
    Updated: Tue, 4 Nov 2003 6:25 PM

Description:
Using composite key, there are some problem on query (see http://forum.hibe=
rnate.org/viewtopic.php?t=3D925205&highlight=3D)

The exception is :
could not resolve property type: piece.id.lot.id [from fr.infologic.stocks.=
modele.Mouv as mouv where mouv.piece.piecePK.lot.lotPK.prod =3D ? ]
=09at net.sf.hibernate.hql.PathExpressionParser.getPropertyType(PathExpress=
ionParser.java:235)

See attached zip file to reproduce the problem.

Philippe


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