hibernate-issues — Hibernate JIRA Notifications

[Hibernate-issues] [Hibernate-JIRA] Created: (HB-164) Temporary tables

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-164
    Summary: Temporary tables
       Type: New Feature

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: Christian Bauer

    Created: Tue, 8 Jul 2003 3:44 PM
    Updated: Tue, 8 Jul 2003 3:44 PM

Description:
Many dbms provide the ability to create and manage temporary tables that have some level of
optimization, like being kept in memory. I know this is not related to or-mapping, but I see
Hibernate as something more than just or-mapping: it's a tool that raises the ability to
write database independent applications in a more transparent way.
 What do I need temp tables for? Consider a complex query that provides
 a result that's needed in other queries but for performance reasons you don't want to run
this query as a subquery again and again. On the other side, keeping the result in memory is
not efficient as well, think about  something like select ... from ... where id in (...)
where the content of the in clause is the result of the above query: it's definitely easy to
go over the maximum statement length, while this query can be more efficiently expressed
thru a subquery or a join with the temp table.
 
 For the moment I've created a persistent table to put the query result in, but this way you
need to know how many temp tables you need at design time or add a selection column... not
as handy as a temporary table that can be created at run time and has special handling by
the database.


---------------------------------------------------------------------
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-163) Table locking

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-163
    Summary: Table locking
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: Christian Bauer

    Created: Tue, 8 Jul 2003 3:43 PM
    Updated: Tue, 8 Jul 2003 3:43 PM

Description:
I would like to have a way to lock objects in a more database
 independent way, and in  particular to lock a table. Now I need
 to make it impossible for two instances of my client application
 to perform a long task in parallel, but the present locking doesn't
 work with databases that does not provide a "select for update".
 On the other side, I guess that most databases provide table level
 locking "LOCK TABLE ...". I would be a nice to have, currently I have
 to isolate databases that don't support Hibernate locking and do my
 own...

 Oh, in the case of SapDb the locking problem could be solved by
 using a row level lock (available) instead of a select for update.


---------------------------------------------------------------------
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-162) No way to reset the maxResults() on a Query

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

Message:

  A new issue has been created in JIRA.

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-162
    Summary: No way to reset the maxResults() on a Query
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: Christian Bauer

    Created: Tue, 8 Jul 2003 3:41 PM
    Updated: Tue, 8 Jul 2003 3:41 PM

Description:
There is currently no way to reset the maximum number of results (query.setMaxResults(int))
returned from a Query once it has been set to a value.  While you can certainly set it to
Integer.MAX_VALUE, that seems impractical.  I have tried query.setMaxResults(0) which
produces "zero" results, and query.setMaxResults(-1) which produces an exception.
 
 I have looked at the source code and noticed that internally the value is maintained as an
Integer and initially starts as "null", however they current interface provides no mechanism
to reset the value to "null" as the calling signature is as show above
Query.setMaxResults(int).
 
 My suggestion would be to simply take any value < 1 as a reset.
 
 Cheers, Dawson


---------------------------------------------------------------------
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-161) sql-type is ignored by net.sf.hibernate.tool.hbm2ddl.SchemaExport

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

Message:

   The following issue has been re-assigned.

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-161
    Summary: sql-type is ignored by net.sf.hibernate.tool.hbm2ddl.SchemaExport
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.0.1

   Assignee: Max Rydahl Andersen
   Reporter: Christian Bauer

    Created: Tue, 8 Jul 2003 3:40 PM
    Updated: Tue, 8 Jul 2003 3:41 PM

Description:
I've tried this in a hbm:
 
 <property name="description" column="description" type="string">
 	<column name="description" sql-type="text" />
 </property>
 
 but the SchemaExport generates this in the DDL:
 
 description VARCHAR(255)


---------------------------------------------------------------------
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-161) sql-type is ignored by net.sf.hibernate.tool.hbm2ddl.SchemaExport

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-161
    Summary: sql-type is ignored by net.sf.hibernate.tool.hbm2ddl.SchemaExport
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.0.1

   Assignee: 
   Reporter: Christian Bauer

    Created: Tue, 8 Jul 2003 3:40 PM
    Updated: Tue, 8 Jul 2003 3:40 PM

Description:
I've tried this in a hbm:
 
 <property name="description" column="description" type="string">
 	<column name="description" sql-type="text" />
 </property>
 
 but the SchemaExport generates this in the DDL:
 
 description VARCHAR(255)


---------------------------------------------------------------------
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-145) insert for classes with composite-id crashes

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

