hibernate-issues — Hibernate JIRA Notifications

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-7) Oracle "Paging Select" w/association problem

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Wed, 11 Jun 2003 8:03 AM

This was fixed, I think. Would someone please verify that ... and re-open this issue if it is not.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-7
    Summary: Oracle "Paging Select" w/association problem   
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.0 final
   Versions:
             2.0rc2

   Assignee: Gavin King
   Reporter: Dave White

    Created: Wed, 30 Apr 2003 9:06 PM
    Updated: Wed, 11 Jun 2003 8:03 AM

Description:
I have a mapping that looks like this: 

<class name="Foo" proxy="Foo" table="Tbl_Foo" dynamic-update="true"> 
  <composite-id name="fooKey" class="FooKey"> 
    <key-property name="barId" column="barID" type="int"/> 
    <key-property name="id2"   column="ID2"   type="int"/> 
  </composite-id> 
  <property name="location" column="Location" type="string"/> 
  <many-to-one name="barRef" class="Bar" cascade="none" 
               insert="false" update="false"> 
    <column name="barID"/> 
  </many-to-one> 
</class> 

As you can see, the the id of Foo is the same as the foreign key used in the many-to-one association to Bar. I've used the insert/update attributes to say that the barID column should not be include (twice) in the insert/update statements. However, when I do a query against this class the generated SQL contains the barID column twice in the select statement. Once for the composite-id, and once for the many-to-one association. This became a problem when I applied my "paging select" patch for Oracle which looks like this: 

select * 
from (select a.*, rownum rnum 
from ( <hibernate-generated-sql> ) a 
where rownum <= ?) 
where rnum >= ? 

The reason this is a problem is that when the <hibernate-generated-sql> statement contains the same column twice in the select clause, Oracle complains about ambiguously declared columns. I'm wondering if different aliases could be generated in the SQL for columns defined in composite-id vs. property vs. many-to-one? 

I did look into the <key-many-to-one> tag in the composite-id, but that didn't fit well with my (already-in-place/legacy) object model. 



---------------------------------------------------------------------
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/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-92) Retrieving native generated identifiers does not support generic Hibernate types

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

The following issue has been updated:

    Updater: Gavin King (mailto:ga...@in...)
       Date: Wed, 11 Jun 2003 8:01 AM
    Changes:
          type changed from Bug to Patch
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-92
    Summary: Retrieving native generated identifiers does not support generic Hibernate types
       Type: Patch

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: Gavin King
   Reporter: Chris Webb

    Created: Wed, 21 May 2003 5:00 AM
    Updated: Wed, 11 Jun 2003 8:01 AM

Description:
At present Hibernate does not support identifier types other than Short, Integer or Long for native generated identifiers. This presents a problem when a user defined type is used to encapsulate an identifier that can support natively generated identifiers. An example is where a identifier type is defined that stores the natively generated value internally as a long, thus is similiar to a Long type but not actually a Long type.

The solution is to use the actual identifier type to extract the identifer value from the appropriate retrieve identifier SQL result set rather than the method IdentifierGeneratorFactory.get(ResultSet, Class) which in fact has been flagged as inappropriate in the source code documentation.

A patch has been supplied that does the following:
1. Removes the method get(ResultSet, Class) from IdentifierGeneratorFactory.
2. Changes SequenceGenerator and AbstractEntityPersister to add an 'id' column alias to the SQL used for retrieving the natively generated identifier.
3 Changes SequenceGenerator, EntityPersister and NormalizedEntityPersister to retrieve the identifier value from the SQL result set using the identifer type via the method nullSafeGet(ResultSet rs, String colName, SessionImplementor session, Object owner).



---------------------------------------------------------------------
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/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-128) OuterJoinLoader.walkClassTree() throws AbstractMethodError under jdk1.2.2 - AbstractEntityPersister needs to be made public

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Wed, 11 Jun 2003 7:48 AM

fixed in CVS
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-128
    Summary: OuterJoinLoader.walkClassTree() throws AbstractMethodError under jdk1.2.2 - AbstractEntityPersister needs to be made public
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.0.1
   Versions:
             2.0 final

   Assignee: Gavin King
   Reporter: Renaud Bruyeron

    Created: Wed, 11 Jun 2003 3:50 AM
    Updated: Wed, 11 Jun 2003 7:48 AM
Environment: linux 2.4.18, iplanet Web Server 6.0SP2, Struts 1.1RC2
java version "1.2.2"
Classic VM (build JDK-1.2.2_014, green threads, nojit)

Description:

during Configuration().configure(), the JVM throws an AbstractMethodError like follows:

[11/Jun/2003:09:16:32] failure (11523): Internal error: Unexpected error condition thrown (java.lang
.AbstractMethodError: net/sf/hibernate/persister/AbstractEntityPersister.insert,net/sf/hibernate/per
sister/AbstractEntityPersister.insert), stack: java.lang.AbstractMethodError: net/sf/hibernate/persi
ster/AbstractEntityPersister.insert
        at net.sf.hibernate.loader.OuterJoinLoader.walkClassTree(OuterJoinLoader.java:191)
        at net.sf.hibernate.loader.OuterJoinLoader.walkTree(OuterJoinLoader.java:80)
        at net.sf.hibernate.loader.AbstractEntityLoader.renderStatement(AbstractEntityLoader.java:38
)
        at net.sf.hibernate.loader.AbstractEntityLoader.renderStatement(AbstractEntityLoader.java:33
)
        at net.sf.hibernate.loader.EntityLoader.<init>(EntityLoader.java:35)
        at net.sf.hibernate.persister.EntityPersister.postInstantiate(EntityPersister.java:150)
        at net.sf.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:241)
        at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:613)
        at com.fullsix.registration.config.HibernatePlugIn.init(HibernatePlugIn.java:60)
        at org.apache.struts.action.ActionServlet.initModulePlugIns(ActionServlet.java:1156)
        at org.apache.struts.action.ActionServlet.init(ActionServlet.java:472)
        at javax.servlet.GenericServlet.init(GenericServlet.java:258)
        at com.iplanet.server.http.servlet.WServletEntity.loadAndInitServlet(WServletEntity.java:98)
        at com.iplanet.server.http.servlet.WebApplication.init(WebApplication.java:314)
        at com.iplanet.server.http.servlet.VirtualServer.init(VirtualServer.java:176)
        at com.iplanet.server.http.servlet.NSServletRunner.VSInit(NSServletRunner.java:686)


