hibernate-issues — Hibernate JIRA Notifications

[Hibernate-issues] [Hibernate-JIRA] Created: (HB-136) Criteria api appears to add elements to a SortedSet before setting their properties

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-136
    Summary: Criteria api appears to add elements to a SortedSet before setting their properties
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: 
   Reporter: Paul Rivers

    Created: Sat, 14 Jun 2003 4:16 PM
    Updated: Sat, 14 Jun 2003 4:16 PM
Environment: Eclipse 2.1, Tomcat4.1.24, jdk1.4.1_03

Description:
As I understand it, this query by criteria query:

Criteria criteria = session.createCriteria(EntryDAO.class);
criteria.setFirstResult(rangeStart);
criteria.setMaxResults(rangeSize);
criteria.addOrder(Order.desc("dateCreated"));
entries = criteria.list();

Should return the same results as this one:
Query query = session.createQuery("from EntryDAO order by dateCreated desc");
query.setFirstResult(rangeStart);
query.setMaxResults(rangeSize);
entries = query.list();

The problem is that the normal (second) query executes fine, but the Criteria (first) query throws a NullPointerException. Each entry has a SortedSet of Categories (It's specified in the mapping file). The stack trace for the null pointer exception leads to this line:

result = this.getName().compareTo(otherCategory.getName());

In this function:

public int compareTo(Object o) {
	int result;
	CategoryDAO otherCategory = (CategoryDAO) o;
	
	result = this.getDisplayIndex() - otherCategory.getDisplayIndex();
	if(result == 0) {
		result = this.getName().compareTo(otherCategory.getName());
	}
	
	return result;
}



The problem appears to be, to me, that for some reason the Criteria API 1. does the database query, 2. adds the new object to the SortedSet, 3. THEN sets it's properties, where it should be 1. doing the query 2. setting the properties, 3. then adding the category to the sortedset.

PLEASE let me know if there's anything I can do to help with the issue, or if there's any other information you would like. Thanks.


---------------------------------------------------------------------
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-131) Select...Limit syntax changed from PostgreSQL 6.5 to 7.0

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Sat, 14 Jun 2003 11:24 AM

I have changed the Postgres dialect to use LIMIT x OFFSET y
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-131
    Summary: Select...Limit syntax changed from PostgreSQL 6.5 to 7.0
       Type: Improvement

     Status: Closed
   Priority: Major
 Resolution: FIXED

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

   Assignee: Gavin King
   Reporter: Jesse McLaughlin

    Created: Thu, 12 Jun 2003 12:16 AM
    Updated: Sat, 14 Jun 2003 11:24 AM

Description:
Using the

Query.setMaxResults(); 

method with the PostgreSQL dialect while using PostgreSQL version >= 7.0 causes the following error: 

14:20:31,140 ERROR [JDBCExceptionReporter] Could not execute query 
java.sql.SQLException: ERROR: LIMIT #,# syntax not supported. 
Use separate LIMIT and OFFSET clauses. 

PostgreSQLDialect.java reads: 

public String getLimitString(String sql) { 
  StringBuffer pagingSelect = new StringBuffer(100); 
  pagingSelect.append(sql); 
  pagingSelect.append(" limit ?, ?"); 
  return pagingSelect.toString(); 
} 

However, the Select..Limit syntax has changed from PostgreSQL 7.0, refer:

SELECT

PostgreSQL 6.5 Synopsis

http://www.postgresql.org/docs/view.php?version=6.5&idoc=1&file=sql-select.htm

SELECT [ALL|DISTINCT [ON column] ]
    expression [ AS
   name ] [, ...]
    [ INTO [TEMP] [TABLE] new_table ]
    [ FROM table
   [alias ] [, ...] ]
    [ WHERE condition ]
    [ GROUP BY column [, ...] ]
    [ HAVING condition [, ...] ]
    [ { UNION [ALL] | INTERSECT | EXCEPT } select ]
    [ ORDER BY column [ ASC | DESC ] [, ...] ]
    [ FOR UPDATE [OF class_name...]]
    [ LIMIT count [OFFSET|, count]]