The following comment has been added to this issue:

     Author: Christian Bauer
    Created: Tue, 8 Jul 2003 3:39 PM
       Body:
 the mapping I used is:
 
 <composite-id>
     <key-property column="COD" length="22" name="cod" type="java.lang.Long"/>
     <key-property column="DATA_FIN" length="7" name="dataFin" type="java.util.Date"/>
 </composite-id>
 <property column="PKID"  name="pkid" not-null="true" type="java.lang.Long"/>
 <property column="NAME" length="200" name="name" not-null="true" type="java.lang.String"/>
 <property column="DATA_INI" length="7" name="dataIni" not-null="true"
type="java.util.Date"/>
 <property column="MGR_ID" length="22" name="mgrId" type="java.lang.Long"/>
 <property column="DEPT_ID" length="22" name="deptId" type="java.lang.Long"/>
 <property column="BOGUS_DT_FIN" length="7" name="dataIni" not-null="true"
type="java.util.Date"/>
 
   <many-to-one name="CurrentManager" class="CdtDACPerson" outer-join="true" insert="false">
       <column name="MGR_ID"  />
       <column name="BOGUS_DT_FIN"/>
   </many-to-one>
 
 If the last many-to-one mapping would disappear the insert would succeed
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-145
    Summary: insert for classes with composite-id crashes
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2

   Assignee: 
   Reporter: Hrituc Ovidiu

    Created: Thu, 19 Jun 2003 10:21 AM
    Updated: Thu, 19 Jun 2003 7:09 PM
Environment: W2k professional, SQL Server 2k, OC4J

Description:
Insert for classes with composite-id crashes when persisting to SQL Server 2000.
The composite id consists of the COD, DATA_FIN combination. I am trying to keep the history of a person in the same table and the current record to be the combination (COD_Value, 01/01/3000)
The current manager's data gets pulled out with a many-to-one relationship with a composite fk (MGR_ID, BOGUS_DT_FIN).
Loading goes ok. 
Insert doesn't, the exceptions look like this:

Hibernate: insert into PERSON (PKID, NAME, DATA_INI, DEPT_ID, MGR_ID, BOGUS_DT_FIN, COD, DATA_FIN) values (?, ?, ?, ?, ?, ?, ?, ?)

Jun 19, 2003 6:02:16 PM net.sf.hibernate.util.JDBCExceptionReporter logExceptions

WARNING: SQL Error: 0, SQLState: 07009

Jun 19, 2003 6:02:16 PM net.sf.hibernate.util.JDBCExceptionReporter logExceptions

SEVERE: [Microsoft][SQLServer 2000 Driver for JDBC]Invalid parameter binding(s).

Jun 19, 2003 6:02:17 PM net.sf.hibernate.JDBCException <init>

SEVERE: Could not synchronize database state with session

java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Invalid parameter binding(s).

	at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)

	at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)

	at com.microsoft.jdbc.base.BasePreparedStatement.validateParameterIndex(Unknown Source)

	at com.microsoft.jdbc.base.BasePreparedStatement.setObjectInternal(Unknown Source)

	at com.microsoft.jdbc.base.BasePreparedStatement.setTimestamp(Unknown Source)

	at com.evermind.sql.FilterPreparedStatement.setTimestamp(FilterPreparedStatement.java:394)

	at com.evermind.sql.FilterPreparedStatement.setTimestamp(FilterPreparedStatement.java:394)

	at net.sf.hibernate.type.TimestampType.set(TimestampType.java:27)

	at net.sf.hibernate.type.NullableType.nullSafeSet(NullableType.java:46)

	at net.sf.hibernate.type.NullableType.nullSafeSet(NullableType.java:31)

	at net.sf.hibernate.type.ComponentType.nullSafeSet(ComponentType.java:163)

	at net.sf.hibernate.persister.EntityPersister.dehydrate(EntityPersister.java:369)

	at net.sf.hibernate.persister.EntityPersister.insert(EntityPersister.java:446)

	at net.sf.hibernate.impl.ScheduledInsertion.execute(ScheduledInsertion.java:20)

	at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2064)

	at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2036)

	at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:1980)

	at it.saga.library.commonDataTypes.impl.CdtBLGBaseSessionBean.save(CdtBLGBaseSessionBean.java:247)

	at CdtBLGPerson_StatelessSessionBeanWrapper10.save(CdtBLGPerson_StatelessSessionBeanWrapper10.java:133)

	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

	at java.lang.reflect.Method.invoke(Method.java:324)

	at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:119)

	at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:48)

	at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:797)

	at java.lang.Thread.run(Thread.java:536)