This can be fixed by declaring net.sf.hibernate.persister.AbstractEntityPersister to be "public".

This problem affects 1.2.x 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/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-129) Query.iterate() using setFirstResult and setMaxResult

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-129
    Summary: Query.iterate() using setFirstResult and setMaxResult
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: 
   Reporter: David Howe

    Created: Wed, 11 Jun 2003 5:49 AM
    Updated: Wed, 11 Jun 2003 5:49 AM

Description:
I am getting some strange behaviour when using Query.iterate() with setFirstResult and setMaxResult. When the following code is run, the number of rows returned is the sum of the first result and the max result (ie. 15 rows): 

Query q = session.createQuery("from com.logicacmg.waf.FixedCode as fixedCode"); 

q.setFirstResult(5); 
q.setMaxResults(10); 

Iterator iter = q.iterate(); 

while (iter.hasNext()) { 
// Do the processing 
} 

The following SQL statement is generated for the initial query: 

select fixedcod0_.fixed_code_id as x0_0_ from FIXED_CODE fixedcod0_ limit ?, ? 

The behaviour of the number of rows returned being the sum of the first result and the max results seems to be consistent. 

If I remove using the query.iterate() and go back to using a query.list(), everything works perfectly and I get 10 rows i.e.: 

q.setFirstResult(5); 
q.setMaxResults(10); 

iter = q.list().iterator(); 

while (iter.hasNext()) { 
// Do the processing 
} 

This generates the following SQL: 

select fixedcod0_.fixed_code_id as fixed_code_id, fixedcod0_.last_updated_sequence as last_upd2_, fixedcod0_.column_name as column_n3_, fixedcod0_.code as code, fixedcod0_.description as descript5_, fixedcod0_.sort_sequence as sort_seq6_, fixedcod0_.CREATED_USER_ID as CREATED_7_, fixedcod0_.CREATED_DT_TM as CREATED_8_, fixedcod0_.LAST_UPDATED_USER_ID as LAST_UPD9_, fixedcod0_.LAST_UPDATED_DT_TM as LAST_UP10_ from FIXED_CODE fixedcod0_ limit ?, ? 

I am running with Hibernate 2 (just upgraded) and MySQL 3.23. The above code was existing code that worked under Hibernate 1. 


By: oneovthafew ( Gavin King ) 
 RE: Query.iterate() setFirstResult problem   
2003-06-11 01:35  
Oh bloody hell this is a pretty bad bug. Damn! 


ah well ..... Hibernate 2.0.1 here we come.... 

P.S. you can work around this by overriding supportsLimit() on MySQLDialect. 


>> If I remove using the query.iterate() and go back to using a query.list(), everything works perfectly and I get 10 rows << 

yah, the test suite only covers *this* case :(  

By: oneovthafew ( Gavin King ) 
 RE: Query.iterate() setFirstResult problem   
2003-06-11 01:38  
please submit this to JIRA 

TIA 

I will fix it tonight anyway....  



---------------------------------------------------------------------
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/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-128) OuterJoinLoader.walkClassTree() throws AbstractMethodError under jdk1.2.2 - AbstractEntityPersister needs to be made public

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-128
    Summary: OuterJoinLoader.walkClassTree() throws AbstractMethodError under jdk1.2.2 - AbstractEntityPersister needs to be made public
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: 
   Reporter: Renaud Bruyeron

    Created: Wed, 11 Jun 2003 3:50 AM
    Updated: Wed, 11 Jun 2003 3:50 AM
Environment: linux 2.4.18, iplanet Web Server 6.0SP2, Struts 1.1RC2
java version "1.2.2"
Classic VM (build JDK-1.2.2_014, green threads, nojit)

Description:

during Configuration().configure(), the JVM throws an AbstractMethodError like follows:

[11/Jun/2003:09:16:32] failure (11523): Internal error: Unexpected error condition thrown (java.lang
.AbstractMethodError: net/sf/hibernate/persister/AbstractEntityPersister.insert,net/sf/hibernate/per
sister/AbstractEntityPersister.insert), stack: java.lang.AbstractMethodError: net/sf/hibernate/persi
ster/AbstractEntityPersister.insert
        at net.sf.hibernate.loader.OuterJoinLoader.walkClassTree(OuterJoinLoader.java:191)
        at net.sf.hibernate.loader.OuterJoinLoader.walkTree(OuterJoinLoader.java:80)
        at net.sf.hibernate.loader.AbstractEntityLoader.renderStatement(AbstractEntityLoader.java:38
)
        at net.sf.hibernate.loader.AbstractEntityLoader.renderStatement(AbstractEntityLoader.java:33
)
        at net.sf.hibernate.loader.EntityLoader.<init>(EntityLoader.java:35)
        at net.sf.hibernate.persister.EntityPersister.postInstantiate(EntityPersister.java:150)
        at net.sf.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:241)
        at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:613)
        at com.fullsix.registration.config.HibernatePlugIn.init(HibernatePlugIn.java:60)
        at org.apache.struts.action.ActionServlet.initModulePlugIns(ActionServlet.java:1156)
        at org.apache.struts.action.ActionServlet.init(ActionServlet.java:472)
        at javax.servlet.GenericServlet.init(GenericServlet.java:258)
        at com.iplanet.server.http.servlet.WServletEntity.loadAndInitServlet(WServletEntity.java:98)
        at com.iplanet.server.http.servlet.WebApplication.init(WebApplication.java:314)
        at com.iplanet.server.http.servlet.VirtualServer.init(VirtualServer.java:176)
        at com.iplanet.server.http.servlet.NSServletRunner.VSInit(NSServletRunner.java:686)


This can be fixed by declaring net.sf.hibernate.persister.AbstractEntityPersister to be "public".

