hibernate-issues — Hibernate JIRA Notifications

[Hibernate-issues] [Hibernate-JIRA] Created: (HBI-20) Compatibility Documentation - missing details on problem with Weblogic Support

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

Message:

  A new issue has been created in JIRA.

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HBI-20
    Summary: Compatibility Documentation - missing details on problem with Weblogic Support
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Hibernate 1.2

   Assignee: 
   Reporter: Nick Minutello

    Created: Wed, 7 Jan 2004 12:57 PM
    Updated: Wed, 7 Jan 2004 12:57 PM

Description:

Regarding http://www.hibernate.org/34.html

Are there some more details on the problem with Hibernate on Weblogic?

I find no mention of this anywhere else in the FAQ, Jira or Wiki - perhaps I missed something?

Is this it still current?




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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Updated: (HB-580) Undo deprecation of Configuration.addJar(String)

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

The following issue has been updated:

    Updater: Max Rydahl Andersen (mailto:xa...@xa...)
       Date: Wed, 7 Jan 2004 12:11 PM
    Changes:
             priority changed from Critical
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-580
    Summary: Undo deprecation of Configuration.addJar(String)
       Type: Improvement

     Status: Reopened
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1.1

   Assignee: 
   Reporter: tom quas

    Created: Fri, 26 Dec 2003 3:51 PM
    Updated: Wed, 7 Jan 2004 12:11 PM
Environment: API

Description:
I just realized that Configuration.addJar( String filename ) has been deprecated. I regularly use it to load mappings from the classpath.
Could you please leave it in for convenience?


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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Reopened: (HB-580) Undo deprecation of Configuration.addJar(String)

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

Message:

   The following issue has been reopened.

   Reopener: Max Rydahl Andersen
       Date: Wed, 7 Jan 2004 12:10 PM

no definite answer - yet...but downgrading the priority since the method is still there.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-580
    Summary: Undo deprecation of Configuration.addJar(String)
       Type: Improvement

     Status: Reopened
   Priority: Critical

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1.1

   Assignee: 
   Reporter: tom quas

    Created: Fri, 26 Dec 2003 3:51 PM
    Updated: Wed, 7 Jan 2004 12:10 PM
Environment: API

Description:
I just realized that Configuration.addJar( String filename ) has been deprecated. I regularly use it to load mappings from the classpath.
Could you please leave it in for convenience?


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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-485) DYNAMIC_PREPARE and @@identity

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

The following comment has been added to this issue:

     Author: YR
    Created: Wed, 7 Jan 2004 4:30 AM
       Body:
Hi,

I have asked a similar question in the Hibernate forum :
http://forum.hibernate.org/viewtopic.php?t=926010&highlight=identity+jconnect

This is a major problem. If it can't be solved by adding a sybase-specific handling of identity keys, then, you have to document it :
- or Sybase Identity feature is not supported by Hibernate (please be clear on this point)
- or Hibernate doesn't support precompilation of statements AND the use of Sybase Identity keys.

Thanks for your feedback and long life to Hibernate !


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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-485
    Summary: DYNAMIC_PREPARE and @@identity
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: Richard Scranton

    Created: Thu, 20 Nov 2003 1:22 PM
    Updated: Wed, 7 Jan 2004 4:30 AM

Description:
Using the Sybase jConnect jdbc driver version 4.5 or 5.5, if the connection property DYNAMIC_PREPARE is set to "true", "select @@identity" will always return a "0".  This is an artifact of the Sybase implementation of prepared statements.  Statements compiled at the server become stored procedures marked by the "DYN" token, and appear named as dyn100, dyn101, etc in the
captured TDS stream.  The value of @@identity is lost at the end of a procedure, so a sequence of prepared statements like:

insert into Yadda (val1,val2) values ( 1,2 )
select @@identity

will execute as expected when DYNAMIC_PREPARE is false.  If it is set to true, the statement "select @@identity" will return "0".  Sybase suggests something like this workaround to get the expected behavior:

String nl=System.getProperty("line.separator");
PreparedStaement ps=conn.prepareStatement(
        "insert into Yadd (val1,val2) values ( 1,2 )"
        + nl
        + "select @@identity");