---------------------------------------------------------------------
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-159) Trans-database 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=HB-159


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-159
    Summary: Trans-database Support
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: Christian Bauer

    Created: Tue, 8 Jul 2003 3:38 PM
    Updated: Tue, 8 Jul 2003 3:38 PM

Description:
Ability to define an object model, and specify that some classes live in database A, and
some live in database B.  Hibernate should assume that it can not join between the databases
and, in fact, the databases may be from different vendors.
 
 I know this can be done by creating multiple Sessions, but I don't think this will make
trans-database relationships work.  That is, I need to be able to have 1-1 and 1-M
relationships defined between objects that live in two different databases.  When Hibernate
goes to lazily initialize a 1-1 or 1-M relationship, it needs to be able to do so using a
Connection connected to the appropriate database.  If M-M can be achieved, as well, so much
the better (will require specification of which database the M-M table lives in, I believe.)
 
 Goal is that a single Session can be used to obtain objects and resulting objects'
relationships all work, even though they may be using Connections from the other database.


---------------------------------------------------------------------
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-160) Batch Reading

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-160
    Summary: Batch Reading
       Type: New Feature

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: Christian Bauer

    Created: Tue, 8 Jul 2003 3:39 PM
    Updated: Tue, 8 Jul 2003 3:39 PM

Description:
Feature is used to reduce # queries sent to the database to retrieve related lazily
initialized 1-1's.  Example:  Retrieve 20 Contact objects, each has a 1-1 to an Account. 
Initial Query just asked to retrieve the Contact objects with nothing else being built
initially.  If each Contact works for a different Account, then if I call getAccount on each
Contact (with initially empty cache), what started as 1 query turns into 21 queries (one PK
query for each Account).
 
 Feature supports the ability for those lazy Account references to "remember" what their
"originating query" was - the one used to retrieve the 20 Contact objects in the first
place.  Then, when the first Contact's "account" reference is initialized, it joins with the
originating query's criteria to get all of the related accounts that match the originating
query's criteria, populating the cache with 20 Account objects with one query.  Now, what
would otherwise be 21 queries is now just 2 (1 for the 20 Contacts, and 1 for the 20
Accounts).
 
 Example:
 
 originating query:  select * from contact where last_name = 'Smith'
 
 Then, when the first uninitialized Contact.account reference is initialized (from that set
of Contacts), the account query is:
 
 select t0.* from account t0, contact t1 where t1.account_id = t0.account_id and
t1.last_name = 'Smith'


---------------------------------------------------------------------
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-157) MapGenerator generator xml fix

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-157
    Summary: MapGenerator generator xml fix
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             toolset
   Versions:
             2.0.1

   Assignee: Max Rydahl Andersen
   Reporter: Christian Bauer

    Created: Tue, 8 Jul 2003 3:37 PM
    Updated: Tue, 8 Jul 2003 3:37 PM

Description:
HB-94 is still open with the hibernate-extensions-2.0.zip from 2003-06-12 07:00. I didn't
found a way to re-open HB-94, so I submit this new bug.


---------------------------------------------------------------------
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-158) Customizable 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-158


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-158
    Summary: Customizable SQL
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: Christian Bauer

    Created: Tue, 8 Jul 2003 3:38 PM
    Updated: Tue, 8 Jul 2003 3:38 PM

Description:
Ability to be able to get the SQL Hibernate would send to the database for a given query,
be able to look at it and possibly tweak it (as a String) and then allow Hibernate to
continue - sending the SQL on its way to the database.  This allows for subtle hints and
other database tricks one is often forced to do when you don't "own" the datamodel.


---------------------------------------------------------------------
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-156) Qualified one-to-many

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-156
    Summary: Qualified one-to-many
       Type: New Feature

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
   Versions:
             2.0.1

   Assignee: 
   Reporter: Christian Bauer

    Created: Tue, 8 Jul 2003 3:36 PM
    Updated: Tue, 8 Jul 2003 3:36 PM

Description:
Ability to add static criteria to what would otherwise be a one-to-many relationship, to
make it into a one-to-one relationship.  Example:  Account has one-to-many relationship to
Address by way of address.account_id foreign key.  However, there is only one "primary"
address for a given account, indicated in the datamodel by address.is_primary = 'Y' for
exactly one row for any given Account.  Enhancement would let me create a property
"primaryAddress" on Account that is mapped like a one-to-many except that it also includes
something like "...AND primary = true".
 
 This allows me to obtain an Account object and call getPrimaryAddress and have that SQL