Compare with:

PostgreSQL 7.0 Synopsis

http://www.postgresql.org/docs/view.php?version=7.0&idoc=1&file=sql-select.htm

SELECT [ ALL | DISTINCT [ ON ( expression [, ...] ) ] ]
    expression [ AS name ] [, ...]
    [ INTO [ TEMPORARY | TEMP ] [ TABLE ] new_table ]
    [ FROM table [ alias ] [, ...] ]
    [ WHERE condition ]
    [ GROUP BY column [, ...] ]
    [ HAVING condition [, ...] ]
    [ { UNION [ ALL ] | INTERSECT | EXCEPT } select ]
    [ ORDER BY column [ ASC | DESC | USING operator ] [, ...] ]
    [ FOR UPDATE [ OF class_name [, ...] ] ]
    LIMIT { count | ALL } [ { OFFSET | , } start ]

The Hibernate PostgreSQL dialect should be updated (or a new one created) to reflect this change.



---------------------------------------------------------------------
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-134) the "where" attribute in collection mapping generates incorrect sql

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Sat, 14 Jun 2003 4:54 AM

The trouble here is that "true" is not really standard SQL. I know Postgres recognizes this, but Hibernate's Dialect system doesn't yet try and abstract these kind of details. For now, use the workaround you discovered.

The parser of the where attribute is pretty braindead, but capable of handling _most_ use cases.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-134
    Summary: the "where" attribute in collection mapping generates incorrect sql
       Type: Bug

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

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: Gavin King
   Reporter: Antoni Reus

    Created: Fri, 13 Jun 2003 6:47 AM
    Updated: Sat, 14 Jun 2003 4:54 AM
Environment: RedHat Linux 7.2, JBoss 3.2.1, J2SDK 1.4.1_02, PostgreSQL 7.3.2

Description:
I have a mapping with the following set:

....
<set 
        name="fillsPublicats" 
    order-by="data desc" 
     inverse="true" 
        lazy="true" 
     cascade="all" 
       where="publicat = true" >
   <jcs-cache usage="read-write"/>
   <key column="pare_id" />
   <one-to-many class="org.ibit.foros.model.Missatge"/>
</set>
....


When the Collection gets initialized it generates the query with this where clause:

WHERE FO_MI0_.pare_id=? and FO_MI0_.publicat = FO_MI0_.true 
                                               ^^^^^^^^
ORDER BY FO_MI0_.data desc;

that throws a JDBCException

while the expected would be:

WHERE FO_MI0_.pare_id=? and FO_MI0_.publicat = true 
ORDER BY FO_MI0_.data desc;




---------------------------------------------------------------------
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-135) where attribute in many-to-many mapping applies to fields of one table

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

The following issue has been updated:

    Updater: Gavin King (mailto:ga...@in...)
       Date: Sat, 14 Jun 2003 3:57 AM
    Comment:
This is a feature request, not a bug!
    Changes:
          type changed from Bug to New Feature
          priority changed from Critical to Minor
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-135
    Summary: where attribute in many-to-many mapping applies to fields of one table
       Type: New Feature

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2

   Assignee: 
   Reporter: Hrituc Ovidiu

    Created: Fri, 13 Jun 2003 9:55 AM
    Updated: Sat, 14 Jun 2003 3:57 AM
Environment: Ms W2K Professional, Hibernate 2.0, OC4J

Description:
I wish it was possible to filter the resultset after attributes of the class we relate to; for now the where clause conditions are put on the "root" class.

For instance if we were to join A and B, the where conditions would automatically, no matter what, be stuck on A fields.




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

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Sat, 14 Jun 2003 2:54 AM

closing this now....
---------------------------------------------------------------------
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: Closed
   Priority: Minor
 Resolution: FIXED

    Project: Hibernate2
   Fix Fors:
             2.0.1
   Versions:
             2.0rc2

   Assignee: Gavin King
   Reporter: Lu Yunhai

    Created: Tue, 13 May 2003 11:40 PM
    Updated: Sat, 14 Jun 2003 2:54 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-78) JCA Connector issues

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Sat, 14 Jun 2003 2:52 AM