Leaving DYNAMIC_PREPARE set false gives away throughput if the queries being sent and parsed are of significant size.  TDS dumps show they are being sent and parsed with each invocation.  Setting DYNAMIC_PREPARE to true allows reuse of the parsed queries.



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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Updated: (HB-609) replicate() with joined-subclass

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

The following issue has been updated:

    Updater: Greg Barton (mailto:gre...@ya...)
       Date: Tue, 6 Jan 2004 12:55 PM
    Comment:
Code example
    Changes:
             Attachment changed to code.tar.gz
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-609
    Summary: replicate() with joined-subclass
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.1.1

   Assignee: 
   Reporter: Greg Barton

    Created: Tue, 6 Jan 2004 12:53 PM
    Updated: Tue, 6 Jan 2004 12:55 PM
Environment: Hibernate 2.1.1, Postgres 7.4

Description:
Attempt to call Session.replicate() on a persistent object mapped using joined-subclass.  A net.sf.hibernate.JDBCException is thrown because HIbernate attempts to access the "version" column in the underlying table.  That column is only present in the superclass table of the class being being replicated.

Exception generated:
net.sf.hibernate.JDBCException: could not retrieve version: [***id of object***]
        at net.sf.hibernate.persister.AbstractEntityPersister.getCurrentVersion(AbstractEntityPersister.java:1141)
        at net.sf.hibernate.impl.SessionImpl.replicate(SessionImpl.java:3698)
        at.... 


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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Created: (HB-609) replicate() with joined-subclass

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-609
    Summary: replicate() with joined-subclass
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.1.1

   Assignee: 
   Reporter: Greg Barton

    Created: Tue, 6 Jan 2004 12:53 PM
    Updated: Tue, 6 Jan 2004 12:53 PM
Environment: Hibernate 2.1.1, Postgres 7.4

Description:
Attempt to call Session.replicate() on a persistent object mapped using joined-subclass.  A net.sf.hibernate.JDBCException is thrown because HIbernate attempts to access the "version" column in the underlying table.  That column is only present in the superclass table of the class being being replicated.

Exception generated:
net.sf.hibernate.JDBCException: could not retrieve version: [***id of object***]
        at net.sf.hibernate.persister.AbstractEntityPersister.getCurrentVersion(AbstractEntityPersister.java:1141)
        at net.sf.hibernate.impl.SessionImpl.replicate(SessionImpl.java:3698)
        at.... 


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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-592) SessionFactory goes stale after database restart

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

The following comment has been added to this issue:

     Author: Brian Topping
    Created: Tue, 6 Jan 2004 12:21 PM
       Body:
Sure, I guess that's what matters! ;)
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-592
    Summary: SessionFactory goes stale after database restart
       Type: Bug

     Status: Closed
   Priority: Critical
 Resolution: REJECTED

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1.1

   Assignee: 
   Reporter: Brian Topping

    Created: Wed, 31 Dec 2003 1:46 PM
    Updated: Tue, 6 Jan 2004 12:21 PM

Description:
It seems impractical to recover a Hibernate SessionFactory from a database restart.  Additionally, Hibernate is kicking back a totally bogus stack trace, one has very little connection to the code that is executed.  (I'll attach that as soon as I can get a copy of one... I restarted the server and didn't save it...)

The problem that I seeing in this particular app is that I am using local configuration objects, not the JBoss service MBean.  I cache the SessionFactory calling Config.buildSessionFactory(), but if the database is restarted, it starts blowing these crazy exceptions.

I'm also looking at this from an architectural perspective.  Confg.buildSessionFactory() is very expensive.  So I can't call it all the time.  I wouldn't mind calling it if I could sense when it needed to be called (i.e. after the database connection is lost), but the exception does not happen until session.find() is called.  Calling SessionFactory.openSession() succeeds just fine.  If the logic required could be wrapped in a SessionFactory facade and the Session that is returned can be validated before it is used by the client, that would not be a problem, and I would welcome a suggestion for a lightweight query or connection validation routine that could be used.  

Should SessionFactory.openSession() be validating the connection before returning it?