query the address table "WHERE account_id = ? AND is_primary = 'Y'".
 


---------------------------------------------------------------------
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-155) Optimistic locking by columns' original values

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-155
    Summary: Optimistic locking by columns' original values
       Type: New Feature

     Status: Unassigned
   Priority: Blocker

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: Christian Bauer

    Created: Tue, 8 Jul 2003 3:36 PM
    Updated: Tue, 8 Jul 2003 3:36 PM

Description:
 Ability to support optimistic locking by columns' original values.  When UPDATE statements
are generated, in addition to the primary key, the WHERE clause includes either all of the
columns' original values, or just the changed columns' original values.  This allows
optimistic locking without requiring the datamodel to have a "timestamp" or "version"
column.


---------------------------------------------------------------------
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-153) discriminator force true doesn't work

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-153
    Summary: discriminator force true doesn't work
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: Christian Bauer

    Created: Tue, 8 Jul 2003 3:34 PM
    Updated: Tue, 8 Jul 2003 3:34 PM
Environment: win2000, WSAD v5, DB2, websphere v5

Description:
A discriminator force true does not cause Hibernate to ignore unmapped discriminator
values, instead WrongClassException is thrown.
 
 see http://sourceforge.net/forum/forum.php?thread_id=889426&forum_id=128638 for more info


---------------------------------------------------------------------
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-154) MapGenerator documentation bug

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

Message:

  A new issue has been created in JIRA.

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-154
    Summary: MapGenerator documentation bug
       Type: Bug

     Status: Assigned
   Priority: Trivial

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: Christian Bauer
   Reporter: Christian Bauer

    Created: Tue, 8 Jul 2003 3:35 PM
    Updated: Tue, 8 Jul 2003 3:35 PM

Description:
 In chapter "16.3.1. Running the tool" the name of the class is written as
"src.net.sf.hibernate.tool.class2hbm.MapGenerator", but it has to be
"net.sf.hibernate.tool.class2hbm.MapGenerator".
 


---------------------------------------------------------------------
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-152) Ability to map one class across two or more tables

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-152
    Summary: Ability to map one class across two or more tables
       Type: New Feature

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: Christian Bauer

    Created: Tue, 8 Jul 2003 3:33 PM
    Updated: Tue, 8 Jul 2003 3:33 PM

Description:
Assumption is that
the tables can all be joined with regular joins all the time, and that the key structure
matches, although the name of the columns may differ across the tables.  An insert of an
object results in an insert to each of the mapped tables all using the same key value.  The
class can then map its properties to any column in any table.  This should all be done
without the workaround of using a delegate.  Thank you.


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

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

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

[Hibernate-issues] [Hibernate-JIRA] Created: (HB-151) Traversing several joined-subclasses in where clause leaves out inner joins

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-151
    Summary: Traversing several joined-subclasses in where clause leaves out inner joins
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: Christian Bauer

    Created: Tue, 8 Jul 2003 3:32 PM
    Updated: Tue, 8 Jul 2003 3:32 PM
Environment: WSAD 5.0.1, JDK 1.3.1, Oracle 9i, Windows 2000

Description:
Class-diagram:
 a-->b  a inherits from b
 a==b   a has relationship to b
 
 (Sorry, classnames are in Dutch)
 
 Persoon == Beroepsuitoefening
 Beroepsuitoefening <-- Jurist
 Jurist == Bevoegdheid
 Bevoegdheid <-- Beediging <-- Procureurschap
 
 If my query contains 'where jurist.persoon.naam like ?', the generated SQL looks like this
(which is OK):
 
 select count(*) as x0_0_ 
 from jurist persiste0_ 
 	inner join beroepsuitoefening persiste0__1 on persiste0_.beg_id=persiste0__1.id, 
 persoon persiste1_ 
 where (
 	(
 		persiste1_.naam like ?  
 		and persiste0__1.psn_id=persiste1_.id
 	)
 )
 
 
 However, if I start one level deeper in the hierarchy ('where
procureurschap.jurist.persoon.naam like ?') the SQL query looks like this:
 
 select count(*) as x0_0_ 
 from procureurschap persiste0_ 
 	inner join beediging persiste0__1 on persiste0_.bvh_id=persiste0__1.bvh_id 
 	inner join bevoegdheid persiste0__2 on persiste0_.bvh_id=persiste0__2.id, 
 jurist persiste1_, 
 persoon persiste2_ 
 
 where (
 	(
 		persiste2_.naam=?  
 		and persiste0__2.beg_id=persiste1_.beg_id 
 		and persiste1__1.psn_id=persiste2_.id
 	)
 )
 
 [Queries are indented to show outline]
 
 As you can see, the last clause references persiste1__1, which isn't listed in the from
clause. It's intended to, because the pattern matches with the previous example (_1 begin
the first innerjoin for persiste1_). It should be an alias for beroepsuitoefening just as it
is in the previous 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] Created: (HB-150) Add getSession method to Transaction interface

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-150
    Summary: Add getSession method to Transaction interface
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Fix Fors:
             2.1
   Versions:
             2.0.1
             2.0.2

   Assignee: 
   Reporter: Christian Bauer

    Created: Tue, 8 Jul 2003 3:31 PM
    Updated: Tue, 8 Jul 2003 3:31 PM

