hibernate-issues — Hibernate JIRA Notifications

[Hibernate-issues] [Hibernate-JIRA] Updated: (HB-470) SQL Exception using a Map within a component

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

The following issue has been updated:

    Updater: James Eitzmann (mailto:jei...@ya...)
       Date: Fri, 14 Nov 2003 10:18 AM
    Comment:
Test driver
    Changes:
             Attachment changed to Test.java
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-470
    Summary: SQL Exception using a Map within a component
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 5

   Assignee: 
   Reporter: James Eitzmann

    Created: Fri, 14 Nov 2003 10:17 AM
    Updated: Fri, 14 Nov 2003 10:18 AM
Environment: nt 2000, oracle 8.1.7, 1.4.1 sdk

Description:
I have a map within a component. When I run a query, I get an SQL exception: "Invalid Column Name". It appears that the SQL hibernate is generating is not including the columns from the mapping table. This works fine in 2.0.3.

Mapping doc:
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
        "-//Hibernate/Hibernate Mapping DTD 2.0//EN"
        "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd">
<hibernate-mapping>
  <class 
  	name="test.hibernate.Test" 
  	table="OBJECT_STACKS"
  	dynamic-update="true"
  	>
  	<id name="id" column="OBJECT_ID" type="string">
      <generator class="com.artesia.server.common.TeamsIdGenerator"/>
    </id>
    <component 
      name="testComponent" 
      class="test.hibernate.TestComponent"
      insert="false"
      update="true"
      >
      <map
  	    name="attrMap"
  	    table="CONTENT_OBJECT_STORAGE_ATTR"
  	    outer-join="true"
  	    batch-size="16"
  	    >
  	    <key column="OBJECT_ID"/>
  	    <index column="ATTR_NAME" type="string"/>
  	    <element column="ATTR_VALUE" type="string"/>
  	  </map>
  	</component>
  </class>
</hibernate-mapping>

Code:
package test.hibernate;

import java.sql.Connection;
import java.sql.DriverManager;
import java.util.ArrayList;
import java.util.List;

import net.sf.hibernate.Criteria;
import net.sf.hibernate.Session;
import net.sf.hibernate.SessionFactory;
import net.sf.hibernate.cfg.Configuration;
import net.sf.hibernate.expression.Expression;
import oracle.jdbc.driver.OracleDriver;

/**
 * 
 * 
 */
public class Test
{
  private String _id;
  private TestComponent _testComponent;
  

	public static void main(String[] args) throws Exception
	{
		DriverManager.registerDriver(new OracleDriver());
		Connection con =
			DriverManager.getConnection("jdbc:oracle:oci8:@j817", "j_adm", "j_adm");

		SessionFactory sf = new Configuration().configure().buildSessionFactory();
		Session s = sf.openSession(con);

		ArrayList contentIdList = new ArrayList(1);
		contentIdList.add("e6656575d7c572592316a2d41bbc4f0a68a7140f");

		Criteria c = s.createCriteria(Test.class);
		c.add(Expression.in("id", contentIdList));
		List infoList = c.list();

	}
  
	/**
	 * @return Returns the id.
	 */
	public String getId()
	{
		return _id;
	}

	/**
	 * @param id The id to set.
	 */
	public void setId(String id)
	{
		_id = id;
	}

	/**
	 * @return Returns the testComponent.
	 */
	public TestComponent getTestComponent()
	{
		return _testComponent;
	}

	/**
	 * @param testComponent The testComponent to set.
	 */
	public void setTestComponent(TestComponent testComponent)
	{
		_testComponent = testComponent;
	}

}



---------------------------------------------------------------------
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-470) SQL Exception using a Map within a component

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-470
    Summary: SQL Exception using a Map within a component
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 5

   Assignee: 
   Reporter: James Eitzmann

    Created: Fri, 14 Nov 2003 10:17 AM
    Updated: Fri, 14 Nov 2003 10:17 AM
Environment: nt 2000, oracle 8.1.7, 1.4.1 sdk

Description:
I have a map within a component. When I run a query, I get an SQL exception: "Invalid Column Name". It appears that the SQL hibernate is generating is not including the columns from the mapping table. This works fine in 2.0.3.

Mapping doc:
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
        "-//Hibernate/Hibernate Mapping DTD 2.0//EN"
        "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd">