Failing a good way to make sure that the Session that is returned is good, I am going to have to write global exception catcher that knows how to determine that the SessionFactory is stale, then kill the cache so that it is reloaded on the next time through.  Color me lazy, but that seems a bit excessive.  

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

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

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-596) AbstractQueryImpl.setParameterList may have 0 length list

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

The following comment has been added to this issue:

     Author: Max Rydahl Andersen
    Created: Tue, 6 Jan 2004 4:54 AM
       Body:
i looked at it - but could not come up with a good behavior if it is null....should it throw a better excpetion, or ?
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-596
    Summary: AbstractQueryImpl.setParameterList may have 0 length list
       Type: Bug

     Status: Open
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1

   Assignee: Max Rydahl Andersen
   Reporter: Chris Mercer

    Created: Fri, 2 Jan 2004 12:57 PM
    Updated: Tue, 6 Jan 2004 4:54 AM
Environment: Hibernate 2.1.1, mysql

Description:
Here is the source code for the method

public Query setParameterList(String name, Collection vals) throws HibernateException {
		setParameterList(name, vals, guessType( vals.iterator().next() ) );
		return this;
	}

The problems comes in when the vals collection is size 0.  The vals.iterator().next() will fail with a NoSuchElementException. 
 



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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-414) Informix dialect creates syntax errors in IDS 9.4

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

The following comment has been added to this issue:

     Author: Finn McCann
    Created: Tue, 6 Jan 2004 2:54 AM
       Body:
Hi Max,

INT8 is a BIG INTEGER i.e. 2^63.

SERIAL8, when used in a PRIMARY KEY context, is a unique ID generator based on INT8. 

The SERIAL8 data type stores a sequential integer assigned automatically by the database server when a new row is inserted. It behaves like the SERIAL data type, but with a larger range.

I would assume that people would want to use INT8 for big integer fields and SERIAL8 for ID fields?
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-414
    Summary: Informix dialect creates syntax errors in IDS 9.4
       Type: Bug

     Status: Open
   Priority: Major

    Project: Hibernate2
   Versions:
             2.0.2

   Assignee: Max Rydahl Andersen
   Reporter: Finn McCann

    Created: Tue, 21 Oct 2003 11:01 AM
    Updated: Tue, 6 Jan 2004 2:54 AM
Environment: Hibernate2 on JDK1.4 on Win2000, talking via Informix JDBC 2.21.JC5 driver to Informix IDS 9.4 on another Windows 2000 box.

Description:
Having tested Informix dialect in Hibernate2 against Informix IDS v9.4, we found a couple of issues: 

1.  Serial ids:

<id name="id" column="ID" length="32" unsaved-value="null">
   <generator class="uuid.hex"/>
</id>

creates a data type:

INT8 SERIAL   

instead of:

SERIAL8

The "INT8 SERIAL" causes a syntax error in IDS 9.4.

2. Foreign Key constraint names:

<set name="upliftRates" lazy="true" cascade="all" order-by="EFFECTIVE_DATE desc">
        <key column="NETWORK_ID" length="32"/>
        <one-to-many class="com.capetechnologies.multinet.domain.UpliftRate"/>
</set>

creates this ALTER TABLE statement:

alter table MULTINET_TAX_RATES add constraint FKE1700D046924EC foreign key (NETWORK_ID) references MULTINET_NETWORK

instead of:

alter table MULTINET_TAX_RATES add constraint foreign key (NETWORK_ID) references MULTINET_NETWORK constraint FKE1700D046924EC

Having "CONSTRAINT <constraint name>" within the statement instead of at the end causes a syntax error.

This also applies to adding UNIQUE CONSTRAINTs.



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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Assigned: (HB-594) Typo in treecache.xml - LockingLevel should be IsolationLevel

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

Message:

   The following issue has been re-assigned.

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-594
    Summary: Typo in treecache.xml - LockingLevel should be IsolationLevel
       Type: Bug

     Status: Open
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1.1

   Assignee: Gavin King
   Reporter: Lari Hotari

    Created: Fri, 2 Jan 2004 2:40 AM
    Updated: Tue, 6 Jan 2004 12:42 AM
Environment: 2.1.1, any

Description:
There is a typo in treecache.xml - LockingLevel should be IsolationLevel.

<attribute name="LockingLevel">REPEATABLE_READ</attribute>