Description:
It should be possible to retrieve the Session associated with a Transaction from a Transaction instance. This would assist some data access implentations by exposing the relationship in a convenient and logical manner.


---------------------------------------------------------------------
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-149) Using Sets Before Fully Initialized causes NullPointerException

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-149
    Summary: Using Sets Before Fully Initialized causes NullPointerException
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: Christian Bauer

    Created: Tue, 8 Jul 2003 3:30 PM
    Updated: Tue, 8 Jul 2003 3:30 PM
Environment: JDK 1.4.1

Description:
one-to-man from A -> B
 
 A.addB(B foo) {
   if(null != foo) {
     set_of_bs.add(foo);
     foo.setA(this);
   }
 }
 
 
 B.setA(A bar) {
   a = bar;
   if(null != a && !a.getBs().contains(this)) {
     a.addB(b);
   }
 }
 
 I'm not sure why but the tempList in the net.sf.hibernate.collection.Set ends up being null
at some point during initialization. endRead is being called twice, the first time its ok
the second time it throws a NullPointerException.
 
 I'm not sure this is a bug with Hibernate or if I should not be maintaining the backwards
pointers in this way. 


---------------------------------------------------------------------
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-166) firebird dialect with support for LIMIT

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

The following comment has been added to this issue:

     Author: Ludovic Orban
    Created: Sun, 29 Jun 2003 12:37 PM
       Body:
I can't find any attachment button so here's the code:

package net.sf.hibernate.dialect;

import java.sql.Types;

import net.sf.hibernate.cfg.Environment;

/**
 * An SQL dialect for Firebird.
 * @author Ludovic Orban
 */

public class FirebirdDialect extends Dialect {
	public FirebirdDialect() {
		super();
		register( Types.BIT, "SMALLINT" );
		register( Types.BIGINT, "NUMERIC(18,0)" );
		register( Types.SMALLINT, "SMALLINT" );
		register( Types.TINYINT, "SMALLINT" );
		register( Types.INTEGER, "INTEGER" );
		register( Types.CHAR, "CHAR(1)" );
		register( Types.VARCHAR, "VARCHAR($l)" );
		register( Types.FLOAT, "FLOAT" );
		register( Types.DOUBLE, "DOUBLE PRECISION" );
		register( Types.DATE, "DATE" );
		register( Types.TIME, "TIME" );
		register( Types.TIMESTAMP, "TIMESTAMP" );
		register( Types.VARBINARY, "BLOB" );
		register( Types.NUMERIC, "NUMERIC(18, $l)" );
		register( Types.BLOB, "BLOB" );
		register( Types.CLOB, "BLOB SUB_TYPE 1" );
		
		getDefaultProperties().setProperty(Environment.USE_OUTER_JOIN, "true");
		getDefaultProperties().setProperty(Environment.STATEMENT_BATCH_SIZE, NO_BATCH);
		getDefaultProperties().setProperty(Environment.STATEMENT_CACHE_SIZE, "0");
		
	}
	
	public String getAddColumnString() {
		return "add";
	}
	public String getSequenceNextValString(String sequenceName) {
		return "select gen_id( " + sequenceName + ", 1 ) from RDB$DATABASE";
	}
	public String getCreateSequenceString(String sequenceName) {
		return "create generator " + sequenceName;
	}
	public String getDropSequenceString(String sequenceName) {
		return "delete from RDB$GENERATORS where RDB$GENERATOR_NAME = '" + sequenceName.toUpperCase() + "'";
	}
	
	public boolean supportsSequences() {
		return true;
	}

    public boolean supportsLimit() {
        return true;
    }