This problem affects 1.2.x 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/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-126) Wrong version number for 2.0 final

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Tue, 10 Jun 2003 9:09 PM

fixed (we rebuilt 2.0 final)
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-126
    Summary: Wrong version number for 2.0 final
       Type: Bug

     Status: Closed
   Priority: Trivial
 Resolution: FIXED

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.0 final
   Versions:
             2.0 final

   Assignee: Gavin King
   Reporter: Leonardo Quijano

    Created: Mon, 9 Jun 2003 10:17 AM
    Updated: Tue, 10 Jun 2003 9:09 PM

Description:
From Environment.java:

	private static final String VERSION = "2.0 beta 6";

I thought that I was still using the old version, but then I checked the file's data: June 6, 2003 - 12:51 pm.


---------------------------------------------------------------------
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/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-127) CounterGenerator Bug

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-127
    Summary: CounterGenerator Bug
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: 
   Reporter: Maks Glukhovtsev

    Created: Tue, 10 Jun 2003 8:23 AM
    Updated: Tue, 10 Jun 2003 8:23 AM
Environment: Sybase 11.9.2

Description:
When using "vm" generator, experiencing problem of trying to insert a non-unique value of PK. 

When sleep() inserted in generate() (just for test purposes), problem disappeared.

So, with minor changes:

	private static long counter =  0;

	protected long getCount() {
		synchronized(CounterGenerator.class) {
			if (counter==0) counter=System.currentTimeMillis();
			return counter++;
		}
	}

	public Serializable generate(SessionImplementor cache, Object obj) {
		return new Long( getCount() );
	}

problem has been resolved.

please.. do something more serious about it :)




---------------------------------------------------------------------
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/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-122) Global "on/off" property for SessionFactory-level cache

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

The following comment has been added to this issue:

     Author: Markus Menner
    Created: Tue, 10 Jun 2003 2:01 AM
       Body:
How can I configure the cache in the .cfg.xml ?

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-122
    Summary: Global "on/off" property for SessionFactory-level cache
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.0rc2

   Assignee: 
   Reporter: Markus Menner

    Created: Fri, 6 Jun 2003 1:41 AM
    Updated: Fri, 6 Jun 2003 1:41 AM

Description:
It would be nice to have a property to switch on/off SessionFactory-level cache (for example to check performance improvements caching vs. no-caching).

At the moment you have to remove/add the jcs-cache tags in the mapping files.





---------------------------------------------------------------------
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/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-125) generator class="assigned", when used in parent-children model's child class

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Mon, 9 Jun 2003 10:07 PM

unsaved-value="null" is not sensible for assigned ids. Please do NOT report bugs in user code here. JIRA is for bugs in *Hibernate*. TIA
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-125
    Summary: generator class="assigned", when used in parent-children model's child class
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: Gavin King
   Reporter: neil yang

    Created: Sun, 8 Jun 2003 10:27 PM
    Updated: Mon, 9 Jun 2003 10:07 PM
Environment: windows xp

Description:
I have two class: Company & Person, they're Parent-children relation-ship. the 2 classes' id are all "assigned", beacause in an other true development env., I had to use programatic "assigned" id. When I run the test code, the exception thrown.

package h;

import java.util.ArrayList;
import java.util.Date;
public class Company {
    static int _lastID = 100;
    String id;
    public void setId(String value) {
        this.id=value;
    }
    public String getId() {
        return id;
    }

    String name;
    public void setName(String value) {
        this.name=value;
    }
    public String getName() {
        return name;
    }

    ArrayList partners = new ArrayList();
    public String[] getMyPartners(){
      return (String[])partners.toArray(new String[partners.size()]);
    }
    public void setMyPartners(String[] parts){
        partners.clear();
        for(int i=0; i<parts.length; i++){
            partners.add(parts[i]);
        }
    }

    java.util.Date createdDate;
    public void setCreatedDate(Date d ){
        this.createdDate = d;
    }
    public Date getCreatedDate(){
        return this.createdDate;
    }
    java.util.List employees=new java.util.ArrayList();
    public void setEmployees(java.util.List value) {
        this.employees=value;
    }
    public java.util.List getEmployees() {
        return employees;
    }
    public void addEmployee(h.Person value) {
        employees.add(value);
    }
    public void removeEmployee(h.Person value) {
        employees.remove(value);
    }
    public void clearEmployees() {
        employees.clear();
    }
    private boolean _registered;
    public boolean getRegistered(){
        return this._registered;
    }
    public void setRegistered(boolean val){
        this._registered = val;
    }


}

Company.hbm.xml:
<?xml version="1.0" encoding="GB2312"?>
<!DOCTYPE hibernate-mapping SYSTEM "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd" >
<hibernate-mapping>

	<class name="h.Company">
		<id name = "id" unsaved-value = "null">
			<generator class="assigned"/>
		</id>		
        <property name="name"/>
        <property name="myPartners" type="serializable" />
        <property name="registered" type="boolean"/>
	    <bag name="employees" cascade="all">
            <key column="company_id"/>
            <one-to-many class="h.Person"/>
        </bag>
	</class>
</hibernate-mapping>


package h;

import java.io.Serializable;

public class Person implements Serializable{
    public static int _lastID = 1000;
    String name;

/**
Sets the value of field name.
@param name value of field name
*/

    public void setName(String value) {
        this.name=value;
    }

/**
Gets the value of field name.
@return value of field name
*/

    public String getName() {
        return name;
    }

    String address;

/**
Sets the value of field address.
@param address value of field address
*/
    public void setAddress(String value) {
        this.address=value;
    }

/**
Gets the value of field address.
@return value of field address
*/

    public String getAddress() {
        return address;
    }

    String id ;

/**
Sets the value of field id.
@param id value of field id
*/

    public void setId(String value) {
        this.id=value;
    }

/**
Gets the value of field id.
@return value of field id
*/

    public String getId() {
        return id;
    }
}