should be:

<attribute name="IsolationLevel">REPEATABLE_READ</attribute>



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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-592) SessionFactory goes stale after database restart

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Tue, 6 Jan 2004 12:42 AM

Not quite sure what you mean but, anyway, I'm happy with current behavior.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-592
    Summary: SessionFactory goes stale after database restart
       Type: Bug

     Status: Closed
   Priority: Critical
 Resolution: REJECTED

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1.1

   Assignee: 
   Reporter: Brian Topping

    Created: Wed, 31 Dec 2003 1:46 PM
    Updated: Tue, 6 Jan 2004 12:42 AM

Description:
It seems impractical to recover a Hibernate SessionFactory from a database restart.  Additionally, Hibernate is kicking back a totally bogus stack trace, one has very little connection to the code that is executed.  (I'll attach that as soon as I can get a copy of one... I restarted the server and didn't save it...)

The problem that I seeing in this particular app is that I am using local configuration objects, not the JBoss service MBean.  I cache the SessionFactory calling Config.buildSessionFactory(), but if the database is restarted, it starts blowing these crazy exceptions.

I'm also looking at this from an architectural perspective.  Confg.buildSessionFactory() is very expensive.  So I can't call it all the time.  I wouldn't mind calling it if I could sense when it needed to be called (i.e. after the database connection is lost), but the exception does not happen until session.find() is called.  Calling SessionFactory.openSession() succeeds just fine.  If the logic required could be wrapped in a SessionFactory facade and the Session that is returned can be validated before it is used by the client, that would not be a problem, and I would welcome a suggestion for a lightweight query or connection validation routine that could be used.  

Should SessionFactory.openSession() be validating the connection before returning it?

Failing a good way to make sure that the Session that is returned is good, I am going to have to write global exception catcher that knows how to determine that the SessionFactory is stale, then kill the cache so that it is reloaded on the next time through.  Color me lazy, but that seems a bit excessive.  

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

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

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-593) Having clause couldn't get the alias in it

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Tue, 6 Jan 2004 12:41 AM

This looks like something for the user forum. Not a bug in Hibernate.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-593
    Summary: Having clause couldn't get the alias in it
       Type: Bug

     Status: Closed
   Priority: Critical
 Resolution: REJECTED

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1

   Assignee: 
   Reporter: simon xi

    Created: Thu, 1 Jan 2004 6:43 PM
    Updated: Tue, 6 Jan 2004 12:41 AM
Environment: mysql database

Description:
The hibernate generate the attribute of field, but in Having clause, it use the true field name, so the database will say that there is no this field in database.

warning : SQL Error: 1054, SQLState: S0022
2004-1-2 8:37:20 net.sf.hibernate.util.JDBCExceptionReporter logExceptions
Hibernate: select forum0_.id as id0_, category1_.id as id1_, message3_.id as id2_, forum0_.name as name0_, forum0_.priority as priority0_, category1_.name as name1_, category1_.priority as priority1_, category1_.description as descript4_1_, category1_.moderator as moderator1_, category1_.forum as forum1_, message3_.toc as toc2_, message3_.text as text2_, message3_.poster as poster2_, message3_.topic as topic2_, message3_.parent as parent2_, forum0_.id as x0_0_, category1_.id as x1_0_, count(distinct topic2_.id) as x2_0_, count(distinct message3_.id) as x3_0_, message3_.id as x4_0_ from Forum forum0_, Category category1_, Topic topic2_, Message message3_ where (message3_.topic=topic2_.id )and(topic2_.category=category1_.id )and(category1_.forum=forum0_.id ) group by  topic2_.category , category1_.forum having (message3_.toc=max(message3_.toc)) order by  forum0_.priority desc , category1_.priority desc , topic2_.toc desc

fatal: Column not found,  message from server: "Unknown column 'message3_.toc' in 'having clause'"
2004-1-2 8:37:20 net.sf.hibernate.JDBCException <init>

fatal: Could not execute query
java.sql.SQLException: Column not found,  message from server: "Unknown column 'message3_.toc' in 'having clause'"



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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-599) delete all entities of persistent class

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Tue, 6 Jan 2004 12:39 AM