	public String getLimitString(String sql) {
		StringBuffer pagingSelect = new StringBuffer(100);
		pagingSelect.append("select first ? skip ?");
		int idx = sql.toLowerCase().indexOf("select");
		pagingSelect.append(sql.substring(idx + "select".length()));
		return pagingSelect.toString();
	}


}

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-166
    Summary: firebird dialect with support for LIMIT
       Type: Patch

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: Ludovic Orban

    Created: Sun, 29 Jun 2003 12:27 PM
    Updated: Sun, 29 Jun 2003 12:27 PM

Description:
tested with firebird 1.0.2 and JayBird type 4 driver


---------------------------------------------------------------------
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-166) firebird dialect with support for LIMIT

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-166
    Summary: firebird dialect with support for LIMIT
       Type: Patch

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: Ludovic Orban

    Created: Sun, 29 Jun 2003 12:27 PM
    Updated: Sun, 29 Jun 2003 12:27 PM

Description:
tested with firebird 1.0.2 and JayBird type 4 driver


---------------------------------------------------------------------
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-165) Where clause not recognising booleans.

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-165
    Summary: Where clause not recognising booleans.
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: 
   Reporter: Andrew Hayes

    Created: Sun, 29 Jun 2003 4:30 AM
    Updated: Sun, 29 Jun 2003 4:30 AM
Environment: jdk1.4.1 on win32(XP) with a MySQL (v3.23.55) back-end.

Description:
SQLException (Column not found) thrown when using 'where blah = false' in a query. Work around is to change where clause to 'where blah = 0'.


Query (broken version):


"select booking from " +
  "from au.com.octarine.bookingengine.model.Booking as booking " +
"where " +
  "booking.sheet.courseId = ? and " +
  "booking.sheet.year = ? and " +
  "booking.sheet.month = ? and " +
  "booking.sheet.day = ? and " +
  "booking.booked = false and " +
  "booking.time between ? and ? "


Query (working version):


"select booking from " +
  "from au.com.octarine.bookingengine.model.Booking as booking " +
"where " +
  "booking.sheet.courseId = ? and " +
  "booking.sheet.year = ? and " +
  "booking.sheet.month = ? and " +
  "booking.sheet.day = ? and " +
  "booking.booked = 0 and " +
  "booking.time between ? and ? "


Booking.java:


/**
 * Booking.java
 *
 * Created on Jan 30, 2003, 4:15:10 PM
 */

package au.com.octarine.bookingengine.model;

import java.sql.Time;

/**
 * The <code>Booking</code> instance captures the booking information.
 *
 * @author Andrew
 * @version $Revision: $
 */

public class Booking {

    // Booking unique id
    private int id;

    // Owning sheet.
    private Sheet sheet;

    // Tee
    private int teeNumber;

    // Time of booking.
    private Time time;

    // Booked? (yes/no)
    private boolean booked;

    // Temporary booking? (yes/no)
    private boolean temporary;

    // Booking userid
    private String bookedBy;

    // When the booking was made.
    private Time bookedWhen;

    // Playing userid
    private String playerId;

    // Player name (if not person who booked).
    private String publicName;

    /** Default constructor. */
    public Booking() {
    }

    public Booking( Sheet sheet, int teeNumber, Time time ) {
        this.sheet = sheet;
        this.teeNumber = teeNumber;
        this.time = time;
    }

    public int getId() {
        return id;
    }

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

    public Sheet getSheet() {
        return sheet;
    }

    public void setSheet( Sheet sheet ) {
        this.sheet = sheet;
    }

    public int getTeeNumber() {
        return teeNumber;
    }

    public void setTeeNumber( int teeNumber ) {
        this.teeNumber = teeNumber;
    }

    public Time getTime() {
        return time;
    }

    public void setTime( Time time ) {
        this.time = time;
    }

    public boolean isBooked() {
        return booked;
    }

    public void setBooked( boolean booked ) {
        this.booked = booked;
    }

    public boolean isTemporary() {
        return temporary;
    }

    public void setTemporary( boolean temporary ) {
        this.temporary = temporary;
    }

    public String getBookedBy() {
        return bookedBy;
    }

    public void setBookedBy( String bookedBy ) {
        this.bookedBy = bookedBy;
    }

    public Time getBookedWhen() {
        return bookedWhen;
    }

    public void setBookedWhen( Time bookedWhen ) {
        this.bookedWhen = bookedWhen;
    }

    public String getPlayerId() {
        return playerId;
    }

    public void setPlayerId( String playerId ) {
        this.playerId = playerId;
    }

    public String getPublicName() {
        return publicName;
    }

    public void setPublicName( String publicName ) {
        this.publicName = publicName;
    }