Person.hbm.xml:
<?xml version="1.0" encoding="GB2312"?>
<!DOCTYPE hibernate-mapping SYSTEM "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd" >
<hibernate-mapping>

	<class name="h.Person">
		<id name = "id" unsaved-value = "null">
               <generator class="assigned"/>
		</id>
		<property name="name"/>
		<property name="address"/>
	</class>
</hibernate-mapping>

the Test code is:

package h;

import net.sf.hibernate.Session;
import net.sf.hibernate.Transaction;
import net.sf.hibernate.SessionFactory;
import net.sf.hibernate.Query;
import net.sf.hibernate.cfg.Configuration;
import net.sf.hibernate.tool.hbm2ddl.SchemaExport;

import java.util.List;
import java.util.Iterator;



class TestCompany
{

    private static SessionFactory sessions;

    public static void main(String[] args) throws Exception
    {

        String[] partners = {
            "IBM",
            "Microsoft",
            "Lenovo",
            "Apple"
        };

        
        Configuration conf = new Configuration()
                .addClass(Person.class)
                .addClass(Company.class);

        
        SchemaExport dbExport = new SchemaExport(conf);
        dbExport.setOutputFile("sql.txt");
        dbExport.create(true, true);

        sessions = conf.buildSessionFactory();
        
         //start......
        Session s = sessions.openSession();
        Transaction t = s.beginTransaction();

        Company c = new Company();
        c.setName("UFSoft Company Ltd.");
        c.setMyPartners(partners);
        c.setRegistered(true);

        Person p1 = new Person();
        p1.setId(String.valueOf(Person._lastID++));
        p1.setName("Liuto");
        p1.setAddress("Beijing Haidian");

        Person p2 = new Person();
        p2.setId(String.valueOf(Person._lastID++));
        p2.setName("sun");
        p2.setAddress("beijing shangdi");

        c.addEmployee(p1);
        c.addEmployee(p2);

      
         c.setId(String.valueOf(Company._lastID++));
        //c.setId(Company._lastID++);
        s.save(c);

        s.flush();
        t.commit();


        s.close();
        sessions.close();
    }
}

when flush(), the bug reported:
net.sf.hibernate.HibernateException: SQL update or deletion failed (row not found)
	at net.sf.hibernate.impl.NonBatchingBatcher.addToBatch(NonBatchingBatcher.java:25)
	at net.sf.hibernate.persister.EntityPersister.update(EntityPersister.java:611)
	at net.sf.hibernate.persister.EntityPersister.update(EntityPersister.java:580)
	at net.sf.hibernate.impl.ScheduledUpdate.execute(ScheduledUpdate.java:27)
	at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2073)
	at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2046)
	at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:1989)
	at h.TestCompany.main(TestCompany.java:115)




---------------------------------------------------------------------
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/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-124) Hibernate thinks unmodified <set> of value objects is dirty

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

The following comment has been added to this issue:

     Author: Gavin King
    Created: Mon, 9 Jun 2003 10:06 PM
       Body:
That line of code is correct.

Are you *sure* that your composite element class implements equals() / hashCode() correctly, as is required by the Set contract?

I doubt that there is a bug in Set....
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-124
    Summary: Hibernate thinks unmodified <set> of value objects is dirty
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: 
   Reporter: Chris Richardson

    Created: Sun, 8 Jun 2003 7:36 PM
    Updated: Sun, 8 Jun 2003 7:36 PM
Environment: Win2k

Description:
Hibernate thinks that a collection of value objects is modified when it really isn't. It tries to save it to the DB everytime it is loaded.

This line from Set.snapshot looks suspect:

clonedSet.put(copied, copied);

Shouldn't the key be the original value - not the copy?


Here is an excerpt of my mapping file:

  				<set name="timeRanges" table="FTGO_RESTAURANT_TIME_RANGE" cascade="all">
					<key column="RESTAURANT_ID"/> 
						<composite-element class="net.chrisrichardson.foodToGo.order.hibernateImpl.HibernateTimeRange"> 
		                <property name="dayOfWeek" column="day_Of_Week"/>
		                <property name="openHour" column="open_Hour"/>
		                <property name="openMinute" column="open_Minute"/>
		                <property name="closeHour" column="close_Hour"/>
		                <property name="closeMinute" column="close_Minute"/>
				    </composite-element>
 				</set>




---------------------------------------------------------------------
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/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-126) Wrong version number for 2.0 final

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-126
    Summary: Wrong version number for 2.0 final
       Type: Bug

     Status: Unassigned
   Priority: Trivial

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: 
   Reporter: Leonardo Quijano

    Created: Mon, 9 Jun 2003 10:17 AM
    Updated: Mon, 9 Jun 2003 10:17 AM

Description:
From Environment.java:

	private static final String VERSION = "2.0 beta 6";

I thought that I was still using the old version, but then I checked the file's data: June 6, 2003 - 12:51 pm.


---------------------------------------------------------------------
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/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-113) Oracle LIMIT Bug (Was HB-88)

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

The following comment has been added to this issue:

     Author: Leonardo Quijano
    Created: Mon, 9 Jun 2003 10:15 AM
       Body:
Just downloaded 2.0 final. Seems to be working fine :)
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-113
    Summary: Oracle LIMIT Bug (Was HB-88)
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.0 final

   Assignee: Gavin King
   Reporter: Leonardo Quijano

    Created: Thu, 29 May 2003 7:19 PM
    Updated: Sat, 7 Jun 2003 7:21 AM
Environment: CVS May 29, 2003

Description:
I'm reopening bug HB-88 (I don't know how to reopen bugs like in Bugzilla.. :( ). It's still wrong. Right now, we have in Oracle9Dialect:

public String getLimitString(String sql) {
	StringBuffer pagingSelect = new StringBuffer(100);
	pagingSelect.append("select * from ( select row_.*, rownum rownum_ from ( ");
	pagingSelect.append(sql);
	pagingSelect.append(" ) row_ where rownum <= ?) where rownum_ >= ?");
	return pagingSelect.toString();
}