I have applied this patch; thanks!
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-78
    Summary: JCA Connector issues
       Type: Patch

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Hibernate2
   Fix Fors:
             2.0.1
   Versions:
             2.0rc2

   Assignee: Gavin King
   Reporter: Mike Mosiewicz

    Created: Thu, 15 May 2003 3:26 AM
    Updated: Sat, 14 Jun 2003 2:52 AM
Environment: Hibernate2 (CVS), JDK 1.4.1, Linux

Description:
I've noticed several issues probably related to things that are not really deeply tested in container managed environment.

I haven't really resolved yet, why sometimes I have this:

2003-05-15 10:05:57,928 INFO  [org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener] Unregistered handle that was not registered! net.sf.hibernate.jca.JCASessionImpl@154bd83 for managedConnection: net.sf.hibernate.jca.ManagedConnectionImpl@1d09ed4

But in such case - JCA breaks further, so there's a small patch:


---------------------------------------------------------------------
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-135) where attribute in many-to-many mapping applies to fields of one table

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-135
    Summary: where attribute in many-to-many mapping applies to fields of one table
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: Hibernate2

   Assignee: 
   Reporter: Hrituc Ovidiu

    Created: Fri, 13 Jun 2003 9:55 AM
    Updated: Fri, 13 Jun 2003 9:55 AM
Environment: Ms W2K Professional, Hibernate 2.0, OC4J

Description:
I wish it was possible to filter the resultset after attributes of the class we relate to; for now the where clause conditions are put on the "root" class.

For instance if we were to join A and B, the where conditions would automatically, no matter what, be stuck on A fields.




---------------------------------------------------------------------
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-64) hibernate*.jar should not contains hibernate-service.xml (example)

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Fri, 13 Jun 2003 8:54 AM

Okay, I did this
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-64
    Summary: hibernate*.jar should not contains hibernate-service.xml (example)
       Type: Patch

     Status: Closed
   Priority: Trivial
 Resolution: FIXED

    Project: Hibernate2
   Fix Fors:
             2.0.1
   Versions:
             2.0rc2

   Assignee: Gavin King
   Reporter: Mike Mosiewicz

    Created: Wed, 7 May 2003 6:31 AM
    Updated: Fri, 13 Jun 2003 8:54 AM

Description:
Index: build.xml
===================================================================
RCS file: /cvsroot/hibernate/Hibernate2/build.xml,v
retrieving revision 1.14
diff -u -r1.14 build.xml
--- build.xml	31 Mar 2003 06:45:12 -0000	1.14
+++ build.xml	7 May 2003 11:28:43 -0000
@@ -60,7 +60,8 @@
         <exclude name="**/*.properties"/>
         <exclude name="**/*.ccf"/>
         <exclude name="**/*.cfg.xml"/>
-        <exclude name="META-INF/ra.xml"/>        
+        <exclude name="META-INF/ra.xml"/>
+        <exclude name="net/sf/hibernate/jca/hibernate-service.xml"/>        
     </patternset>
 
     <patternset id="refdoc.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-72) Proxool Connection Provider

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Fri, 13 Jun 2003 7:53 AM

I have added this stuff to Hibernate2 CVS. (with some minor changes)
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-72
    Summary: Proxool Connection Provider
       Type: Patch

     Status: Closed
   Priority: Minor
 Resolution: FIXED

    Project: Hibernate2
   Fix Fors:
             2.0.1

   Assignee: Gavin King
   Reporter: Martin Crawford

    Created: Tue, 13 May 2003 12:09 PM
    Updated: Fri, 13 Jun 2003 7:53 AM

Description:
This patch adds a Proxool Connection Provider for Hibernate. The Connection Provider implementation is really a simple wrapper that makes using Proxool easier, and more "integrated" with Hibernate. 