    /** Generate human-readable representation. */
    public String toString() {
        StringBuffer buf = new StringBuffer( super.toString() );
        buf.append( " Booking { " );
        // todo: insert contents here
        buf.append( " }" );
        return buf.toString();
    }
}



Booking.hbm.xml:



<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
        "-//Hibernate/Hibernate Mapping DTD//EN"
        "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd">

<hibernate-mapping>
    <class name="au.com.octarine.bookingengine.model.Booking" table="bookings">
        <id name="id" column="id" type="int" >
            <generator class="identity" />
        </id>
        <many-to-one name="sheet" column="sheet_id" class="au.com.octarine.bookingengine.model.Sheet" />
        <property name="teeNumber" column="tee_number" type="integer"/>
        <property name="time" column="time" type="time"/>
        <property name="booked" column="booked" type="boolean"/>
        <property name="temporary" column="temporary" type="boolean"/>
        <property name="bookedBy" column="booked_by" type="string" length="20" />
        <property name="bookedWhen" column="booked_when" type="time"/>
        <property name="playerId" column="player_id" type="string" length="20" />
        <property name="publicName" column="name" type="string" length="50" />
    </class>
</hibernate-mapping>


Generated SQL:


Hibernate: select booking0_.id as id, booking0_.sheet_id as sheet_id, booking0_.tee_number as tee_number, booking0_.time as time, booking0_.booked as booked, booking0_.temporary as temporary, booking0_.booked_by as booked_by, booking0_.booked_when as booked_w8_, booking0_.player_id as player_id, booking0_.name as name from bookings booking0_, sheets sheet1_ where (sheet1_.course_id=?  and booking0_.sheet_id=sheet1_.id)and(sheet1_.year=?  and booking0_.sheet_id=sheet1_.id)and(sheet1_.month=?  and booking0_.sheet_id=sheet1_.id)and(sheet1_.day=?  and booking0_.sheet_id=sheet1_.id)and(booking0_.booked=false )and(booking0_.time between ? and ? ) order by  booking0_.tee_number , booking0_.time


Stack trace:


Caused by: java.sql.SQLException: Column not found,  message from server: "Unknown column 'false' in 'where clause'"
	at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1651)
	at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:889)
	at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:956)
	at com.mysql.jdbc.Connection.execSQL(Connection.java:1874)
	at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1538)
	at net.sf.hibernate.impl.BatcherImpl.getResultSet(BatcherImpl.java:62)
	at net.sf.hibernate.loader.Loader.getResultSet(Loader.java:537)
	at net.sf.hibernate.loader.Loader.doFind(Loader.java:140)
	at net.sf.hibernate.loader.Loader.find(Loader.java:604)
	at net.sf.hibernate.hql.QueryTranslator.find(QueryTranslator.java:912)
	at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1356)
	... 44 more




---------------------------------------------------------------------
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-159) Trans-database Support

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

The following comment has been added to this issue:

     Author: Christian Bauer
    Created: Sat, 28 Jun 2003 7:15 AM
       Body:
I think this should be solved at the database level, not with ORM. Most good RDBMS support some way to join databases/schemas. Even some kind of replication would work.

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-159
    Summary: Trans-database Support
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: Mike Gorman

    Created: Thu, 26 Jun 2003 8:13 AM
    Updated: Thu, 26 Jun 2003 8:13 AM

Description:
Ability to define an object model, and specify that some classes live in database A, and some live in database B.  Hibernate should assume that it can not join between the databases and, in fact, the databases may be from different vendors.

I know this can be done by creating multiple Sessions, but I don't think this will make trans-database relationships work.  That is, I need to be able to have 1-1 and 1-M relationships defined between objects that live in two different databases.  When Hibernate goes to lazily initialize a 1-1 or 1-M relationship, it needs to be able to do so using a Connection connected to the appropriate database.  If M-M can be achieved, as well, so much the better (will require specification of which database the M-M table lives in, I believe.)

Goal is that a single Session can be used to obtain objects and resulting objects' relationships all work, even though they may be using Connections from the other database.


---------------------------------------------------------------------
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-151) Traversing several joined-subclasses in where clause leaves out inner joins for superclasses

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

The following comment has been added to this issue:

     Author: Sander Verbruggen
    Created: Fri, 27 Jun 2003 3:48 AM
       Body:
It seems that this works fine when a property of the second joined-subclass is used in the query.

If my query only contains
where procureur.jurist.persoon.naam = ?

Hibernate fails, but if my query contains