I am rethinking the concept of delete-by-query, and something nice might be possible in 2.2, but it won't look like this.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-599
    Summary: delete all entities of persistent class
       Type: New Feature

     Status: Closed
   Priority: Minor
 Resolution: REJECTED

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: Alexey Kaigorodov

    Created: Mon, 5 Jan 2004 5:29 AM
    Updated: Tue, 6 Jan 2004 12:39 AM

Description:
I propose add method 

Session.deleteAll(Class persistentClass)

which delete all rows from entity's table, evict all entities of persistentClass from session cache and second level cache.

--
With best regards,
Alex 


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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-601) delete(Serializable pk) in session

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Tue, 6 Jan 2004 12:38 AM

Not to mention collections. This is not really possible to implement cleanly.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-601
    Summary: delete(Serializable pk) in session 
       Type: New Feature

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: belcore walter

    Created: Mon, 5 Jan 2004 8:46 AM
    Updated: Tue, 6 Jan 2004 12:38 AM

Description:
Why ther isn't a delete method like delete(Serializable pk) ? Where pk is a composite id o a primary key 

Now, if want delete a object, I should before load it e after delete. So Hibernate makes two (select and delete) sql istance. 

With my suggestion I can delete a object with this code: 

MyCompositeId pk= new MyCompositeId("ABC22",2); 

session.delete(pk); 

and Hibernate will make only a sql like:

delete from FOO where COD='ABC22' and INCREMENT=2


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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-600) hbm2java can't mapping joined-subclasses correctly which are in independent files from the file of the super class.

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

The following comment has been added to this issue:

     Author: Eileen Huan
    Created: Tue, 6 Jan 2004 12:35 AM
       Body:
All the jars can found in the "lib" package of hibernate toolset demo package.
Thanks, Max.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-600
    Summary: hbm2java can't mapping joined-subclasses correctly which are in independent files from the file of the super class.
       Type: Bug

     Status: Resolved
   Priority: Critical
 Resolution: CANNOT REPRODUCE

    Project: Hibernate2
 Components: 
             toolset
   Versions:
             2.1

   Assignee: Max Rydahl Andersen
   Reporter: Eileen Huan

    Created: Mon, 5 Jan 2004 6:16 AM
    Updated: Tue, 6 Jan 2004 12:35 AM
Environment: Apache Ant version 1.5.4 compiled on August 12 2003
Buildfile: build.xml
Detected Java version: 1.4 in: C:\j2sdk1.4.2_03\jre
Detected OS: Windows 2000

Description:
I have posted my problem on hibernate forum as "http://forum.hibernate.org/viewtopic.php?t=926802&sid=a04167043b0b8cd84c79b9d16b332a7e".



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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Assigned: (HB-607) <composite-element> does not accept <any> in it

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

Message:

   The following issue has been re-assigned.

   Assignee: Gavin King (mailto:ga...@hi...)
   Assigner: Gavin King (mailto:ga...@hi...)
       Date: Tue, 6 Jan 2004 12:20 AM
    Comment:
Interesting. Didn't expect anyone to need this.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-607
    Summary: <composite-element> does not accept <any> in it
       Type: Bug

     Status: Open
   Priority: Major

    Project: Hibernate2
   Versions:
             2.1

   Assignee: Gavin King
   Reporter: Sankara N Alwar

    Created: Mon, 5 Jan 2004 8:10 PM
    Updated: Tue, 6 Jan 2004 12:20 AM
Environment: Hibernate 2.1 Final, Oralce 8.1.7, Windows 2000

Description:
<composite-element> does not accept <any> in it. I get the following error if I add any inside <composite-element>: 

ERROR [Thread-4] 2003-12-23 23:42:18,735 - net.sf.hibernate.util.XMLHelper - Error parsing XML: XML InputStream(180) The content of element type "composite-element" must match "(parent?,(property|many-to-one|nested-composite-element)*)". 

Even I verified the dtd, it doesn't accept it. Here is my mapping: 