<hibernate-mapping>
  <class 
  	name="test.hibernate.Test" 
  	table="OBJECT_STACKS"
  	dynamic-update="true"
  	>
  	<id name="id" column="OBJECT_ID" type="string">
      <generator class="com.artesia.server.common.TeamsIdGenerator"/>
    </id>
    <component 
      name="testComponent" 
      class="test.hibernate.TestComponent"
      insert="false"
      update="true"
      >
      <map
  	    name="attrMap"
  	    table="CONTENT_OBJECT_STORAGE_ATTR"
  	    outer-join="true"
  	    batch-size="16"
  	    >
  	    <key column="OBJECT_ID"/>
  	    <index column="ATTR_NAME" type="string"/>
  	    <element column="ATTR_VALUE" type="string"/>
  	  </map>
  	</component>
  </class>
</hibernate-mapping>

Code:
package test.hibernate;

import java.sql.Connection;
import java.sql.DriverManager;
import java.util.ArrayList;
import java.util.List;

import net.sf.hibernate.Criteria;
import net.sf.hibernate.Session;
import net.sf.hibernate.SessionFactory;
import net.sf.hibernate.cfg.Configuration;
import net.sf.hibernate.expression.Expression;
import oracle.jdbc.driver.OracleDriver;

/**
 * 
 * 
 */
public class Test
{
  private String _id;
  private TestComponent _testComponent;
  

	public static void main(String[] args) throws Exception
	{
		DriverManager.registerDriver(new OracleDriver());
		Connection con =
			DriverManager.getConnection("jdbc:oracle:oci8:@j817", "j_adm", "j_adm");

		SessionFactory sf = new Configuration().configure().buildSessionFactory();
		Session s = sf.openSession(con);

		ArrayList contentIdList = new ArrayList(1);
		contentIdList.add("e6656575d7c572592316a2d41bbc4f0a68a7140f");

		Criteria c = s.createCriteria(Test.class);
		c.add(Expression.in("id", contentIdList));
		List infoList = c.list();

	}
  
	/**
	 * @return Returns the id.
	 */
	public String getId()
	{
		return _id;
	}

	/**
	 * @param id The id to set.
	 */
	public void setId(String id)
	{
		_id = id;
	}

	/**
	 * @return Returns the testComponent.
	 */
	public TestComponent getTestComponent()
	{
		return _testComponent;
	}

	/**
	 * @param testComponent The testComponent to set.
	 */
	public void setTestComponent(TestComponent testComponent)
	{
		_testComponent = testComponent;
	}

}



---------------------------------------------------------------------
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-464) Dialect-specific limit + select distinct

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Thu, 13 Nov 2003 9:37 PM

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-464
    Summary: Dialect-specific limit + select distinct
       Type: Bug

     Status: Closed
   Priority: Minor
 Resolution: FIXED

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

   Assignee: Gavin King
   Reporter: Gavin King

    Created: Tue, 11 Nov 2003 8:05 PM
    Updated: Thu, 13 Nov 2003 9:37 PM

Description:
Some Dialects don't handle distinct elegantly when stting limits:


http://forum.hibernate.org/viewtopic.php?t=924401


---------------------------------------------------------------------
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-469) Allow UserTypes to access property meta-data

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-469
    Summary: Allow UserTypes to access property meta-data
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2

   Assignee: 
   Reporter: Marc Wilson

    Created: Thu, 13 Nov 2003 8:25 PM
    Updated: Thu, 13 Nov 2003 8:25 PM

Description:
From forum topic
http://forum.hibernate.org/viewtopic.php?t=925519&highlight=

The ability for a user type to access the meta data for of a property would be a usefull feature.

One use would be for a UserType that truncates string properties to be able to determine the length it needs to truncate to from the meta data of the property.

I am sure there would be other uses too.



---------------------------------------------------------------------
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-467) Allow composite collection elements in filters

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

The following issue has been updated:

    Updater: Gavin King (mailto:ga...@hi...)
       Date: Thu, 13 Nov 2003 7:46 AM
    Comment:
I'll just change the title :)
    Changes:
             summary changed from Allow composite collection element properties in a query/filter.
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-467
    Summary: Allow composite collection elements in filters
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 5

   Assignee: 
   Reporter: Matt Read

    Created: Wed, 12 Nov 2003 6:31 PM
    Updated: Thu, 13 Nov 2003 7:46 AM

Description:
Section 6.2 of the documentation states:

"Composite element properties may not appear in a query, unfortunately."

The following post from Gavin suggests that this is "probably not very difficult".

http://forum.hibernate.org/viewtopic.php?t=924854

I would really be like to do the following:

int count = ((Integer) session.filter(myCompositeElementsColection, "select count(*) where myProperty = ?", somePropertyValue, Hibernate.entity(SomePropertyType.class)).iterator().next()).intValue();