Two nicesties exist: 

- Closing the Proxool pool when Hibernate closes the SessionFactory. 

- External confiuration via a JAXP XML file or properties file.

- Ability to hook into an existing Proxool managed Connection pool (in a servlet environment for example)

Requirements:

- proxool.jar, as of this posting the latest release is 7.2 available from http://proxool.sf.net/

Patch:

- A new class ProxoolConnectionProvider.java
- Modifications to Environment.java, ConnectionProviderFactory.java, hibernate.properties





---------------------------------------------------------------------
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-134) the "where" attribute in collection mapping generates incorrect sql

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

The following comment has been added to this issue:

     Author: Antoni Reus
    Created: Fri, 13 Jun 2003 6:58 AM
       Body:
I just noticed that changing
   .... where="publicats = true" ...
for:
  ... where="publicats = 'Y'" ...
works as expected

so I think the problem is that the parser of the where attribute doesn't recognize the token "true" as a value.


(excuse-me for my poor english)
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-134
    Summary: the "where" attribute in collection mapping generates incorrect sql
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: 
   Reporter: Antoni Reus

    Created: Fri, 13 Jun 2003 6:47 AM
    Updated: Fri, 13 Jun 2003 6:47 AM
Environment: RedHat Linux 7.2, JBoss 3.2.1, J2SDK 1.4.1_02, PostgreSQL 7.3.2

Description:
I have a mapping with the following set:

....
<set 
        name="fillsPublicats" 
    order-by="data desc" 
     inverse="true" 
        lazy="true" 
     cascade="all" 
       where="publicat = true" >
   <jcs-cache usage="read-write"/>
   <key column="pare_id" />
   <one-to-many class="org.ibit.foros.model.Missatge"/>
</set>
....


When the Collection gets initialized it generates the query with this where clause:

WHERE FO_MI0_.pare_id=? and FO_MI0_.publicat = FO_MI0_.true 
                                               ^^^^^^^^
ORDER BY FO_MI0_.data desc;

that throws a JDBCException

while the expected would be:

WHERE FO_MI0_.pare_id=? and FO_MI0_.publicat = true 
ORDER BY FO_MI0_.data desc;




---------------------------------------------------------------------
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-134) the "where" attribute in collection mapping generates incorrect sql

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

Message:

  A new issue has been created in JIRA.

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-134
    Summary: the "where" attribute in collection mapping generates incorrect sql
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: 
   Reporter: Antoni Reus

    Created: Fri, 13 Jun 2003 6:47 AM
    Updated: Fri, 13 Jun 2003 6:47 AM
Environment: RedHat Linux 7.2, JBoss 3.2.1, J2SDK 1.4.1_02, PostgreSQL 7.3.2

Description:
I have a mapping with the following set:

....
<set 
        name="fillsPublicats" 
    order-by="data desc" 
     inverse="true" 
        lazy="true" 
     cascade="all" 
       where="publicat = true" >
   <jcs-cache usage="read-write"/>
   <key column="pare_id" />
   <one-to-many class="org.ibit.foros.model.Missatge"/>
</set>
....


When the Collection gets initialized it generates the query with this where clause:

WHERE FO_MI0_.pare_id=? and FO_MI0_.publicat = FO_MI0_.true 
                                               ^^^^^^^^
ORDER BY FO_MI0_.data desc;

that throws a JDBCException

while the expected would be:

WHERE FO_MI0_.pare_id=? and FO_MI0_.publicat = true 
ORDER BY FO_MI0_.data desc;




---------------------------------------------------------------------
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-130) "where" attribute of collections mapping translates into SQL badly

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Fri, 13 Jun 2003 5:09 AM

Yep, missing a toLowerCase()

Fixed in CVS. A workaround is to use lowercase SQL.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-130
    Summary: "where" attribute of collections mapping translates into SQL badly
       Type: Bug

     Status: Closed
   Priority: Critical
 Resolution: FIXED

    Project: Hibernate2
   Fix Fors:
             2.0.1
   Versions:
             2.0 final

   Assignee: Gavin King
   Reporter: Hrituc Ovidiu

    Created: Wed, 11 Jun 2003 8:52 AM
    Updated: Fri, 13 Jun 2003 5:09 AM