<set name="Persons" table="groupmembership" lazy="true" inverse="true"> 
<key column="group_id"/> 
<composite-element class="net.sf.hibernate.examples.quickstart.GroupMembership"> 
<any name="members" id-type="string" meta-type="net.sf.hibernate.examples.quickstart.GroupTypeMapper"> 
<column name="child_type"/> 
<column name="child_id"/> 
</any> 
</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/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Assigned: (HB-608) Allow criteria queries on abstract classes from table-per-concrete-class mappings

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

Message:

   The following issue has been re-assigned.

   Assignee: Gavin King (mailto:ga...@hi...)
   Assigner: Gavin King (mailto:ga...@hi...)
       Date: Tue, 6 Jan 2004 12:19 AM
    Comment:
I'll take a look at this next week.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-608
    Summary: Allow criteria queries on abstract classes from table-per-concrete-class mappings
       Type: Improvement

     Status: Open
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1.1

   Assignee: Gavin King
   Reporter: Shorn Tolley

    Created: Mon, 5 Jan 2004 11:09 PM
    Updated: Tue, 6 Jan 2004 12:19 AM
Environment: Hibernate 2.1.1, Ingres 2.6 SP2

Description:
I'm mapping a part of my domain model using the table-per-concrete-class strategy.  I need to use hibernate's "implicit polymorphism" feature to query on the abstract class in the hierarchy to return specific instances of the class regardless of their concrete type.

I can do it using the HQL query mechanism (as long as I fully qualify the name of the abstract class), but when I try to use the Criteria query mechanism I get a mapping exception with a "No persisten for: <Classname>" type message.

The relevant section in the 2.1.1 documentation is "Chapter 16 Inheritance mappings".

I posted my problem in a forum topic and am raising this issue as a result of instructions given by the hibernate team: http://forum.hibernate.org/viewtopic.php?t=926608

Even if you don't want to implement the functionality I'm talking about (or want to delay it's implementation for a while), it might be a good idea to update the table in the limitations section for the "polymorphic load()/get()" column that says "use a query" to note that you can't use a criteria query.

It also might be worth mentioning that you need to use the fully qualified classname of the abstract class in the HQL query.



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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Assigned: (HB-606) Add nested component in Query By Example

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

Message:

   The following issue has been re-assigned.

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-606
    Summary: Add nested component in Query By Example
       Type: Improvement

     Status: Open
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1.1

   Assignee: Gavin King
   Reporter: Emmanuel Bernard

    Created: Mon, 5 Jan 2004 4:49 PM
    Updated: Tue, 6 Jan 2004 12:18 AM
Environment: Head of 2.1 branch 01/06/2003 00h00 GMT+1

Description:
Add nested component parsing during Query By Example.


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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Assigned: (HB-605) No "duplicate import" error on DTD violation - includes Patch

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

Message:

   The following issue has been re-assigned.

   Assignee: Gavin King (mailto:ga...@hi...)
   Assigner: Gavin King (mailto:ga...@hi...)
       Date: Tue, 6 Jan 2004 12:18 AM
    Comment:
Thanks!
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-605
    Summary: No "duplicate import" error on DTD violation - includes Patch
       Type: Improvement

     Status: Open
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1.1

   Assignee: Gavin King
   Reporter: Michael Gloegl

    Created: Mon, 5 Jan 2004 4:41 PM
    Updated: Tue, 6 Jan 2004 12:18 AM
Environment: Hibernate 2.1.1

Description:
When a mapping document violates the DTD, Hibernate will log the error and nertheless add the mapping to the session factory. Later on a "duplicate import" error gets produced when Hibernate tries to add the same mapping again. This patch intends to solve this by not adding the mapping if there is an error during parsing.


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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Assigned: (HB-596) AbstractQueryImpl.setParameterList may have 0 length list

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

Message:

   The following issue has been re-assigned.

   Assignee: Max Rydahl Andersen (mailto:xa...@xa...)
   Assigner: Gavin King (mailto:ga...@hi...)
       Date: Tue, 6 Jan 2004 12:17 AM
    Comment:
You wanna look at this one Max?
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-596
    Summary: AbstractQueryImpl.setParameterList may have 0 length list
       Type: Bug

     Status: Open
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1

   Assignee: Max Rydahl Andersen
   Reporter: Chris Mercer

    Created: Fri, 2 Jan 2004 12:57 PM
    Updated: Tue, 6 Jan 2004 12:17 AM
Environment: Hibernate 2.1.1, mysql

Description:
Here is the source code for the method

public Query setParameterList(String name, Collection vals) throws HibernateException {
		setParameterList(name, vals, guessType( vals.iterator().next() ) );
		return this;
	}

The problems comes in when the vals collection is size 0.  The vals.iterator().next() will fail with a NoSuchElementException. 
 



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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Assigned: (HB-587) Lazy collections not lazy when used with second level cache

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

Message:

   The following issue has been re-assigned.

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-587
    Summary: Lazy collections not lazy when used with second level cache
       Type: Bug

     Status: Open
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1.1

   Assignee: Gavin King
   Reporter: Juho Snellman

    Created: Tue, 30 Dec 2003 8:53 AM
    Updated: Tue, 6 Jan 2004 12:16 AM
Environment: Hibernate 2.1.1
ehcache

Description:
When an object is loaded from the second level cache, any of its collections that are found from the cache are immediately initialized.
This happens for both lazy and non-lazy collections. These initializations then cascade on to the contents of the collection, and their child-collections. 

For a sufficiently large and interconnected graph of objects this results in a disastrous performance loss when caching is enabled. In my particular case a test enabling caching increases the runtime of a test from about 12 minutes to over 40 minutes. In the latter case SessionImpl.getCachedCollection() takes up 68% of the runtime. Disabling caching only for collections brings the runtime back down.
 
Aside from the performance issue, it seems to me that initializing lazy collections is also conceptually wrong. Shouldn't laziness mean "no work is done unless it's neccessary", instead of "nothing is fetched from the DB unless it's neccessary"?

I'm pretty sure this didn't happen with Hibernate 2.0 and JCS. 


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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-587) Lazy collections not lazy when used with second level cache

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