Thanks,
Matt.


---------------------------------------------------------------------
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-468) handling of version checking in optimistic transactions

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

The following comment has been added to this issue:

     Author: Panagiotis Louridas
    Created: Thu, 13 Nov 2003 7:42 AM
       Body:
Thanks Gavin,

You are right; I should have checked. Sorry if my mail seemed offensive in any way. I had an impression that perhaps hibernate were using some internal versioning mechanism on its session-level cache, and that the programmers were on their own concerning optimistic transactions.

Sorry again. We are a big Greek investment bank and a big development project was saved thanks to hibernate. We develop on hibernate daily for almost a year, and we definitely have had no reasons to believe hibernate's developers stupid.

Best Regards,

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-468
    Summary: handling of version checking in optimistic transactions
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: 
   Reporter: Panagiotis Louridas

    Created: Thu, 13 Nov 2003 3:19 AM
    Updated: Thu, 13 Nov 2003 5:40 AM

Description:
Taking the example given in 14.3.3 of the reference manual,

// foo is an instance loaded by a previous Session
session = factory.openSession();
int oldVersion = foo.getVersion();
session.load( foo, foo.getKey() );
if (oldVersion!=foo.getVersion ) throw new StaleObjectStateException();
foo.setProperty("bar");
session.flush();
session.connection().commit();
session.close();

it is possible that the version check will succeed and yet stale objects will be persisted in the database. Consider two clients A and B, running the above code concurrently. Suppose we have their actions are interleaved in the following way:

A: session = factory.openSession();
B: session = factory.openSession();
A: int oldVersion = foo.getVersion();
B: int oldVersion = foo.getVersion();
A: session.load( foo, foo.getKey() );
B: session.load( foo, foo.getKey() );
A: if (oldVersion!=foo.getVersion ) throw new StaleObjectStateException();
B: if (oldVersion!=foo.getVersion ) throw new StaleObjectStateException();
A: foo.setProperty("Abar");
B: foo.setProperty("Bbar");
A: session.flush();
A: session.connection().commit();

at this point, the object read by client B is stale. Still, B will proceed with

B: session.flush();
B: session.connection().commit();

as if nothing had happened.

I surmise that hibernate produces SQL update code that updates the database tables using the id of the persisted object:

UPDATE ... WHERE id = ...

The above issue would be resolved if the SQL update code also contained a version equality test:

UPDATE ... WHERE id = ... AND version = ...

Best Regards,

Panos Louridas.


---------------------------------------------------------------------
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-468) handling of version checking in optimistic transactions

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Thu, 13 Nov 2003 5:40 AM

If you would have actually tested the functionality before submitting a bug report, you would have seen that Hibernate does exactly what you have suggested. We are not stupid, we know how to do version checking.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-468
    Summary: handling of version checking in optimistic transactions
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: 
   Reporter: Panagiotis Louridas

    Created: Thu, 13 Nov 2003 3:19 AM
    Updated: Thu, 13 Nov 2003 5:40 AM

Description:
Taking the example given in 14.3.3 of the reference manual,

// foo is an instance loaded by a previous Session
session = factory.openSession();
int oldVersion = foo.getVersion();
session.load( foo, foo.getKey() );
if (oldVersion!=foo.getVersion ) throw new StaleObjectStateException();
foo.setProperty("bar");
session.flush();
session.connection().commit();
session.close();

it is possible that the version check will succeed and yet stale objects will be persisted in the database. Consider two clients A and B, running the above code concurrently. Suppose we have their actions are interleaved in the following way:

A: session = factory.openSession();
B: session = factory.openSession();
A: int oldVersion = foo.getVersion();
B: int oldVersion = foo.getVersion();
A: session.load( foo, foo.getKey() );
B: session.load( foo, foo.getKey() );
A: if (oldVersion!=foo.getVersion ) throw new StaleObjectStateException();
B: if (oldVersion!=foo.getVersion ) throw new StaleObjectStateException();
A: foo.setProperty("Abar");
B: foo.setProperty("Bbar");
A: session.flush();
A: session.connection().commit();

at this point, the object read by client B is stale. Still, B will proceed with

B: session.flush();
B: session.connection().commit();

as if nothing had happened.

I surmise that hibernate produces SQL update code that updates the database tables using the id of the persisted object:

UPDATE ... WHERE id = ...

The above issue would be resolved if the SQL update code also contained a version equality test:

UPDATE ... WHERE id = ... AND version = ...

Best Regards,

Panos Louridas.