Environment: Win 2K Professional, Hib used under OC4J with SQL Server 2000

Description:
I added this filter on collection to get a subset of the original colection: "DATA_FIN IS NULL"
and Hibernate put this to the end of the SQL statement:
... and Perso0_.DATA_FIN Perso0_.IS Perso0_.NULL
I guess that if the SQL islands inside HQL will be solved maybe this will go away 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-133) Cascading a many-to-one child object in MYSQL

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Fri, 13 Jun 2003 4:26 AM

As described in the documentation, you must use unsaved-value="0" for a primitive id type.

The User Forum is the correct place for these kinds of issues.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-133
    Summary: Cascading a many-to-one child object in MYSQL
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: Gavin King
   Reporter: Todd Nine

    Created: Thu, 12 Jun 2003 1:38 PM
    Updated: Fri, 13 Jun 2003 4:26 AM
Environment: Orion Application Server
MY SQL DB
Java 1.4.1_02

Description:
This is a concrete example of the Cascades.isUnsaved(Serializable id) error.

We have 2 class Customer and Address, Address is a child of Customer.

if we have the following in the Customer.hbm.xml file:

<many-to-one name="address" class="com.sigma.webtools.modal.services.facades.facadechildren.Address" cascade="all"/>

and Address.hbm.xml is the following

<hibernate-mapping>
    <class name="com.sigma.webtools.modal.services.facades.facadechildren.Address" table="WTS_ADDRESS">
        <id name="id"  type="long">
            <generator class="native"/>
        </id>
        <property name="firstName"  type="string"/>
        <property name="lastName"  type="string"/>
        <property name="address1"  type="string"/>
        <property name="address2"  type="string"/>
        <property name="address3"  type="string"/>
        <property name="city"  type="string"/>
        <property name="state"  type="string"/>
        <property name="zip"  type="string"/>
        <property name="contact"  type="string"/>
        <property name="deliveryType"  type="string"/>
        <property name="addressType"  type="string"/>

    </class>
</hibernate-mapping>

when the generator is "native" and the variable type is a primitive numberic, the following will return 0;

//line 1210 in file net.sf.hibernate.impl.SessionImpl
Serializable id = persister.getIdentifier(object); 

Therefore, when the following is called 
if ( persister.isUnsaved(id))

The following evaluates false

return id==null;

The child object will not be saved because an update is called instead of a save.




---------------------------------------------------------------------
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-133) Cascading a many-to-one child object in MYSQL

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-133
    Summary: Cascading a many-to-one child object in MYSQL
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: 
   Reporter: Todd Nine

    Created: Thu, 12 Jun 2003 1:38 PM
    Updated: Thu, 12 Jun 2003 1:38 PM
Environment: Orion Application Server
MY SQL DB
Java 1.4.1_02

Description:
This is a concrete example of the Cascades.isUnsaved(Serializable id) error.

We have 2 class Customer and Address, Address is a child of Customer.

if we have the following in the Customer.hbm.xml file:

<many-to-one name="address" class="com.sigma.webtools.modal.services.facades.facadechildren.Address" cascade="all"/>

and Address.hbm.xml is the following

<hibernate-mapping>
    <class name="com.sigma.webtools.modal.services.facades.facadechildren.Address" table="WTS_ADDRESS">
        <id name="id"  type="long">
            <generator class="native"/>
        </id>
        <property name="firstName"  type="string"/>
        <property name="lastName"  type="string"/>
        <property name="address1"  type="string"/>
        <property name="address2"  type="string"/>
        <property name="address3"  type="string"/>
        <property name="city"  type="string"/>
        <property name="state"  type="string"/>
        <property name="zip"  type="string"/>
        <property name="contact"  type="string"/>
        <property name="deliveryType"  type="string"/>
        <property name="addressType"  type="string"/>

    </class>