From Oracle 9i Documentation (http://otn.oracle.com/docs/products/oracle9i/doc_library/release2/server.920/a96540/sql_elements6a.htm#27457)

"ROWNUM

For each row returned by a query, the ROWNUM pseudocolumn returns a number indicating the order in which Oracle selects the row from a table or set of joined rows. The first row selected has a ROWNUM of 1, the second has 2, and so on."

In Hibernate's doc, it says:

"setFirstResult

public Query setFirstResult(int firstResult)

    Set the first row to retrieve. If not set, rows will be retrieved beginnning from row 0. This method is more efficient if the JDBC driver supports scrollable ResultSets.

    Parameters:
        firstResult - a row number, numbered from 0"

So, if I call query.setFirstResult(0) - as documented - it should give me the first result in Oracle (Oracle ROWNUM 1). So maybe it should be:

	pagingSelect.append(" ) row_ where rownum <= ?) where rownum_ > ?");

or

	pagingSelect.append(" ) row_ where rownum <= ?) where rownum_ >= (? + 1)");

(don't know if the last one works, though). 

I don't know if the value is increased in some other place... but it's still not working for me. I applied the change and it did work. 

Leonardo





---------------------------------------------------------------------
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/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-81) Missing Online Documentation for Hibernate2

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

The following comment has been added to this issue:

     Author: Leonardo Quijano
    Created: Mon, 9 Jun 2003 1:00 AM
       Body:
Regrettably, I still disagree :(.
I was asking for *both* documentations, not only 2.0 final ;)....

But, anyway, that's IMHO, maybe you could ask around to see what people think :).

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-81
    Summary: Missing Online Documentation for Hibernate2
       Type: New Feature

     Status: Closed
   Priority: Minor
 Resolution: FIXED

    Project: Hibernate2
   Versions:
             2.0 final

   Assignee: Gavin King
   Reporter: Leonardo Quijano

    Created: Fri, 16 May 2003 9:18 AM
    Updated: Sun, 8 Jun 2003 6:26 AM
Environment: Online Docs

Description:
I recently posted something about this on the forum (http://sourceforge.net/forum/message.php?msg_id=1993128). I'm reposting here to make a formal request. 

It seems that there's no references to Hibernate2's docs on the main website. I *know* it's included in the downloaded package, but that's not my point. It'd be useful to have both documentations online. For example: I downloaded the whole hibernate page for my web app, but there are other developers who don't. It's easier to tell them the Internet URL so I don't have to share my package and they don't have to download it themselves, either. And neither doc should have preference over the other (there are people developing in both versions of Hibernate).

It's just as easy as:

Reference Documentation

Hibernate 1.x:

    * Online HTML version
    * Single Page HTML version (230 kb)
    * PDF Print version (670 kb)

    * API Javadoc
    * Hibernate Mapping DTD

Hibernate 2.x:

    * Online HTML version
    * Single Page HTML version (230 kb)
    * PDF Print version (670 kb)

    * API Javadoc
    * Hibernate Mapping DTD

Leonardo


---------------------------------------------------------------------
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/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-125) generator class="assigned", when used in parent-children model's child class

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-125
    Summary: generator class="assigned", when used in parent-children model's child class
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: 
   Reporter: neil yang

    Created: Sun, 8 Jun 2003 10:27 PM
    Updated: Sun, 8 Jun 2003 10:27 PM
Environment: windows xp

Description:
I have two class: Company & Person, they're Parent-children relation-ship. the 2 classes' id are all "assigned", beacause in an other true development env., I had to use programatic "assigned" id. When I run the test code, the exception thrown.

package h;

import java.util.ArrayList;
import java.util.Date;
public class Company {
    static int _lastID = 100;
    String id;
    public void setId(String value) {
        this.id=value;
    }
    public String getId() {
        return id;
    }

    String name;
    public void setName(String value) {
        this.name=value;
    }
    public String getName() {
        return name;
    }

    ArrayList partners = new ArrayList();
    public String[] getMyPartners(){
      return (String[])partners.toArray(new String[partners.size()]);
    }
    public void setMyPartners(String[] parts){
        partners.clear();
        for(int i=0; i<parts.length; i++){
            partners.add(parts[i]);
        }
    }

    java.util.Date createdDate;
    public void setCreatedDate(Date d ){
        this.createdDate = d;
    }
    public Date getCreatedDate(){
        return this.createdDate;
    }
    java.util.List employees=new java.util.ArrayList();
    public void setEmployees(java.util.List value) {
        this.employees=value;
    }
    public java.util.List getEmployees() {
        return employees;
    }
    public void addEmployee(h.Person value) {
        employees.add(value);
    }
    public void removeEmployee(h.Person value) {
        employees.remove(value);
    }
    public void clearEmployees() {
        employees.clear();
    }
    private boolean _registered;
    public boolean getRegistered(){
        return this._registered;
    }
    public void setRegistered(boolean val){
        this._registered = val;
    }


}

Company.hbm.xml:
<?xml version="1.0" encoding="GB2312"?>
<!DOCTYPE hibernate-mapping SYSTEM "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd" >
<hibernate-mapping>

	<class name="h.Company">
		<id name = "id" unsaved-value = "null">
			<generator class="assigned"/>
		</id>		
        <property name="name"/>
        <property name="myPartners" type="serializable" />
        <property name="registered" type="boolean"/>
	    <bag name="employees" cascade="all">
            <key column="company_id"/>
            <one-to-many class="h.Person"/>
        </bag>
	</class>
</hibernate-mapping>


package h;

import java.io.Serializable;

public class Person implements Serializable{
    public static int _lastID = 1000;
    String name;

/**
Sets the value of field name.
@param name value of field name
*/

    public void setName(String value) {
        this.name=value;
    }

/**
Gets the value of field name.
@return value of field name
*/

    public String getName() {
        return name;
    }

    String address;

/**
Sets the value of field address.
@param address value of field address
*/
    public void setAddress(String value) {
        this.address=value;
    }

/**
Gets the value of field address.
@return value of field address
*/

    public String getAddress() {
        return address;
    }

    String id ;

/**
Sets the value of field id.
@param id value of field id
*/

    public void setId(String value) {
        this.id=value;
    }

/**
Gets the value of field id.
@return value of field id
*/

    public String getId() {
        return id;
    }
}

Person.hbm.xml:
<?xml version="1.0" encoding="GB2312"?>
<!DOCTYPE hibernate-mapping SYSTEM "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd" >
<hibernate-mapping>

	<class name="h.Person">
		<id name = "id" unsaved-value = "null">
               <generator class="assigned"/>
		</id>
		<property name="name"/>
		<property name="address"/>
	</class>
</hibernate-mapping>

the Test code is:

package h;

import net.sf.hibernate.Session;
import net.sf.hibernate.Transaction;
import net.sf.hibernate.SessionFactory;
import net.sf.hibernate.Query;
import net.sf.hibernate.cfg.Configuration;
import net.sf.hibernate.tool.hbm2ddl.SchemaExport;

import java.util.List;
import java.util.Iterator;



class TestCompany
{

    private static SessionFactory sessions;

    public static void main(String[] args) throws Exception
    {

        String[] partners = {
            "IBM",
            "Microsoft",
            "Lenovo",
            "Apple"
        };

        
        Configuration conf = new Configuration()
                .addClass(Person.class)
                .addClass(Company.class);

        
        SchemaExport dbExport = new SchemaExport(conf);
        dbExport.setOutputFile("sql.txt");
        dbExport.create(true, true);

        sessions = conf.buildSessionFactory();
        
         //start......
        Session s = sessions.openSession();
        Transaction t = s.beginTransaction();

        Company c = new Company();
        c.setName("UFSoft Company Ltd.");
        c.setMyPartners(partners);
        c.setRegistered(true);

        Person p1 = new Person();
        p1.setId(String.valueOf(Person._lastID++));
        p1.setName("Liuto");
        p1.setAddress("Beijing Haidian");

        Person p2 = new Person();
        p2.setId(String.valueOf(Person._lastID++));
        p2.setName("sun");
        p2.setAddress("beijing shangdi");

        c.addEmployee(p1);
        c.addEmployee(p2);

      
         c.setId(String.valueOf(Company._lastID++));
        //c.setId(Company._lastID++);
        s.save(c);

        s.flush();
        t.commit();


        s.close();
        sessions.close();
    }
}

when flush(), the bug reported:
net.sf.hibernate.HibernateException: SQL update or deletion failed (row not found)
	at net.sf.hibernate.impl.NonBatchingBatcher.addToBatch(NonBatchingBatcher.java:25)
	at net.sf.hibernate.persister.EntityPersister.update(EntityPersister.java:611)
	at net.sf.hibernate.persister.EntityPersister.update(EntityPersister.java:580)
	at net.sf.hibernate.impl.ScheduledUpdate.execute(ScheduledUpdate.java:27)
	at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2073)
	at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2046)
	at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:1989)
	at h.TestCompany.main(TestCompany.java:115)