---------------------------------------------------------------------
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-468) handling of version checking in optimistic transactions

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-468
    Summary: handling of version checking in optimistic transactions
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: 
   Reporter: Panagiotis Louridas

    Created: Thu, 13 Nov 2003 3:19 AM
    Updated: Thu, 13 Nov 2003 3:19 AM

Description:
Taking the example given in 14.3.3 of the reference manual,

// foo is an instance loaded by a previous Session
session = factory.openSession();
int oldVersion = foo.getVersion();
session.load( foo, foo.getKey() );
if (oldVersion!=foo.getVersion ) throw new StaleObjectStateException();
foo.setProperty("bar");
session.flush();
session.connection().commit();
session.close();

it is possible that the version check will succeed and yet stale objects will be persisted in the database. Consider two clients A and B, running the above code concurrently. Suppose we have their actions are interleaved in the following way:

A: session = factory.openSession();
B: session = factory.openSession();
A: int oldVersion = foo.getVersion();
B: int oldVersion = foo.getVersion();
A: session.load( foo, foo.getKey() );
B: session.load( foo, foo.getKey() );
A: if (oldVersion!=foo.getVersion ) throw new StaleObjectStateException();
B: if (oldVersion!=foo.getVersion ) throw new StaleObjectStateException();
A: foo.setProperty("Abar");
B: foo.setProperty("Bbar");
A: session.flush();
A: session.connection().commit();

at this point, the object read by client B is stale. Still, B will proceed with

B: session.flush();
B: session.connection().commit();

as if nothing had happened.

I surmise that hibernate produces SQL update code that updates the database tables using the id of the persisted object:

UPDATE ... WHERE id = ...

The above issue would be resolved if the SQL update code also contained a version equality test:

UPDATE ... WHERE id = ... AND version = ...

Best Regards,

Panos Louridas.


---------------------------------------------------------------------
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-467) Allow composite collection element properties in a query/filter.

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

The following comment has been added to this issue:

     Author: Matt Read
    Created: Thu, 13 Nov 2003 2:00 AM
       Body:
Ok, well in my ignorance I assumed that one might imply the other, obviously not. Should I raise a seperate JIRA issue to clarify what it is exactly I'm looking for or does this one still do the job?

Matt.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-467
    Summary: Allow composite collection element properties in a query/filter.
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 5

   Assignee: 
   Reporter: Matt Read

    Created: Wed, 12 Nov 2003 6:31 PM
    Updated: Wed, 12 Nov 2003 6:31 PM

Description:
Section 6.2 of the documentation states:

"Composite element properties may not appear in a query, unfortunately."

The following post from Gavin suggests that this is "probably not very difficult".

http://forum.hibernate.org/viewtopic.php?t=924854

I would really be like to do the following:

int count = ((Integer) session.filter(myCompositeElementsColection, "select count(*) where myProperty = ?", somePropertyValue, Hibernate.entity(SomePropertyType.class)).iterator().next()).intValue();

Thanks,
Matt.


---------------------------------------------------------------------
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-466) 2.1 beta6 slow?

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Wed, 12 Nov 2003 8:48 PM

This difference is due to the removal of the PreparedStatement cache in 2.1. Try using the DBCP connection provider which does prepared statement caching.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-466
    Summary: 2.1 beta6 slow?
       Type: Bug

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

    Project: Hibernate2

   Assignee: 
   Reporter: Daniel Rosenbaum

    Created: Wed, 12 Nov 2003 4:13 PM
    Updated: Wed, 12 Nov 2003 8:48 PM
Environment: Windows XP 1.66 GHZ 512 megs ram

Description:
When running the same code with both 2.0.3 and 2.1 beta 6, the beta runs much slower when doing an iterate().

This is the result of a discussion on the Beginners forum at http://forum.hibernate.org/viewtopic.php?t=925487

With my sample code, running using the 2.0.3 jars took 14435 ms to get appox 700 objects from the db, but with the beta it took 45618 ms, about 3 times slower.  I repeated this test a number of times with similar results.

I provided the classes, xml files and props.  I also provided logs, one set with SQL logging and one without (the sql logging logs show greater execution time due to the extra i/o involved in logging the SQL).

Is it only on my system that this is happening?  

Note also that I am not sure if anyone would even be able to execute the code, since it uses a db table I have in my db.  I suppose one can do schemaexport and populate the resulting table with 700 rows.

Thank you.


---------------------------------------------------------------------
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-467) Allow composite collection element properties in a query/filter.

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

The following comment has been added to this issue:

     Author: Gavin King
    Created: Wed, 12 Nov 2003 7:40 PM
       Body:
Composite elements may now appear in queries. We havn't got collection filter support working yet, however.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-467
    Summary: Allow composite collection element properties in a query/filter.
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 5

   Assignee: 
   Reporter: Matt Read

    Created: Wed, 12 Nov 2003 6:31 PM
    Updated: Wed, 12 Nov 2003 6:31 PM

Description:
Section 6.2 of the documentation states:

"Composite element properties may not appear in a query, unfortunately."

The following post from Gavin suggests that this is "probably not very difficult".

http://forum.hibernate.org/viewtopic.php?t=924854

I would really be like to do the following:

int count = ((Integer) session.filter(myCompositeElementsColection, "select count(*) where myProperty = ?", somePropertyValue, Hibernate.entity(SomePropertyType.class)).iterator().next()).intValue();

Thanks,
Matt.


---------------------------------------------------------------------
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-465) Floats truncated with Oracle 9i

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

The following comment has been added to this issue:

     Author: Gavin King
    Created: Wed, 12 Nov 2003 7:38 PM
       Body:
In future, please do not report things that are quite obviously JDBC driver bugs here! Go to the user forum if you are not sure.

I would comment that in general its reasonable to assume that Hibernate is much better tested and bug-free than your JDBC driver, so looking elsewhere first will save us all time.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-465
    Summary: Floats truncated with Oracle 9i
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.3

   Assignee: 
   Reporter: Jose Raya

    Created: Wed, 12 Nov 2003 12:05 PM
    Updated: Wed, 12 Nov 2003 1:04 PM
Environment: Oracle 9i (don't know exact version number) with Oracle9i dialect
Oracle thin driver
Oracle9iAS (9.0.3.0.0)
jdk 1.3.1_06 for Windows (2000)
Hibernate version 2.0.3, 27 August 2003 

Description:
As a post in your forum says:
"the float mapping using oracle 9i (9.2.0.1) does NOT work, while double works fine. whenever we store a float value, it is truncated to an integer value. changing the mapping and the bean to double works like expected. I use the right jdbc driver for our version, like provided by oracle and I use jdk 1.4.2."

See post at http://forum.hibernate.org/viewtopic.php?p=2177880#2177880



---------------------------------------------------------------------
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-467) Allow composite collection element properties in a query/filter.

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-467
    Summary: Allow composite collection element properties in a query/filter.
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 5

   Assignee: 
   Reporter: Matt Read

    Created: Wed, 12 Nov 2003 6:31 PM
    Updated: Wed, 12 Nov 2003 6:31 PM

Description:
Section 6.2 of the documentation states:

"Composite element properties may not appear in a query, unfortunately."

The following post from Gavin suggests that this is "probably not very difficult".

http://forum.hibernate.org/viewtopic.php?t=924854

I would really be like to do the following:

int count = ((Integer) session.filter(myCompositeElementsColection, "select count(*) where myProperty = ?", somePropertyValue, Hibernate.entity(SomePropertyType.class)).iterator().next()).intValue();

Thanks,
Matt.


---------------------------------------------------------------------
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-466) 2.1 beta6 slow?

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

The following issue has been updated:

    Updater: Daniel Rosenbaum (mailto:dro...@if...)
       Date: Wed, 12 Nov 2003 4:13 PM
    Changes:
             Attachment changed to testhibernate.ZIP
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-466
    Summary: 2.1 beta6 slow?
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2

   Assignee: 
   Reporter: Daniel Rosenbaum

    Created: Wed, 12 Nov 2003 4:13 PM
    Updated: Wed, 12 Nov 2003 4:13 PM
Environment: Windows XP 1.66 GHZ 512 megs ram

Description:
When running the same code with both 2.0.3 and 2.1 beta 6, the beta runs much slower when doing an iterate().

This is the result of a discussion on the Beginners forum at http://forum.hibernate.org/viewtopic.php?t=925487

With my sample code, running using the 2.0.3 jars took 14435 ms to get appox 700 objects from the db, but with the beta it took 45618 ms, about 3 times slower.  I repeated this test a number of times with similar results.

I provided the classes, xml files and props.  I also provided logs, one set with SQL logging and one without (the sql logging logs show greater execution time due to the extra i/o involved in logging the SQL).

Is it only on my system that this is happening?  

Note also that I am not sure if anyone would even be able to execute the code, since it uses a db table I have in my db.  I suppose one can do schemaexport and populate the resulting table with 700 rows.

Thank you.