</hibernate-mapping>

when the generator is "native" and the variable type is a primitive numberic, the following will return 0;

//line 1210 in file net.sf.hibernate.impl.SessionImpl
Serializable id = persister.getIdentifier(object); 

Therefore, when the following is called 
if ( persister.isUnsaved(id))

The following evaluates false

return id==null;

The child object will not be saved because an update is called instead of a save.




---------------------------------------------------------------------
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-43) Auto db build

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

The following comment has been added to this issue:

     Author: Travis
    Created: Thu, 12 Jun 2003 11:23 AM
       Body:
Noticed it doesn't say anything about crossdb on here either.  This will require crossdb.jar from www.crossdb.com

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-43
    Summary: Auto db build
       Type: Patch

     Status: Assigned
   Priority: Major

    Project: Hibernate2

   Assignee: Gavin King
   Reporter: Max Rydahl Andersen

    Created: Sat, 3 May 2003 10:27 AM
    Updated: Mon, 19 May 2003 10:45 PM

Description:
Auto db build
small change in Configuation and new class. 

Turned on by the following property: 

hibernate.autobuilddb true 

Small change required in Configuration: replace 
buildSessionFactory with this one: 

public SessionFactory buildSessionFactory() throws 
HibernateException { 
secondPassCompile(); 
Environment.verifyProperties 
(properties); 
Properties copy = new Properties 
(); 
copy.putAll(properties); 
SessionFactoryImpl sessImpl = 
new SessionFactoryImpl(this, copy, interceptor); 

// build db if autobuild set 
String autobuilddb = (String) properties.get 
("hibernate.autobuilddb"); 
if(autobuilddb != null && 
autobuilddb.equalsIgnoreCase("true")){ 
DbBuilder.autoBuild(this, sessImpl); 
} 

return sessImpl; 
} 

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


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/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-132) Query by Criteria enhancement

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-132
    Summary: Query by Criteria enhancement
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
   Versions:
             2.1

   Assignee: 
   Reporter: Grzegorz Mucha

    Created: Thu, 12 Jun 2003 3:59 AM
    Updated: Thu, 12 Jun 2003 3:59 AM

Description:
Is there a plan to add some extensions to Criteria API? Since there is now FETCH support in Criteria, a nice thing would be to allow users sorting the criteria returned not only by class properties, but the associated classes' properties as well.

example:

class Task {
  User user;
........

}

Criteria crit=session.createCriteria(Task.class);
crit.addOrder(Order.asc("user.lastName");

I know it can be done in java,by applying own sorters for the returned list, though I'd prefer a single step process


---------------------------------------------------------------------
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-131) Select...Limit syntax changed from PostgreSQL 6.5 to 7.0

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-131
    Summary: Select...Limit syntax changed from PostgreSQL 6.5 to 7.0
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0rc2
             2.1
             2.0 final
             2.0.1

   Assignee: 
   Reporter: Jesse McLaughlin

    Created: Thu, 12 Jun 2003 12:16 AM
    Updated: Thu, 12 Jun 2003 12:16 AM

Description:
Using the

Query.setMaxResults(); 

method with the PostgreSQL dialect while using PostgreSQL version >= 7.0 causes the following error: 

14:20:31,140 ERROR [JDBCExceptionReporter] Could not execute query 
java.sql.SQLException: ERROR: LIMIT #,# syntax not supported. 
Use separate LIMIT and OFFSET clauses. 

PostgreSQLDialect.java reads: 

public String getLimitString(String sql) { 
  StringBuffer pagingSelect = new StringBuffer(100); 
  pagingSelect.append(sql); 
  pagingSelect.append(" limit ?, ?"); 
  return pagingSelect.toString(); 
} 

However, the Select..Limit syntax has changed from PostgreSQL 7.0, refer:

SELECT

PostgreSQL 6.5 Synopsis

http://www.postgresql.org/docs/view.php?version=6.5&idoc=1&file=sql-select.htm