---------------------------------------------------------------------
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/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-124) Hibernate thinks unmodified <set> of value objects is dirty

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-124
    Summary: Hibernate thinks unmodified <set> of value objects is dirty
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: 
   Reporter: Chris Richardson

    Created: Sun, 8 Jun 2003 7:36 PM
    Updated: Sun, 8 Jun 2003 7:36 PM
Environment: Win2k

Description:
Hibernate thinks that a collection of value objects is modified when it really isn't. It tries to save it to the DB everytime it is loaded.

This line from Set.snapshot looks suspect:

clonedSet.put(copied, copied);

Shouldn't the key be the original value - not the copy?


Here is an excerpt of my mapping file:

  				<set name="timeRanges" table="FTGO_RESTAURANT_TIME_RANGE" cascade="all">
					<key column="RESTAURANT_ID"/> 
						<composite-element class="net.chrisrichardson.foodToGo.order.hibernateImpl.HibernateTimeRange"> 
		                <property name="dayOfWeek" column="day_Of_Week"/>
		                <property name="openHour" column="open_Hour"/>
		                <property name="openMinute" column="open_Minute"/>
		                <property name="closeHour" column="close_Hour"/>
		                <property name="closeMinute" column="close_Minute"/>
				    </composite-element>
 				</set>




---------------------------------------------------------------------
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/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-98) SchemaExport does not generate the multicolumn index

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Sun, 8 Jun 2003 6:29 AM

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-98
    Summary: SchemaExport does not generate the multicolumn index 
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: CANNOT REPRODUCE

    Project: Hibernate2
 Components: 
             toolset
   Versions:
             2.0rc2

   Assignee: Gavin King
   Reporter: Dan Tran

    Created: Fri, 23 May 2003 2:04 AM
    Updated: Sun, 8 Jun 2003 6:29 AM
Environment: HSQL 1.7.1 JDK 1.4.1

Description:
Hi SchemaExport does not generate the multicolumn index as specified in the map file.




---------------------------------------------------------------------
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/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-81) Missing Online Documentation for Hibernate2

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Sun, 8 Jun 2003 6:26 AM

Christian just fixed this :)
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-81
    Summary: Missing Online Documentation for Hibernate2
       Type: New Feature

     Status: Closed
   Priority: Minor
 Resolution: FIXED

    Project: Hibernate2
   Versions:
             2.0 final

   Assignee: Gavin King
   Reporter: Leonardo Quijano

    Created: Fri, 16 May 2003 9:18 AM
    Updated: Sun, 8 Jun 2003 6:26 AM
Environment: Online Docs

Description:
I recently posted something about this on the forum (http://sourceforge.net/forum/message.php?msg_id=1993128). I'm reposting here to make a formal request. 

It seems that there's no references to Hibernate2's docs on the main website. I *know* it's included in the downloaded package, but that's not my point. It'd be useful to have both documentations online. For example: I downloaded the whole hibernate page for my web app, but there are other developers who don't. It's easier to tell them the Internet URL so I don't have to share my package and they don't have to download it themselves, either. And neither doc should have preference over the other (there are people developing in both versions of Hibernate).

It's just as easy as:

Reference Documentation

Hibernate 1.x:

    * Online HTML version
    * Single Page HTML version (230 kb)
    * PDF Print version (670 kb)

    * API Javadoc
    * Hibernate Mapping DTD

Hibernate 2.x:

    * Online HTML version
    * Single Page HTML version (230 kb)
    * PDF Print version (670 kb)

    * API Javadoc
    * Hibernate Mapping DTD

Leonardo


---------------------------------------------------------------------
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/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-104) Unable to locate dialect when only specified in properties file

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Sun, 8 Jun 2003 6:24 AM