---------------------------------------------------------------------
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-466) 2.1 beta6 slow?

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-466
    Summary: 2.1 beta6 slow?
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2

   Assignee: 
   Reporter: Daniel Rosenbaum

    Created: Wed, 12 Nov 2003 4:13 PM
    Updated: Wed, 12 Nov 2003 4:13 PM
Environment: Windows XP 1.66 GHZ 512 megs ram

Description:
When running the same code with both 2.0.3 and 2.1 beta 6, the beta runs much slower when doing an iterate().

This is the result of a discussion on the Beginners forum at http://forum.hibernate.org/viewtopic.php?t=925487

With my sample code, running using the 2.0.3 jars took 14435 ms to get appox 700 objects from the db, but with the beta it took 45618 ms, about 3 times slower.  I repeated this test a number of times with similar results.

I provided the classes, xml files and props.  I also provided logs, one set with SQL logging and one without (the sql logging logs show greater execution time due to the extra i/o involved in logging the SQL).

Is it only on my system that this is happening?  

Note also that I am not sure if anyone would even be able to execute the code, since it uses a db table I have in my db.  I suppose one can do schemaexport and populate the resulting table with 700 rows.

Thank you.


---------------------------------------------------------------------
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-465) Floats truncated with Oracle 9i

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

Message:

   The following issue has been closed.

   Resolver: Max Rydahl Andersen
       Date: Wed, 12 Nov 2003 1:04 PM

This is actually documented at http://hibernate.org/80.html (though there was a mistype in the version number 9.2.0.3 had become 9.0.3)

But I will close this bug since it is not a bug in hibernate. (but pleaes verify that you can make it work with the latest driver - just for the record ;)
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-465
    Summary: Floats truncated with Oracle 9i
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.3

   Assignee: 
   Reporter: Jose Raya

    Created: Wed, 12 Nov 2003 12:05 PM
    Updated: Wed, 12 Nov 2003 1:04 PM
Environment: Oracle 9i (don't know exact version number) with Oracle9i dialect
Oracle thin driver
Oracle9iAS (9.0.3.0.0)
jdk 1.3.1_06 for Windows (2000)
Hibernate version 2.0.3, 27 August 2003 

Description:
As a post in your forum says:
"the float mapping using oracle 9i (9.2.0.1) does NOT work, while double works fine. whenever we store a float value, it is truncated to an integer value. changing the mapping and the bean to double works like expected. I use the right jdbc driver for our version, like provided by oracle and I use jdk 1.4.2."

See post at http://forum.hibernate.org/viewtopic.php?p=2177880#2177880



---------------------------------------------------------------------
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-465) Floats truncated with Oracle 9i

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

The following comment has been added to this issue:

     Author: Max Rydahl Andersen
    Created: Wed, 12 Nov 2003 12:49 PM
       Body:
Last i checked this bug (which is in oracle driver - not hibernate!) the stuff worked on the latest driver.

Could you try with the latest drivers ? (9.2.0.3)
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-465
    Summary: Floats truncated with Oracle 9i
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.3

   Assignee: 
   Reporter: Jose Raya

    Created: Wed, 12 Nov 2003 12:05 PM
    Updated: Wed, 12 Nov 2003 12:05 PM
Environment: Oracle 9i (don't know exact version number) with Oracle9i dialect
Oracle thin driver
Oracle9iAS (9.0.3.0.0)
jdk 1.3.1_06 for Windows (2000)
Hibernate version 2.0.3, 27 August 2003 

Description:
As a post in your forum says:
"the float mapping using oracle 9i (9.2.0.1) does NOT work, while double works fine. whenever we store a float value, it is truncated to an integer value. changing the mapping and the bean to double works like expected. I use the right jdbc driver for our version, like provided by oracle and I use jdk 1.4.2."

See post at http://forum.hibernate.org/viewtopic.php?p=2177880#2177880



---------------------------------------------------------------------
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-465) Floats truncated with Oracle 9i

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

The following comment has been added to this issue:

     Author: Jose Raya
    Created: Wed, 12 Nov 2003 12:07 PM
       Body:
I don't have a full log but I have a snip.
As you can see, the value for parameter 8 gets to the PreparedStatement but is truncated on saving.