SELECT [ALL|DISTINCT [ON column] ]
    expression [ AS
   name ] [, ...]
    [ INTO [TEMP] [TABLE] new_table ]
    [ FROM table
   [alias ] [, ...] ]
    [ WHERE condition ]
    [ GROUP BY column [, ...] ]
    [ HAVING condition [, ...] ]
    [ { UNION [ALL] | INTERSECT | EXCEPT } select ]
    [ ORDER BY column [ ASC | DESC ] [, ...] ]
    [ FOR UPDATE [OF class_name...]]
    [ LIMIT count [OFFSET|, count]]

Compare with:

PostgreSQL 7.0 Synopsis

http://www.postgresql.org/docs/view.php?version=7.0&idoc=1&file=sql-select.htm

SELECT [ ALL | DISTINCT [ ON ( expression [, ...] ) ] ]
    expression [ AS name ] [, ...]
    [ INTO [ TEMPORARY | TEMP ] [ TABLE ] new_table ]
    [ FROM table [ alias ] [, ...] ]
    [ WHERE condition ]
    [ GROUP BY column [, ...] ]
    [ HAVING condition [, ...] ]
    [ { UNION [ ALL ] | INTERSECT | EXCEPT } select ]
    [ ORDER BY column [ ASC | DESC | USING operator ] [, ...] ]
    [ FOR UPDATE [ OF class_name [, ...] ] ]
    LIMIT { count | ALL } [ { OFFSET | , } start ]

The Hibernate PostgreSQL dialect should be updated (or a new one created) to reflect this change.



---------------------------------------------------------------------
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-130) "where" attribute of collections mapping translates into SQL badly

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

Message:

   The following issue has been re-assigned.

   Assignee: Gavin King (mailto:ga...@in...)
   Assigner: Gavin King (mailto:ga...@in...)
       Date: Wed, 11 Jun 2003 6:44 PM
    Comment:
Hah! I knew that code was dodgy....

I will fix this (its pretty easy)
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-130
    Summary: "where" attribute of collections mapping translates into SQL badly
       Type: Bug

     Status: Assigned
   Priority: Critical

    Project: Hibernate2
   Versions:
             2.0 final

   Assignee: Gavin King
   Reporter: Hrituc Ovidiu

    Created: Wed, 11 Jun 2003 8:52 AM
    Updated: Wed, 11 Jun 2003 6:44 PM
Environment: Win 2K Professional, Hib used under OC4J with SQL Server 2000

Description:
I added this filter on collection to get a subset of the original colection: "DATA_FIN IS NULL"
and Hibernate put this to the end of the SQL statement:
... and Perso0_.DATA_FIN Perso0_.IS Perso0_.NULL
I guess that if the SQL islands inside HQL will be solved maybe this will go away 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-130) "where" attribute of collections mapping translates into SQL badly

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-130
    Summary: "where" attribute of collections mapping translates into SQL badly
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: Hibernate2
   Versions:
             2.0 final

   Assignee: 
   Reporter: Hrituc Ovidiu

    Created: Wed, 11 Jun 2003 8:52 AM
    Updated: Wed, 11 Jun 2003 8:52 AM
Environment: Win 2K Professional, Hib used under OC4J with SQL Server 2000

Description:
I added this filter on collection to get a subset of the original colection: "DATA_FIN IS NULL"
and Hibernate put this to the end of the SQL statement:
... and Perso0_.DATA_FIN Perso0_.IS Perso0_.NULL
I guess that if the SQL islands inside HQL will be solved maybe this will go away 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] Updated: (HB-123) Apply distinctness to HQL fetch of collection

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

The following issue has been updated:

    Updater: Gavin King (mailto:ga...@in...)
       Date: Wed, 11 Jun 2003 8:19 AM
    Comment:
There are certain problems with this, but I am thinking about them.
    Changes:
          type changed from Task to Improvement
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

     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: Wed, 11 Jun 2003 8:19 AM

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] Closed: (HB-129) Query.iterate() using setFirstResult and setMaxResult

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