I fixed the problem with the doco.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-104
    Summary: Unable to locate dialect when only specified in properties file
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Hibernate2
   Fix Fors:
             2.0 final
   Versions:
             2.0rc2

   Assignee: Gavin King
   Reporter: Axel Fontaine

    Created: Sun, 25 May 2003 4:34 PM
    Updated: Sun, 8 Jun 2003 6:24 AM
Environment: WinXP SP1, Eclipse 2.1, Hibernate 2.0 beta 6, McKoi 1.0.1

Description:
When using the following property file:

hibernate.dialect = net.sf.hibernate.dialect.McKoiDialect
hibernate.connection.driver_class = com.mckoi.JDBCDriver
hibernate.connection.url = jdbc:mckoi://localhost/
hibernate.connection.username = dbadmin
hibernate.connection.password = dbpass

hibernate complains that it can't find the dialect net.sf.hibernate.dialect.McKoiDialect


Adding this to the code makes it work:
Configuration config = new Configuration();
config.setProperty("hibernate.dialect", MckoiDialect.class.getName());


---------------------------------------------------------------------
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/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-75) Some javadoc problems in build.xml

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

Message:

   The following issue has been re-assigned.

   Assignee: Christian Bauer (mailto:chr...@bl...)
   Assigner: Gavin King (mailto:ga...@in...)
       Date: Sun, 8 Jun 2003 6:23 AM
    Comment:
The missing packages are intentionally not documented (they are internal impl).

Christian, if you get a change ... would you please look at the build script problem (not high priority).
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-75
    Summary: Some javadoc problems in build.xml
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.0rc2

   Assignee: Christian Bauer
   Reporter: Lu Yunhai

    Created: Tue, 13 May 2003 11:40 PM
    Updated: Sun, 8 Jun 2003 6:23 AM
Environment: Win2000 JDK1.4.1 

Description:
1. line28-line29
    <property name="doc.api.dir" value="${doc.dir}/api"/>
    <property name="doc.ref.dir" value="${doc.dir}/reference"/>
should be 
    <property name="doc.api.dir" value="${doc.dir}/hib_docs/api"/>
    <property name="doc.ref.dir" value="${doc.dir}/hib_docs/reference"/>

2. line175
         Overview="${doc.api.dir}/package.html"
should be
         Overview="${doc.api.dir}/packages.html"

3. some packages missed in javadoc:
        net.sf.hibernate.collection
        net.sf.hibernate.hql
        net.sf.hibernate.impl
        net.sf.hibernate.jca
        net.sf.hibernate.lob
        net.sf.hibernate.proxy
        net.sf.hibernate.ps
        net.sf.hibernate.sql
        net.sf.hibernate.tool
        net.sf.hibernate.tool.*
        net.sf.hibernate.util
        net.sf.hibernate.xml
Maybe not all these packages should be put into javadoc, but there are some do need such as net.sf.hibernate.impl.SessionFactoryImpl, otherwise SessionFactoryImplementor's seealso will be incorrect.


---------------------------------------------------------------------
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/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-100) Bad reference to the Configurator class in the documentation

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Sun, 8 Jun 2003 6:21 AM

Thanks. I fixed this.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-100
    Summary: Bad reference to the Configurator class in the documentation
       Type: Bug

     Status: Closed
   Priority: Minor
 Resolution: FIXED

    Project: Hibernate2
   Fix Fors:
             2.0 final
   Versions:
             2.0rc2

   Assignee: Gavin King
   Reporter: Ruben de Heras

    Created: Fri, 23 May 2003 12:11 PM
    Updated: Sun, 8 Jun 2003 6:21 AM
Environment: Doesn't apply

Description:
In the documentation provided with Hibernate 2.0 Beta6 seems to be a typo in the html file session-configuration.html

Chapter 2. SessionFactory Configuration -> 2.1. Programmatic Configuration

An instance of net.sf.hibernate.Configuration  represents [...] 

Shouldn't it be net.sf.hibernate.cfg.Configuration?


---------------------------------------------------------------------
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/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-92) Retrieving native generated identifiers does not support generic Hibernate types

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

Message:

   The following issue has been re-assigned.

   Assignee: Gavin King (mailto:ga...@in...)
   Assigner: Gavin King (mailto:ga...@in...)
       Date: Sun, 8 Jun 2003 6:20 AM
    Comment:
I'll look at this ASAP.

Thanks :)
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-92
    Summary: Retrieving native generated identifiers does not support generic Hibernate types
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: Gavin King
   Reporter: Chris Webb

    Created: Wed, 21 May 2003 5:00 AM
    Updated: Sun, 8 Jun 2003 6:20 AM

Description:
At present Hibernate does not support identifier types other than Short, Integer or Long for native generated identifiers. This presents a problem when a user defined type is used to encapsulate an identifier that can support natively generated identifiers. An example is where a identifier type is defined that stores the natively generated value internally as a long, thus is similiar to a Long type but not actually a Long type.

The solution is to use the actual identifier type to extract the identifer value from the appropriate retrieve identifier SQL result set rather than the method IdentifierGeneratorFactory.get(ResultSet, Class) which in fact has been flagged as inappropriate in the source code documentation.

A patch has been supplied that does the following:
1. Removes the method get(ResultSet, Class) from IdentifierGeneratorFactory.
2. Changes SequenceGenerator and AbstractEntityPersister to add an 'id' column alias to the SQL used for retrieving the natively generated identifier.
3 Changes SequenceGenerator, EntityPersister and NormalizedEntityPersister to retrieve the identifier value from the SQL result set using the identifer type via the method nullSafeGet(ResultSet rs, String colName, SessionImplementor session, Object owner).