where procureur.jurist.einddatum = ? 
and procureur.jurist.persoon.naam = ?

then everything is fine. It seems that the parser interpretes the path-expression incorrectly if too many entities are used...
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-151
    Summary: Traversing several joined-subclasses in where clause leaves out inner joins for superclasses
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: Sander Verbruggen

    Created: Thu, 26 Jun 2003 3:05 AM
    Updated: Thu, 26 Jun 2003 3:05 AM
Environment: WSAD 5.0.1, JDK 1.3.1, Oracle 9i, Windows 2000

Description:
Class-diagram:
a-->b  a inherits from b
a==b   a has relationship to b

(Sorry, classnames are in Dutch)

Persoon == Beroepsuitoefening
Beroepsuitoefening <-- Jurist
Jurist == Bevoegdheid
Bevoegdheid <-- Beediging <-- Procureurschap

If my query contains 'where jurist.persoon.naam like ?', the generated SQL looks like this (which is OK):

select count(*) as x0_0_ 
from jurist persiste0_ 
	inner join beroepsuitoefening persiste0__1 on persiste0_.beg_id=persiste0__1.id, 
persoon persiste1_ 
where (
	(
		persiste1_.naam like ?  
		and persiste0__1.psn_id=persiste1_.id
	)
)


However, if I start one level deeper in the hierarchy ('where procureurschap.jurist.persoon.naam like ?') the SQL query looks like this:

select count(*) as x0_0_ 
from procureurschap persiste0_ 
	inner join beediging persiste0__1 on persiste0_.bvh_id=persiste0__1.bvh_id 
	inner join bevoegdheid persiste0__2 on persiste0_.bvh_id=persiste0__2.id, 
jurist persiste1_, 
persoon persiste2_ 

where (
	(
		persiste2_.naam=?  
		and persiste0__2.beg_id=persiste1_.beg_id 
		and persiste1__1.psn_id=persiste2_.id
	)
)

[Queries are indented to show outline]

As you can see, the last clause references persiste1__1, which isn't listed in the from clause. It's intended to, because the pattern matches with the previous example (_1 begin the first innerjoin for persiste1_). It should be an alias for beroepsuitoefening just as it is in the previous 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] Commented: (HB-150) Add getSession method to Transaction interface

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

The following comment has been added to this issue:

     Author: Chris Webb
    Created: Fri, 27 Jun 2003 3:00 AM
       Body:
Gavin, just saw your response in the discussion thread. I'm wondering if you removed/closed the original issue that I raised because I couldn't find it (HB-151). I thought it must have been lost so I've re-entered it as you can see.

I understand your comment regarding that the method should not be added to the interface because a JTA transaction may not be associated with just one Session. This enhancement would only be good for JDBC transactions which are bound to one session. How about adding the getSession method to the JDBCTransaction class so then I can at least retrieve the Session by casting. If the transaction is not an instance of JDBCTransaction my code will throw some sort of exception.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-150
    Summary: Add getSession method to Transaction interface
       Type: New Feature

     Status: Unassigned
   Priority: Major

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

   Assignee: 
   Reporter: Chris Webb

    Created: Wed, 25 Jun 2003 11:45 PM
    Updated: Wed, 25 Jun 2003 11:45 PM

Description:
It should be possible to retrieve the Session associated with a Transaction from a Transaction instance. This would assist some data access implentations by exposing the relationship in a convenient and logical manner.


---------------------------------------------------------------------
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-164) Temporary tables

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-164
    Summary: Temporary tables
       Type: New Feature

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
   Versions:
             2.0.1

   Assignee: 
   Reporter: Andrea Aime

    Created: Fri, 27 Jun 2003 2:52 AM
    Updated: Fri, 27 Jun 2003 2:52 AM

Description:
Many dbms provide the ability to create and manage temporary tables that have some level of optimization, like being kept in memory. I know this is not related to or-mapping, but I see Hibernate as something more than just or-mapping: it's a tool that raises the ability to write database independent applications in a more transparent way.
What do I need temp tables for? Consider a complex query that provides
a result that's needed in other queries but for performance reasons you don't want to run this query as a subquery again and again. On the other side, keeping the result in memory is not efficient as well, think about  something like select ... from ... where id in (...) where the content of the in clause is the result of the above query: it's definitely easy to go over the maximum statement length, while this query can be more efficiently expressed thru a subquery or a join with the temp table.

For the moment I've created a persistent table to put the query result in, but this way you need to know how many temp tables you need at design time or add a selection column... not as handy as a temporary table that can be created at run time and has special handling by the database.


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