Message:

   The following issue has been closed.

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

fixed now, with a testcase - this also affected postgres
---------------------------------------------------------------------
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: Closed
   Priority: Major
 Resolution: FIXED

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

   Assignee: Gavin King
   Reporter: David Howe

    Created: Wed, 11 Jun 2003 5:49 AM
    Updated: Wed, 11 Jun 2003 8:15 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] Updated: (HB-75) Some javadoc problems in build.xml

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

The following issue has been updated:

    Updater: Gavin King (mailto:ga...@in...)
       Date: Wed, 11 Jun 2003 8:12 AM
    Comment:
Christian made "jar" the default Ant target.
    Changes:
          priority changed from Major to Minor
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

    Project: Hibernate2
   Versions:
             2.0rc2

   Assignee: Christian Bauer
   Reporter: Lu Yunhai

    Created: Tue, 13 May 2003 11:40 PM
    Updated: Wed, 11 Jun 2003 8:12 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] Updated: (HB-14) Problem in ReverseGenerator (sequence generator class)

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

The following issue has been updated:

    Updater: Gavin King (mailto:ga...@in...)
       Date: Wed, 11 Jun 2003 8:10 AM
    Comment:
Haslf of this issue was fixed. Are we maintaining this tool?
    Changes:
          priority changed from Major to Minor
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

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


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

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
   Versions:
             2.0rc2

   Assignee: 
   Reporter: Max Rydahl Andersen

    Created: Sat, 3 May 2003 10:03 AM
    Updated: Wed, 11 Jun 2003 8:10 AM

Description:
Problem in sequence generator class.

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

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

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

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


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/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-101) xtags.xml missing entry for joined subclass [XDoclet]

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

The following issue has been updated:

    Updater: Gavin King (mailto:ga...@in...)
       Date: Wed, 11 Jun 2003 8:08 AM
    Comment:
Thanks. This should really have been submitted to XDoclet JIRA, but I'll take care of it anyway....
    Changes:
          type changed from Bug to Patch
          summary changed from xtags.xml missing entry for joined subclass to xtags.xml missing entry for joined subclass [XDoclet]
          priority changed from Major to Minor
          Component changed from toolset to 
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-101
    Summary: xtags.xml missing entry for joined subclass [XDoclet]
       Type: Patch

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
   Versions:
             2.0rc2

   Assignee: 
   Reporter: Low Heng Sin

    Created: Sun, 25 May 2003 5:32 AM
    Updated: Wed, 11 Jun 2003 8:08 AM

Description:
XDoclet hibernate module's xtags.xml doesn't contains entry for the hibernate.joined-subclass and hibernate.joined-subclass-key although the xdt is there.



---------------------------------------------------------------------
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-16) Query generation bug

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

Message:

   The following issue has been closed.

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

I don't believe this issue affects Hibernate2. If it _does_, please reopen. (I think there is even a test for this.)
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-16
    Summary:  Query generation bug
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Hibernate2
   Fix Fors:
             2.0 final

   Assignee: Gavin King
   Reporter: Max Rydahl Andersen

    Created: Sat, 3 May 2003 10:05 AM
    Updated: Wed, 11 Jun 2003 8:05 AM

Description:
Query generation bug
Persistent class "Inquiry" contains property 
"idCustomerInquiry". 

Query: 

"select max(iq.idCustomerInquiry) 
from Inquiry as iq 
where iq.customer.id=?" 

is translated into wrong: 

"select 
max(iq.idCustomercom.qbizm.ik.core.impl.persistobj.Inquiry) 
from Inquiry as iq 
where iq.customer.id=?" 

instead of correct: 

"select max(iq.idCustomerInquiry) 
from com.qbizm.ik.core.impl.persistobj.Inquiry as iq 
where iq.customer.id=?" 


Problem is only if property name contains class name as its 
substring. When property "idCustomerInquiry" is renamed 
into "idCustomerInq", query translation is OK. 

Jan Dundacek 

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

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