The following comment has been added to this issue:

     Author: Gavin King
    Created: Tue, 6 Jan 2004 12:16 AM
       Body:
OK, makes sense.

So we may have to rethink that change.

I'm on it.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-587
    Summary: Lazy collections not lazy when used with second level cache
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1.1

   Assignee: 
   Reporter: Juho Snellman

    Created: Tue, 30 Dec 2003 8:53 AM
    Updated: Tue, 6 Jan 2004 12:16 AM
Environment: Hibernate 2.1.1
ehcache

Description:
When an object is loaded from the second level cache, any of its collections that are found from the cache are immediately initialized.
This happens for both lazy and non-lazy collections. These initializations then cascade on to the contents of the collection, and their child-collections. 

For a sufficiently large and interconnected graph of objects this results in a disastrous performance loss when caching is enabled. In my particular case a test enabling caching increases the runtime of a test from about 12 minutes to over 40 minutes. In the latter case SessionImpl.getCachedCollection() takes up 68% of the runtime. Disabling caching only for collections brings the runtime back down.
 
Aside from the performance issue, it seems to me that initializing lazy collections is also conceptually wrong. Shouldn't laziness mean "no work is done unless it's neccessary", instead of "nothing is fetched from the DB unless it's neccessary"?

I'm pretty sure this didn't happen with Hibernate 2.0 and JCS. 


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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Updated: (HB-600) hbm2java can't mapping joined-subclasses correctly which are in independent files from the file of the super class.

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

The following issue has been updated:

    Updater: Eileen Huan (mailto:ff...@16...)
       Date: Mon, 5 Jan 2004 11:25 PM
    Comment:
a new build.xml file.
    Changes:
             Attachment changed to build.xml
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-600
    Summary: hbm2java can't mapping joined-subclasses correctly which are in independent files from the file of the super class.
       Type: Bug

     Status: Resolved
   Priority: Critical
 Resolution: CANNOT REPRODUCE

    Project: Hibernate2
 Components: 
             toolset
   Versions:
             2.1

   Assignee: Max Rydahl Andersen
   Reporter: Eileen Huan

    Created: Mon, 5 Jan 2004 6:16 AM
    Updated: Mon, 5 Jan 2004 11:25 PM
Environment: Apache Ant version 1.5.4 compiled on August 12 2003
Buildfile: build.xml
Detected Java version: 1.4 in: C:\j2sdk1.4.2_03\jre
Detected OS: Windows 2000