DEBUG-12/11 17:42:34,304-SessionFactoryImpl-prepared statement get: update DescripcioAssignatura set assignaturaId=?, descripcioLlarga=?, descripcioCurta=?, curs=?, horesCalculades=?, departamentId=?, coordinadorDescripcio=?, factorHoresCredit=?, ensenyament=? where id=?
DEBUG-12/11 17:42:34,304-SessionFactoryImpl-preparing statement
DEBUG-12/11 17:42:34,314-EntityPersister-Dehydrating entity: es.castinfo.ub.domain.DescripcioAssignatura#DescripcioAssignatura-9
DEBUG-12/11 17:42:34,314-StringType-binding 'ASS-11' to parameter: 1
DEBUG-12/11 17:42:34,314-StringType-binding 'DescripcioAssignatura-9/descripcioLlarga' to parameter: 2
DEBUG-12/11 17:42:34,314-StringType-binding 'DescripcioAssignatura-9/descripcioCurta' to parameter: 3
DEBUG-12/11 17:42:34,314-StringType-binding 'C1' to parameter: 4
DEBUG-12/11 17:42:34,314-BooleanType-binding 'false' to parameter: 5
DEBUG-12/11 17:42:34,314-StringType-binding 'DEPT1' to parameter: 6
DEBUG-12/11 17:42:34,314-LongType-binding '1' to parameter: 7
DEBUG-12/11 17:42:34,324-FloatType-binding '0.5' to parameter: 8
DEBUG-12/11 17:42:34,324-StringType-binding 'ENS1' to parameter: 9
DEBUG-12/11 17:42:34,324-StringType-binding 'DescripcioAssignatura-9' to parameter: 10
DEBUG-12/11 17:42:34,324-BatcherImpl-Adding to batch
DEBUG-12/11 17:42:34,324-BatcherImpl-Executing batch size: 1
DEBUG-12/11 17:42:34,324-BatcherImpl-done closing: 0 open PreparedStatements, 0 open ResultSets

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-465
    Summary: Floats truncated with Oracle 9i
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.3

   Assignee: 
   Reporter: Jose Raya

    Created: Wed, 12 Nov 2003 12:05 PM
    Updated: Wed, 12 Nov 2003 12:05 PM
Environment: Oracle 9i (don't know exact version number) with Oracle9i dialect
Oracle thin driver
Oracle9iAS (9.0.3.0.0)
jdk 1.3.1_06 for Windows (2000)
Hibernate version 2.0.3, 27 August 2003 

Description:
As a post in your forum says:
"the float mapping using oracle 9i (9.2.0.1) does NOT work, while double works fine. whenever we store a float value, it is truncated to an integer value. changing the mapping and the bean to double works like expected. I use the right jdbc driver for our version, like provided by oracle and I use jdk 1.4.2."

See post at http://forum.hibernate.org/viewtopic.php?p=2177880#2177880



---------------------------------------------------------------------
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-465) Floats truncated with Oracle 9i

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-465
    Summary: Floats truncated with Oracle 9i
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.3

   Assignee: 
   Reporter: Jose Raya

    Created: Wed, 12 Nov 2003 12:05 PM
    Updated: Wed, 12 Nov 2003 12:05 PM
Environment: Oracle 9i (don't know exact version number) with Oracle9i dialect
Oracle thin driver
Oracle9iAS (9.0.3.0.0)
jdk 1.3.1_06 for Windows (2000)
Hibernate version 2.0.3, 27 August 2003 

Description:
As a post in your forum says:
"the float mapping using oracle 9i (9.2.0.1) does NOT work, while double works fine. whenever we store a float value, it is truncated to an integer value. changing the mapping and the bean to double works like expected. I use the right jdbc driver for our version, like provided by oracle and I use jdk 1.4.2."

See post at http://forum.hibernate.org/viewtopic.php?p=2177880#2177880



---------------------------------------------------------------------
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-464) Dialect-specific limit + select distinct

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

Message:

   The following issue has been re-assigned.

   Assignee: Gavin King (mailto:ga...@hi...)
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-464
    Summary: Dialect-specific limit + select distinct
       Type: Bug

     Status: Assigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 5

   Assignee: Gavin King
   Reporter: Gavin King

    Created: Tue, 11 Nov 2003 8:05 PM
    Updated: Wed, 12 Nov 2003 9:33 AM

Description:
Some Dialects don't handle distinct elegantly when stting limits:


http://forum.hibernate.org/viewtopic.php?t=924401


---------------------------------------------------------------------
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-464) Dialect-specific limit + select distinct

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-464
    Summary: Dialect-specific limit + select distinct
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 5

   Assignee: 
   Reporter: Gavin King

    Created: Tue, 11 Nov 2003 8:05 PM
    Updated: Tue, 11 Nov 2003 8:05 PM

Description:
Some Dialects don't handle distinct elegantly when stting limits:


http://forum.hibernate.org/viewtopic.php?t=924401


---------------------------------------------------------------------
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] =?UTF-8?Q?[Hibernate-JIRA]_Deleted:_(HB-463)_=E5=86=AC=E7=9C=A0?=

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