---------------------------------------------------------------------
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/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-113) Oracle LIMIT Bug (Was HB-88)

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Sat, 7 Jun 2003 7:21 AM

Okay, I applied your suggested fix. (looks correct)

Please check out from CVS and test it for me TIA.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-113
    Summary: Oracle LIMIT Bug (Was HB-88)
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.0 final

   Assignee: Gavin King
   Reporter: Leonardo Quijano

    Created: Thu, 29 May 2003 7:19 PM
    Updated: Sat, 7 Jun 2003 7:21 AM
Environment: CVS May 29, 2003

Description:
I'm reopening bug HB-88 (I don't know how to reopen bugs like in Bugzilla.. :( ). It's still wrong. Right now, we have in Oracle9Dialect:

public String getLimitString(String sql) {
	StringBuffer pagingSelect = new StringBuffer(100);
	pagingSelect.append("select * from ( select row_.*, rownum rownum_ from ( ");
	pagingSelect.append(sql);
	pagingSelect.append(" ) row_ where rownum <= ?) where rownum_ >= ?");
	return pagingSelect.toString();
}

From Oracle 9i Documentation (http://otn.oracle.com/docs/products/oracle9i/doc_library/release2/server.920/a96540/sql_elements6a.htm#27457)

"ROWNUM

For each row returned by a query, the ROWNUM pseudocolumn returns a number indicating the order in which Oracle selects the row from a table or set of joined rows. The first row selected has a ROWNUM of 1, the second has 2, and so on."

In Hibernate's doc, it says:

"setFirstResult

public Query setFirstResult(int firstResult)

    Set the first row to retrieve. If not set, rows will be retrieved beginnning from row 0. This method is more efficient if the JDBC driver supports scrollable ResultSets.

    Parameters:
        firstResult - a row number, numbered from 0"

So, if I call query.setFirstResult(0) - as documented - it should give me the first result in Oracle (Oracle ROWNUM 1). So maybe it should be:

	pagingSelect.append(" ) row_ where rownum <= ?) where rownum_ > ?");

or

	pagingSelect.append(" ) row_ where rownum <= ?) where rownum_ >= (? + 1)");

(don't know if the last one works, though). 

I don't know if the value is increased in some other place... but it's still not working for me. I applied the change and it did work. 

Leonardo





---------------------------------------------------------------------
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/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-123) Apply distinctness to HQL fetch of collection

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-123
    Summary: Apply distinctness to HQL fetch of collection
       Type: Task

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: 
   Reporter: Steve Knight

    Created: Fri, 6 Jun 2003 11:34 PM
    Updated: Fri, 6 Jun 2003 11:34 PM

Description:
HQL fetch of an associated collection should return distinct entities.
For example, the following HQL:

"FROM Department dept LEFT JOIN FETCH dept.personnel"

should return each department(with its associated collection) only once.


---------------------------------------------------------------------
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/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-122) Global "on/off" property for SessionFactory-level cache

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

The following comment has been added to this issue:

     Author: Gavin King
    Created: Fri, 6 Jun 2003 8:55 PM
       Body:
It is also now possible to config caching in the .cfg.xml file. That makes it a lot easier to disable caching. Does that address this issue?
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-122
    Summary: Global "on/off" property for SessionFactory-level cache
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.0rc2

   Assignee: 
   Reporter: Markus Menner

    Created: Fri, 6 Jun 2003 1:41 AM
    Updated: Fri, 6 Jun 2003 1:41 AM

Description:
It would be nice to have a property to switch on/off SessionFactory-level cache (for example to check performance improvements caching vs. no-caching).

At the moment you have to remove/add the jcs-cache tags in the mapping files.





---------------------------------------------------------------------
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/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-113) Oracle LIMIT Bug (Was HB-88)

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

The following comment has been added to this issue:

     Author: Leonardo Quijano
    Created: Fri, 6 Jun 2003 12:45 PM
       Body:
Anything you need to confirm this? I don't like keeping a self-patched version of Hibernate around... specially in a release for a client ;).

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-113
    Summary: Oracle LIMIT Bug (Was HB-88)
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core

   Assignee: Gavin King
   Reporter: Leonardo Quijano

    Created: Thu, 29 May 2003 7:19 PM
    Updated: Thu, 29 May 2003 8:52 PM
Environment: CVS May 29, 2003

Description:
I'm reopening bug HB-88 (I don't know how to reopen bugs like in Bugzilla.. :( ). It's still wrong. Right now, we have in Oracle9Dialect:

public String getLimitString(String sql) {
	StringBuffer pagingSelect = new StringBuffer(100);
	pagingSelect.append("select * from ( select row_.*, rownum rownum_ from ( ");
	pagingSelect.append(sql);
	pagingSelect.append(" ) row_ where rownum <= ?) where rownum_ >= ?");
	return pagingSelect.toString();
}

From Oracle 9i Documentation (http://otn.oracle.com/docs/products/oracle9i/doc_library/release2/server.920/a96540/sql_elements6a.htm#27457)

"ROWNUM

For each row returned by a query, the ROWNUM pseudocolumn returns a number indicating the order in which Oracle selects the row from a table or set of joined rows. The first row selected has a ROWNUM of 1, the second has 2, and so on."

In Hibernate's doc, it says:

"setFirstResult

public Query setFirstResult(int firstResult)

    Set the first row to retrieve. If not set, rows will be retrieved beginnning from row 0. This method is more efficient if the JDBC driver supports scrollable ResultSets.

    Parameters:
        firstResult - a row number, numbered from 0"

So, if I call query.setFirstResult(0) - as documented - it should give me the first result in Oracle (Oracle ROWNUM 1). So maybe it should be:

	pagingSelect.append(" ) row_ where rownum <= ?) where rownum_ > ?");

or

	pagingSelect.append(" ) row_ where rownum <= ?) where rownum_ >= (? + 1)");

(don't know if the last one works, though). 

I don't know if the value is increased in some other place... but it's still not working for me. I applied the change and it did work. 

Leonardo





---------------------------------------------------------------------
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/Administrators.jspa

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