Description:
I have posted my problem on hibernate forum as "http://forum.hibernate.org/viewtopic.php?t=926802&sid=a04167043b0b8cd84c79b9d16b332a7e".



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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-600) hbm2java can't mapping joined-subclasses correctly which are in independent files from the file of the super class.

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

The following comment has been added to this issue:

     Author: Eileen Huan
    Created: Mon, 5 Jan 2004 11:18 PM
       Body:
I really don't know how you make the long names of those hbm files as command line parameters. what I did just followed hibernate toolset demo on your hibernate.org website (http://www.hibernate.org/hib_docs/online/workshop_toolset/presentation/html).

My steps in command line are:
f:\set-env.bat
f:\ant clean
f:\ant h2j

BTW: I have cut my build.xml short and uploaded it as a new attachment. The former build.xml is almost the same as the one in your hibernate toolset demo on hibernate.org.

After I write the hbm definition of all subclass into the hbm file of the superclass that is Resource.hbm.xml, and delete all "extends = ..." element, the "hbm2java" tool run perfectly well! 

Since you'r a guy from hibernate team, I hope I can get a real answer from you.

Thank you for your help.

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-600
    Summary: hbm2java can't mapping joined-subclasses correctly which are in independent files from the file of the super class.
       Type: Bug

     Status: Resolved
   Priority: Critical
 Resolution: CANNOT REPRODUCE

    Project: Hibernate2
 Components: 
             toolset
   Versions:
             2.1

   Assignee: Max Rydahl Andersen
   Reporter: Eileen Huan

    Created: Mon, 5 Jan 2004 6:16 AM
    Updated: Mon, 5 Jan 2004 11:18 PM
Environment: Apache Ant version 1.5.4 compiled on August 12 2003
Buildfile: build.xml
Detected Java version: 1.4 in: C:\j2sdk1.4.2_03\jre
Detected OS: Windows 2000

Description:
I have posted my problem on hibernate forum as "http://forum.hibernate.org/viewtopic.php?t=926802&sid=a04167043b0b8cd84c79b9d16b332a7e".



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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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

[Hibernate-issues] [Hibernate-JIRA] Updated: (HB-608) Allow criteria queries on abstract classes from table-per-concrete-class mappings

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

The following issue has been updated:

    Updater: Shorn Tolley (mailto:Sho...@nr...)
       Date: Mon, 5 Jan 2004 11:15 PM
    Comment:
Here's a patch I'm using at the moment to see if the idea will work for us.
It's kind of dodgy coz I don't really know what I'm doing :) (don't think it does the right thing for root classes of other types of hierarchies like table-per-class).

Is the format Ok for submitting patches?
(I'm diffing against two copies of the source, coz I can't access the CVS repository from here).
    Changes:
             Attachment changed to ImplictPolyCriteriaQuery.patch
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-608
    Summary: Allow criteria queries on abstract classes from table-per-concrete-class mappings
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1.1

   Assignee: 
   Reporter: Shorn Tolley

    Created: Mon, 5 Jan 2004 11:09 PM
    Updated: Mon, 5 Jan 2004 11:15 PM
Environment: Hibernate 2.1.1, Ingres 2.6 SP2

Description:
I'm mapping a part of my domain model using the table-per-concrete-class strategy.  I need to use hibernate's "implicit polymorphism" feature to query on the abstract class in the hierarchy to return specific instances of the class regardless of their concrete type.

I can do it using the HQL query mechanism (as long as I fully qualify the name of the abstract class), but when I try to use the Criteria query mechanism I get a mapping exception with a "No persisten for: <Classname>" type message.

The relevant section in the 2.1.1 documentation is "Chapter 16 Inheritance mappings".

I posted my problem in a forum topic and am raising this issue as a result of instructions given by the hibernate team: http://forum.hibernate.org/viewtopic.php?t=926608

Even if you don't want to implement the functionality I'm talking about (or want to delay it's implementation for a while), it might be a good idea to update the table in the limitations section for the "polymorphic load()/get()" column that says "use a query" to note that you can't use a criteria query.

It also might be worth mentioning that you need to use the fully qualified classname of the abstract class in the HQL query.



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

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

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