Message:

  The following issue has been deleted from JIRA.

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-463
    Summary: =E5=86=AC=E7=9C=A0
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Hibernate2

   Assignee:=20
   Reporter: Fengbo Tse

    Created: Tue, 11 Nov 2003 2:21 AM
    Updated: Tue, 11 Nov 2003 2:21 AM
Environment: =E5=BE=AE=E8=BD=AF=E8=A7=86=E7=AA=97=E6=93=8D=E4=BD=9C=E7=B3=
=BB=E7=BB=9F

Description:
=E6=B2=A1=E6=9C=89=E3=80=82=E6=B5=8B=E8=AF=95=E7=9B=AE=E7=9A=84=E4=B9=8B=E4=
=BD=BF=E7=94=A8=E3=80=82


---------------------------------------------------------------------
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] =?UTF-8?Q?[Hibernate-JIRA]_Created:_(HB-463)_=E5=86=AC=E7=9C=A0?=

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

Message:

  A new issue has been created in JIRA.

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-463
    Summary: =E5=86=AC=E7=9C=A0
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Hibernate2

   Assignee:=20
   Reporter: Fengbo Tse

    Created: Tue, 11 Nov 2003 2:21 AM
    Updated: Tue, 11 Nov 2003 2:21 AM
Environment: =E5=BE=AE=E8=BD=AF=E8=A7=86=E7=AA=97=E6=93=8D=E4=BD=9C=E7=B3=
=BB=E7=BB=9F

Description:
=E6=B2=A1=E6=9C=89=E3=80=82=E6=B5=8B=E8=AF=95=E7=9B=AE=E7=9A=84=E4=B9=8B=E4=
=BD=BF=E7=94=A8=E3=80=82


---------------------------------------------------------------------
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-12) low performance loading with optional 1-1 association

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

The following issue has been updated:

    Updater: Gavin King (mailto:ga...@hi...)
       Date: Sun, 9 Nov 2003 9:43 AM
    Comment:
Now also implemented for HQL FETCH clause. Other cases much less important.
    Changes:
             priority changed from Major
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-12
    Summary:  low performance loading with optional 1-1 association
       Type: Bug

     Status: In Progress
   Priority: Minor

    Project: Hibernate2

   Assignee: Gavin King
   Reporter: Max Rydahl Andersen

    Created: Sat, 3 May 2003 10:02 AM
    Updated: Sun, 9 Nov 2003 9:43 AM

Description:
low performance loading with optional 1-1 association
I use Hibernate 1.2.3. 

There is a problem, which causes a severe performance loss: 

If you have 2 entites (A and B) with a 1-1 association, 
Hibernate uses an SQL query with a join (if enabled) to 
load both entites with 1 statement. Wonderful! If there 
is a B for an A, everything is okay. 

If there is no B for a certain A, Hibernate tries 
(although the 1st statment returned no instance for B) 
to load B, when you invoke the corresponding getter, 
which results in an unnecessary SQL query! 

If there are many entities associated, there are many 
unnecessesary SQL queries and the performance suffers. 

Thanks 
Markus 

(Original: http://sourceforge.net/tracker/index.php?func=detail&aid=686577&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] Commented: (HB-12) low performance loading with optional 1-1 association

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

The following comment has been added to this issue:

     Author: Gavin King
    Created: Sun, 9 Nov 2003 12:27 AM
       Body:
fixed (finally) for load(), get() and Criteria queries .... other cases to come: HQL queries, collection initialization.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-12
    Summary:  low performance loading with optional 1-1 association
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: Hibernate2

   Assignee: Gavin King
   Reporter: Max Rydahl Andersen

    Created: Sat, 3 May 2003 10:02 AM
    Updated: Sat, 3 May 2003 10:02 AM

Description:
low performance loading with optional 1-1 association
I use Hibernate 1.2.3. 

There is a problem, which causes a severe performance loss: 

If you have 2 entites (A and B) with a 1-1 association, 
Hibernate uses an SQL query with a join (if enabled) to 
load both entites with 1 statement. Wonderful! If there 
is a B for an A, everything is okay. 

If there is no B for a certain A, Hibernate tries 
(although the 1st statment returned no instance for B) 
to load B, when you invoke the corresponding getter, 
which results in an unnecessary SQL query! 

If there are many entities associated, there are many 
unnecessesary SQL queries and the performance suffers. 

Thanks 
Markus 

(Original: http://sourceforge.net/tracker/index.php?func=detail&aid=686577&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