Menu
▾
▴
hibernate-issues — Hibernate JIRA Notifications
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(32) |
Jun
(175) |
Jul
(209) |
Aug
(302) |
Sep
(287) |
Oct
(339) |
Nov
(314) |
Dec
(329) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(479) |
Feb
(389) |
Mar
(599) |
Apr
(307) |
May
(390) |
Jun
(300) |
Jul
(410) |
Aug
(458) |
Sep
(299) |
Oct
(315) |
Nov
(363) |
Dec
(529) |
| 2005 |
Jan
(568) |
Feb
(434) |
Mar
(1004) |
Apr
(823) |
May
(767) |
Jun
(763) |
Jul
(854) |
Aug
(862) |
Sep
(560) |
Oct
(853) |
Nov
(763) |
Dec
(731) |
| 2006 |
Jan
(776) |
Feb
(608) |
Mar
(657) |
Apr
(424) |
May
(559) |
Jun
(440) |
Jul
(448) |
Aug
(58) |
Sep
|
Oct
(17) |
Nov
(16) |
Dec
(8) |
| 2007 |
Jan
(1) |
Feb
(8) |
Mar
(2) |
Apr
(5) |
May
(3) |
Jun
(3) |
Jul
(3) |
Aug
(16) |
Sep
(10) |
Oct
(4) |
Nov
(4) |
Dec
(4) |
| 2008 |
Jan
(8) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: <leg...@at...> - 2003-07-25 13:29:14
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-212 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-212 Summary: Nightly builds or tarballs from CVS Type: New Feature Status: Assigned Priority: Minor Project: Hibernate2 Components: core Fix Fors: 2.0.2 Versions: 2.0.1 Assignee: Christian Bauer Reporter: Christian Bauer Created: Fri, 25 Jul 2003 8:28 AM Updated: Fri, 25 Jul 2003 8:28 AM Environment: n/a Description: Check SF for nightly builds and/or CVS tarballs, link on the Hibernate wiki. --------------------------------------------------------------------- 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 |
|
From: <leg...@at...> - 2003-07-24 05:57:17
|
Message:
The following issue has been re-assigned.
Assignee: Gavin King (mailto:ga...@in...)
Assigner: Gavin King (mailto:ga...@in...)
Date: Thu, 24 Jul 2003 12:57 AM
Comment:
I will look at this asap
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-209
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-209
Summary: FlushMode.AUTO problem in joined subclass hierarchy
Type: Bug
Status: Assigned
Priority: Major
Project: Hibernate2
Versions:
2.0.1
Assignee: Gavin King
Reporter: Panagiotis Louridas
Created: Tue, 22 Jul 2003 8:09 AM
Updated: Thu, 24 Jul 2003 12:57 AM
Environment: RedHat Linux 9.0, JVM 1.4.2
Description:
Suppose we have a class hierarchy
A <- B <- C.
In my case the class hierarchy is mapped as a joined-subclass hierarchy, but my observations may hold in general.
I use a Session with the default FlushMode setting (FlushMode.AUTO). I open the session, load an object of class B or C, perform some changes on it, do some queries and flush the session. When the session is flushed, only updates for the table pertaining to class A are issued by hibernate.
If I manually flush just before the queries hibernate performs fine, issuing the proper updates for tables B and C. The same happens when I manually flush at the end of the transaction, after the queries, but having set the Session's flush mode to FlushMode.NEVER.
---------------------------------------------------------------------
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
|
|
From: <leg...@at...> - 2003-07-24 05:57:16
|
The following comment has been added to this issue:
Author: Gavin King
Created: Thu, 24 Jul 2003 12:56 AM
Body:
You may need to run stuff in the "WebSphere VM".
Otherwise just don't use the TransactionManagerLookup in development (just =
use it in production).
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?=
key=3DHB-210
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-210
Summary: JTA with Websphere 5.0 in WASD 5.0 environment
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:=20
core
Versions:
2.0.1
Assignee:=20
Reporter: gilles courtial
Created: Wed, 23 Jul 2003 2:55 AM
Updated: Wed, 23 Jul 2003 2:55 AM
Environment: ide: WSAD 5.0 os: win2000 bd: Oracle 9.2i
Description:
I try to use JTA transaction in websphere environment.=20
My Hibernate.cfg.xml is:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=09<property name=3D"show_sql">true</property>
=09<property name=3D"use_outer_join">true</property>
=09<property name=3D"jdbc.batch_size">0</property>
=09<property name=3D"query.substitutions">true 1, false 0, yes 'Y', no 'N'<=
/property>
=09<property name=3D"jndi.class">com.ibm.websphere.naming.WsnInitialContext=
Factory</property>
=09=09=09
=09<property name=3D"jndi.url">iiop://localhost:2809/</property>
=09<property name=3D"connection.datasource">jdbc/OracleDS</property>
=09<property name=3D"connection.username">easyejb</property>
=09<property name=3D"connection.password">easyejb</property>
=09<property name=3D"connection.provider_class">net.sf.hibernate.connection=
.DatasourceConnectionProvider</property>
=09<property name=3D"jdbc.use_streams_for_binary">true</property>
=09<property name=3D"dialect">net.sf.hibernate.dialect.OracleDialect</prope=
rty>
=09<property name=3D"transaction.factory_class">net.sf.hibernate.transactio=
n.JTATransactionFactory</property>
=09<property name=3D"transaction.manager_lookup_class">net.sf.hibernate.tra=
nsaction.WebSphereTransactionManagerLookup</property>
=09
=09
My trace:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
[22/07/03 18:11:59:188 CEST] 415086d4 DatasourceCon I net.sf.hibernate.conn=
ection.DatasourceConnectionProvider Using datasource: jdbc/OracleDS
[22/07/03 18:11:59:188 CEST] 415086d4 SessionFactor I net.sf.hibernate.impl=
.SessionFactoryImpl Use outer join fetching: true
[22/07/03 18:11:59:409 CEST] 415086d4 SessionFactor I net.sf.hibernate.impl=
.SessionFactoryImpl Use scrollable result sets: true
[22/07/03 18:11:59:409 CEST] 415086d4 SessionFactor I net.sf.hibernate.impl=
.SessionFactoryImpl Transaction strategy: net.sf.hibernate.transaction.JTA=
TransactionFactory
[22/07/03 18:11:59:419 CEST] 415086d4 NamingHelper I net.sf.hibernate.util=
.NamingHelper JNDI InitialContext properties:{java.naming.provider.url=3Di=
iop://localhost:2809/, java.naming.factory.initial=3Dcom.ibm.websphere.nami=
ng.WsnInitialContextFactory}
[22/07/03 18:11:59:429 CEST] 415086d4 JTATransactio I net.sf.hibernate.tran=
saction.JTATransactionFactory Locating TransactionManager using: net.sf.hi=
bernate.transaction.WebSphereTransactionManagerLookup
[22/07/03 18:11:59:439 CEST] 415086d4 WebSphereTran I net.sf.hibernate.tran=
saction.WebSphereTransactionManagerLookup getTransactionManager
[22/07/03 18:11:59:439 CEST] 415086d4 WebSphereTran I net.sf.hibernate.tran=
saction.WebSphereTransactionManagerLookup WebSphere 5
18:11:59,459 3706 FATAL FwormDaoException (<init>, 27 ) - =09=
- Dao - La cr=C3=A9ation du mapping pour hibernate a =C3=A9chou=C3=A9
18:11:59,469 3716 DEBUG FwormDaoException (<init>, 28 ) - net=
.sf.hibernate.HibernateException: Could not obtain WebSphere JTSXA instance=
: getTransactionManager
=3D> I don't find the com.ibm.ejcs.jts.jta.JTSXA class in WSAD 5.0. In fact=
i have only com.ibm.ejs.jts.jta.JTSXA in txPrivate.jar.=20
Do you have an idea of this problem ?
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
|
|
From: <leg...@at...> - 2003-07-24 05:55:18
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 24 Jul 2003 12:54 AM
This is not a bug in Hibernate. It is a bug in Firebird. Please see the Hibernate FAQ.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-211
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-211
Summary: Firebird Support
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Versions:
2.1
Assignee:
Reporter: Jason Hunter
Created: Wed, 23 Jul 2003 3:55 PM
Updated: Thu, 24 Jul 2003 12:54 AM
Environment: RedHat 9.0
Firebird 1.5 rc3
Description:
Trying to run the demo.sh file configured for an empty Firebird database gives me this error when I run the 'setup' command.
alter table edge add constraint FK2F6DBD35DE93 foreign key (sink) references vertex(vertex_id)
Unsuccessful: GDS Exception. unsuccessful metadata update
object VERTEX is in use
alter table edge add constraint FK2F6DBDCA90681B foreign key (source) references vertex(vertex_id)
Unsuccessful: GDS Exception. unsuccessful metadata update
object VERTEX is in use
The table creation works fine. I used the FirebirdDialect that I found in this bug system as my Dialect. And the firebird-jca-jdbc-driver from firebirds website.
---------------------------------------------------------------------
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
|
|
From: <leg...@at...> - 2003-07-23 20:56:02
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-211 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-211 Summary: Firebird Support Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.1 Assignee: Reporter: Jason Hunter Created: Wed, 23 Jul 2003 3:55 PM Updated: Wed, 23 Jul 2003 3:55 PM Environment: RedHat 9.0 Firebird 1.5 rc3 Description: Trying to run the demo.sh file configured for an empty Firebird database gives me this error when I run the 'setup' command. alter table edge add constraint FK2F6DBD35DE93 foreign key (sink) references vertex(vertex_id) Unsuccessful: GDS Exception. unsuccessful metadata update object VERTEX is in use alter table edge add constraint FK2F6DBDCA90681B foreign key (source) references vertex(vertex_id) Unsuccessful: GDS Exception. unsuccessful metadata update object VERTEX is in use The table creation works fine. I used the FirebirdDialect that I found in this bug system as my Dialect. And the firebird-jca-jdbc-driver from firebirds website. --------------------------------------------------------------------- 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 |
|
From: <leg...@at...> - 2003-07-23 14:24:02
|
The following issue has been updated:
Updater: Panagiotis Louridas (mailto:plo...@ya...)
Date: Wed, 23 Jul 2003 9:23 AM
Comment:
Thanks for your response Gavin,
I am attaching a simple test case illustrating the issue.
We have a Currency class and the following hierarchy:
BusinessTransaction <- Deal <- DummyDeal.
I attach simplified versions of the original classes with just some fields and their associated get/set methods.
After saving and committing a Currency and a DummyDeal, if we:
(1) query for the DummyDeal
(2) perform a change on it
(3) perform a query for the Currency we saved before
(4) flush and commit
the changes to DummyDeal are not persisted in the database.
This can be seen in the file DummyDealHibernateTest which is a JUnit test case. It containts a single test, testDummyDeal().
After unpacking the attached tarball:
* ant create-db creates the test database. hibernate.properties containts the connection parameters.
* ant test -Dtest.case=DummyDealHibernateTest runs the test.
In the beginning of build.xml file there are some path properties that I guess should be tweaked somewhat to suit your environment.
Changes:
Attachment changed to hibernate_report.tar.gz
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-209&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-209
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-209
Summary: FlushMode.AUTO problem in joined subclass hierarchy
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.0.1
Assignee:
Reporter: Panagiotis Louridas
Created: Tue, 22 Jul 2003 8:09 AM
Updated: Wed, 23 Jul 2003 9:23 AM
Environment: RedHat Linux 9.0, JVM 1.4.2
Description:
Suppose we have a class hierarchy
A <- B <- C.
In my case the class hierarchy is mapped as a joined-subclass hierarchy, but my observations may hold in general.
I use a Session with the default FlushMode setting (FlushMode.AUTO). I open the session, load an object of class B or C, perform some changes on it, do some queries and flush the session. When the session is flushed, only updates for the table pertaining to class A are issued by hibernate.
If I manually flush just before the queries hibernate performs fine, issuing the proper updates for tables B and C. The same happens when I manually flush at the end of the transaction, after the queries, but having set the Session's flush mode to FlushMode.NEVER.
---------------------------------------------------------------------
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
|
|
From: <leg...@at...> - 2003-07-23 07:57:02
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?= key=3DHB-210 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-210 Summary: JTA with Websphere 5.0 in WASD 5.0 environment Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components:=20 core Versions: 2.0.1 Assignee:=20 Reporter: gilles courtial Created: Wed, 23 Jul 2003 2:55 AM Updated: Wed, 23 Jul 2003 2:55 AM Environment: ide: WSAD 5.0 os: win2000 bd: Oracle 9.2i Description: I try to use JTA transaction in websphere environment.=20 My Hibernate.cfg.xml is: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =09<property name=3D"show_sql">true</property> =09<property name=3D"use_outer_join">true</property> =09<property name=3D"jdbc.batch_size">0</property> =09<property name=3D"query.substitutions">true 1, false 0, yes 'Y', no 'N'<= /property> =09<property name=3D"jndi.class">com.ibm.websphere.naming.WsnInitialContext= Factory</property> =09=09=09 =09<property name=3D"jndi.url">iiop://localhost:2809/</property> =09<property name=3D"connection.datasource">jdbc/OracleDS</property> =09<property name=3D"connection.username">easyejb</property> =09<property name=3D"connection.password">easyejb</property> =09<property name=3D"connection.provider_class">net.sf.hibernate.connection= .DatasourceConnectionProvider</property> =09<property name=3D"jdbc.use_streams_for_binary">true</property> =09<property name=3D"dialect">net.sf.hibernate.dialect.OracleDialect</prope= rty> =09<property name=3D"transaction.factory_class">net.sf.hibernate.transactio= n.JTATransactionFactory</property> =09<property name=3D"transaction.manager_lookup_class">net.sf.hibernate.tra= nsaction.WebSphereTransactionManagerLookup</property> =09 =09 My trace: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D [22/07/03 18:11:59:188 CEST] 415086d4 DatasourceCon I net.sf.hibernate.conn= ection.DatasourceConnectionProvider Using datasource: jdbc/OracleDS [22/07/03 18:11:59:188 CEST] 415086d4 SessionFactor I net.sf.hibernate.impl= .SessionFactoryImpl Use outer join fetching: true [22/07/03 18:11:59:409 CEST] 415086d4 SessionFactor I net.sf.hibernate.impl= .SessionFactoryImpl Use scrollable result sets: true [22/07/03 18:11:59:409 CEST] 415086d4 SessionFactor I net.sf.hibernate.impl= .SessionFactoryImpl Transaction strategy: net.sf.hibernate.transaction.JTA= TransactionFactory [22/07/03 18:11:59:419 CEST] 415086d4 NamingHelper I net.sf.hibernate.util= .NamingHelper JNDI InitialContext properties:{java.naming.provider.url=3Di= iop://localhost:2809/, java.naming.factory.initial=3Dcom.ibm.websphere.nami= ng.WsnInitialContextFactory} [22/07/03 18:11:59:429 CEST] 415086d4 JTATransactio I net.sf.hibernate.tran= saction.JTATransactionFactory Locating TransactionManager using: net.sf.hi= bernate.transaction.WebSphereTransactionManagerLookup [22/07/03 18:11:59:439 CEST] 415086d4 WebSphereTran I net.sf.hibernate.tran= saction.WebSphereTransactionManagerLookup getTransactionManager [22/07/03 18:11:59:439 CEST] 415086d4 WebSphereTran I net.sf.hibernate.tran= saction.WebSphereTransactionManagerLookup WebSphere 5 18:11:59,459 3706 FATAL FwormDaoException (<init>, 27 ) - =09= - Dao - La cr=C3=A9ation du mapping pour hibernate a =C3=A9chou=C3=A9 18:11:59,469 3716 DEBUG FwormDaoException (<init>, 28 ) - net= .sf.hibernate.HibernateException: Could not obtain WebSphere JTSXA instance= : getTransactionManager =3D> I don't find the com.ibm.ejcs.jts.jta.JTSXA class in WSAD 5.0. In fact= i have only com.ibm.ejs.jts.jta.JTSXA in txPrivate.jar.=20 Do you have an idea of this problem ? 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 |
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Tue, 22 Jul 2003 8:45 PM
map the property with insert="false" update="false"
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-208
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-208
Summary: ArrayIndexOutOfBoundsException is thrown when an attempt is make to save a polymorphic object (with discriminator column)
Type: Bug
Status: Closed
Priority: Critical
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.0.2
Assignee:
Reporter: Ferdinand Che
Created: Tue, 22 Jul 2003 8:03 AM
Updated: Tue, 22 Jul 2003 8:45 PM
Environment: XP, JBoss-3.2.1, JDK-1.4.1_02,MySQL-4.0.12-max-nt
Description:
An ArrayIndexOutOfBoundsException is thrown when an attempt is made to save (e.g. session.save(obj);session.flush();) that is a subclass (see mapping extract below). This exception is thrown at the point where the underlying preparedstatement is being populated with data following a net.sf.hibernate.type.StringType.set()-->line 22; following a call to EntityPersister.dehydrate() folowing an EntityPersister.insert().
On further inspection I have been able to determine that this is caused by a line in EntityPersister.generateInsertString() --> specifically: insert.addColumn(getDiscriminatorColumnName(), discriminatorSQLString); This line is only called because in this scenario we are handling polymorphic behaviour. the trouble is that this conflicts with the other underlying handling of object properties. The above call effectively overrides what what should appear in the resultant sql from something like (... (?,?,?,?) to an sql containing something like (?,?,'2',?). The trouble is then that when it comes to populating the prepared statement the there is one index more than is required and 'bang' ... an ArrayIndexOutOfBoundsException is thrown.
This can be 'fixed' by completely removing the line: insert.addColumn(getDiscriminatorColumnName(), discriminatorSQLString); and of cause the if statement associated with it Or making sure that the Property.isInsertable() returns false for all discriminator columns. I have used the former as a temporary fix until I get further feedback from the hibernate people.
The following is an example extract from mapping file that will trigger this issue:
<class name="com.mycom.data.ITestItem table="ITEMS">
<id name="code" column="CODE" type="string" unsaved-value="any">
<generator class="assigned">
</generator>
</id>
<discriminator column="TYPE" type="string" />
<property name="name" type="java.lang.String" column="NAME" not-null="true" />
<property name="desc" type="java.lang.String" column="DESCR" not-null="true" />
<property name="type" type="int" column="TYPE" not-null="true" />
<subclass name="com.mycom.data.TestItemType1" discriminator-value="1" />
<subclass name="com.mycom.data.TestItemType2" discriminator-value="2" />
</class>
---------------------------------------------------------------------
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
|
|
From: <leg...@at...> - 2003-07-23 01:03:01
|
The following comment has been added to this issue:
Author: Gavin King
Created: Tue, 22 Jul 2003 8:02 PM
Body:
I'm quite skeptical about this one, and certainly you will need to submit a test case to help me reproduce it.
Submit the test as a _very_ simple main() method that isolates the problem.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-209
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-209
Summary: FlushMode.AUTO problem in joined subclass hierarchy
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.0.1
Assignee:
Reporter: Panagiotis Louridas
Created: Tue, 22 Jul 2003 8:09 AM
Updated: Tue, 22 Jul 2003 8:09 AM
Environment: RedHat Linux 9.0, JVM 1.4.2
Description:
Suppose we have a class hierarchy
A <- B <- C.
In my case the class hierarchy is mapped as a joined-subclass hierarchy, but my observations may hold in general.
I use a Session with the default FlushMode setting (FlushMode.AUTO). I open the session, load an object of class B or C, perform some changes on it, do some queries and flush the session. When the session is flushed, only updates for the table pertaining to class A are issued by hibernate.
If I manually flush just before the queries hibernate performs fine, issuing the proper updates for tables B and C. The same happens when I manually flush at the end of the transaction, after the queries, but having set the Session's flush mode to FlushMode.NEVER.
---------------------------------------------------------------------
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
|
|
From: <leg...@at...> - 2003-07-23 01:01:05
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Tue, 22 Jul 2003 8:00 PM
You will have to take this to sf.net support.
Theres nothing I can do.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-207
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-207
Summary: CVS login is refused
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Assignee:
Reporter: Bill Zhao
Created: Mon, 21 Jul 2003 3:26 PM
Updated: Tue, 22 Jul 2003 8:00 PM
Environment: window 2000
Description:
I try to get cvs source. But after I type
cvs -d:pserver:ano...@cv...:/cvsroot/hibernate login
and hit enter after "password:" prompt, the connection is refused so I can't proceed.
Thank you,
Bill Zhao
---------------------------------------------------------------------
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
|
|
From: <leg...@at...> - 2003-07-22 16:07:05
|
The following comment has been added to this issue:
Author: Panagiotis Louridas
Created: Tue, 22 Jul 2003 11:06 AM
Body:
After changing hibernate's log level to DEBUG I see some of the subclasses' fields as dirty. It then seems that whenever, after marking these fields as dirty, hibernate outputs that "Dont need to execute flush" and leaves it for later on, when the time comes it has forgotten the subclasses' fields.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-209
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-209
Summary: FlushMode.AUTO problem in joined subclass hierarchy
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.0.1
Assignee:
Reporter: Panagiotis Louridas
Created: Tue, 22 Jul 2003 8:09 AM
Updated: Tue, 22 Jul 2003 8:09 AM
Environment: RedHat Linux 9.0, JVM 1.4.2
Description:
Suppose we have a class hierarchy
A <- B <- C.
In my case the class hierarchy is mapped as a joined-subclass hierarchy, but my observations may hold in general.
I use a Session with the default FlushMode setting (FlushMode.AUTO). I open the session, load an object of class B or C, perform some changes on it, do some queries and flush the session. When the session is flushed, only updates for the table pertaining to class A are issued by hibernate.
If I manually flush just before the queries hibernate performs fine, issuing the proper updates for tables B and C. The same happens when I manually flush at the end of the transaction, after the queries, but having set the Session's flush mode to FlushMode.NEVER.
---------------------------------------------------------------------
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
|
|
From: <leg...@at...> - 2003-07-22 14:58:02
|
The following comment has been added to this issue:
Author: Panagiotis Louridas
Created: Tue, 22 Jul 2003 9:57 AM
Body:
FlushMode.AUTO works OK if before flushing at the end of the transaction a Session.save(anotherObject) operation is performed; hibernate then issues the correct UPDATE statements just after the INSERT statement for anotherObject.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-209
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-209
Summary: FlushMode.AUTO problem in joined subclass hierarchy
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.0.1
Assignee:
Reporter: Panagiotis Louridas
Created: Tue, 22 Jul 2003 8:09 AM
Updated: Tue, 22 Jul 2003 8:09 AM
Environment: RedHat Linux 9.0, JVM 1.4.2
Description:
Suppose we have a class hierarchy
A <- B <- C.
In my case the class hierarchy is mapped as a joined-subclass hierarchy, but my observations may hold in general.
I use a Session with the default FlushMode setting (FlushMode.AUTO). I open the session, load an object of class B or C, perform some changes on it, do some queries and flush the session. When the session is flushed, only updates for the table pertaining to class A are issued by hibernate.
If I manually flush just before the queries hibernate performs fine, issuing the proper updates for tables B and C. The same happens when I manually flush at the end of the transaction, after the queries, but having set the Session's flush mode to FlushMode.NEVER.
---------------------------------------------------------------------
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
|
The following comment has been added to this issue:
Author: Ferdinand Che
Created: Tue, 22 Jul 2003 8:15 AM
Body:
An alternative solution would be not to include the discriminator column in the list of properties. Presently the property associated with the dicriminator column also has to be included as a property in the mappings file - otherwise, it is not possible to handle this field as a persistent field/property.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-208
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-208
Summary: ArrayIndexOutOfBoundsException is thrown when an attempt is make to save a polymorphic object (with discriminator column)
Type: Bug
Status: Unassigned
Priority: Critical
Project: Hibernate2
Components:
core
Versions:
2.0.2
Assignee:
Reporter: Ferdinand Che
Created: Tue, 22 Jul 2003 8:03 AM
Updated: Tue, 22 Jul 2003 8:03 AM
Environment: XP, JBoss-3.2.1, JDK-1.4.1_02,MySQL-4.0.12-max-nt
Description:
An ArrayIndexOutOfBoundsException is thrown when an attempt is made to save (e.g. session.save(obj);session.flush();) that is a subclass (see mapping extract below). This exception is thrown at the point where the underlying preparedstatement is being populated with data following a net.sf.hibernate.type.StringType.set()-->line 22; following a call to EntityPersister.dehydrate() folowing an EntityPersister.insert().
On further inspection I have been able to determine that this is caused by a line in EntityPersister.generateInsertString() --> specifically: insert.addColumn(getDiscriminatorColumnName(), discriminatorSQLString); This line is only called because in this scenario we are handling polymorphic behaviour. the trouble is that this conflicts with the other underlying handling of object properties. The above call effectively overrides what what should appear in the resultant sql from something like (... (?,?,?,?) to an sql containing something like (?,?,'2',?). The trouble is then that when it comes to populating the prepared statement the there is one index more than is required and 'bang' ... an ArrayIndexOutOfBoundsException is thrown.
This can be 'fixed' by completely removing the line: insert.addColumn(getDiscriminatorColumnName(), discriminatorSQLString); and of cause the if statement associated with it Or making sure that the Property.isInsertable() returns false for all discriminator columns. I have used the former as a temporary fix until I get further feedback from the hibernate people.
The following is an example extract from mapping file that will trigger this issue:
<class name="com.mycom.data.ITestItem table="ITEMS">
<id name="code" column="CODE" type="string" unsaved-value="any">
<generator class="assigned">
</generator>
</id>
<discriminator column="TYPE" type="string" />
<property name="name" type="java.lang.String" column="NAME" not-null="true" />
<property name="desc" type="java.lang.String" column="DESCR" not-null="true" />
<property name="type" type="int" column="TYPE" not-null="true" />
<subclass name="com.mycom.data.TestItemType1" discriminator-value="1" />
<subclass name="com.mycom.data.TestItemType2" discriminator-value="2" />
</class>
---------------------------------------------------------------------
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
|
|
From: <leg...@at...> - 2003-07-22 13:10:02
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-209 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-209 Summary: FlushMode.AUTO problem in joined subclass hierarchy Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.0.1 Assignee: Reporter: Panagiotis Louridas Created: Tue, 22 Jul 2003 8:09 AM Updated: Tue, 22 Jul 2003 8:09 AM Environment: RedHat Linux 9.0, JVM 1.4.2 Description: Suppose we have a class hierarchy A <- B <- C. In my case the class hierarchy is mapped as a joined-subclass hierarchy, but my observations may hold in general. I use a Session with the default FlushMode setting (FlushMode.AUTO). I open the session, load an object of class B or C, perform some changes on it, do some queries and flush the session. When the session is flushed, only updates for the table pertaining to class A are issued by hibernate. If I manually flush just before the queries hibernate performs fine, issuing the proper updates for tables B and C. The same happens when I manually flush at the end of the transaction, after the queries, but having set the Session's flush mode to FlushMode.NEVER. --------------------------------------------------------------------- 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 |
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-208 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-208 Summary: ArrayIndexOutOfBoundsException is thrown when an attempt is make to save a polymorphic object (with discriminator column) Type: Bug Status: Unassigned Priority: Critical Project: Hibernate2 Components: core Versions: 2.0.2 Assignee: Reporter: Ferdinand Che Created: Tue, 22 Jul 2003 8:03 AM Updated: Tue, 22 Jul 2003 8:03 AM Environment: XP, JBoss-3.2.1, JDK-1.4.1_02,MySQL-4.0.12-max-nt Description: An ArrayIndexOutOfBoundsException is thrown when an attempt is made to save (e.g. session.save(obj);session.flush();) that is a subclass (see mapping extract below). This exception is thrown at the point where the underlying preparedstatement is being populated with data following a net.sf.hibernate.type.StringType.set()-->line 22; following a call to EntityPersister.dehydrate() folowing an EntityPersister.insert(). On further inspection I have been able to determine that this is caused by a line in EntityPersister.generateInsertString() --> specifically: insert.addColumn(getDiscriminatorColumnName(), discriminatorSQLString); This line is only called because in this scenario we are handling polymorphic behaviour. the trouble is that this conflicts with the other underlying handling of object properties. The above call effectively overrides what what should appear in the resultant sql from something like (... (?,?,?,?) to an sql containing something like (?,?,'2',?). The trouble is then that when it comes to populating the prepared statement the there is one index more than is required and 'bang' ... an ArrayIndexOutOfBoundsException is thrown. This can be 'fixed' by completely removing the line: insert.addColumn(getDiscriminatorColumnName(), discriminatorSQLString); and of cause the if statement associated with it Or making sure that the Property.isInsertable() returns false for all discriminator columns. I have used the former as a temporary fix until I get further feedback from the hibernate people. The following is an example extract from mapping file that will trigger this issue: <class name="com.mycom.data.ITestItem table="ITEMS"> <id name="code" column="CODE" type="string" unsaved-value="any"> <generator class="assigned"> </generator> </id> <discriminator column="TYPE" type="string" /> <property name="name" type="java.lang.String" column="NAME" not-null="true" /> <property name="desc" type="java.lang.String" column="DESCR" not-null="true" /> <property name="type" type="int" column="TYPE" not-null="true" /> <subclass name="com.mycom.data.TestItemType1" discriminator-value="1" /> <subclass name="com.mycom.data.TestItemType2" discriminator-value="2" /> </class> --------------------------------------------------------------------- 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 |
|
From: <leg...@at...> - 2003-07-21 20:27:43
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-207 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-207 Summary: CVS login is refused Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Assignee: Reporter: Bill Zhao Created: Mon, 21 Jul 2003 3:26 PM Updated: Mon, 21 Jul 2003 3:26 PM Environment: window 2000 Description: I try to get cvs source. But after I type cvs -d:pserver:ano...@cv...:/cvsroot/hibernate login and hit enter after "password:" prompt, the connection is refused so I can't proceed. Thank you, Bill Zhao --------------------------------------------------------------------- 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 |
|
From: <leg...@at...> - 2003-07-21 17:42:43
|
The following issue has been updated:
Updater: Matt Hall (mailto:ma...@us...)
Date: Mon, 21 Jul 2003 12:40 PM
Comment:
The utility that will load any hibernate object from an HttpServlet request as long as those constants are present. I've put it in the net.sf.hibernate.tools package for now.
Changes:
Attachment changed to HttpFormUtil.java
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-206&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-206
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-206
Summary: Fieldname constants generator, and Http form loader utility.
Type: Improvement
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
toolset
Versions:
2.0.2
Assignee:
Reporter: Matt Hall
Created: Mon, 21 Jul 2003 12:38 PM
Updated: Mon, 21 Jul 2003 12:40 PM
Description:
This is a modification to BasicRenderer to generate a series of constants at the top of generated hibernate data objects that represent each property contained in the object. Looks something like:
public static String FIELD_ID = "com.whatever.Category.id";
public static String FIELD_TYPE = "com.whatever.Category.type";
public static String FIELD_TITLE = "com.whateverCategory.title";
If you then use these constants to name your fields in a web form, you can use the other part of this submissions, HttpFormUtil, to load your hibernate data objects from an HttpServletRequest automatically via reflection.
---------------------------------------------------------------------
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
|
|
From: <leg...@at...> - 2003-07-21 17:40:43
|
The following issue has been updated:
Updater: Matt Hall (mailto:ma...@us...)
Date: Mon, 21 Jul 2003 12:39 PM
Comment:
BasicRenderer diff used to generate class property constants.
Changes:
Attachment changed to patch.txt
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-206&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-206
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-206
Summary: Fieldname constants generator, and Http form loader utility.
Type: Improvement
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
toolset
Versions:
2.0.2
Assignee:
Reporter: Matt Hall
Created: Mon, 21 Jul 2003 12:38 PM
Updated: Mon, 21 Jul 2003 12:39 PM
Description:
This is a modification to BasicRenderer to generate a series of constants at the top of generated hibernate data objects that represent each property contained in the object. Looks something like:
public static String FIELD_ID = "com.whatever.Category.id";
public static String FIELD_TYPE = "com.whatever.Category.type";
public static String FIELD_TITLE = "com.whateverCategory.title";
If you then use these constants to name your fields in a web form, you can use the other part of this submissions, HttpFormUtil, to load your hibernate data objects from an HttpServletRequest automatically via reflection.
---------------------------------------------------------------------
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
|
|
From: <leg...@at...> - 2003-07-21 17:38:47
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-206 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-206 Summary: Fieldname constants generator, and Http form loader utility. Type: Improvement Status: Unassigned Priority: Major Project: Hibernate2 Components: toolset Versions: 2.0.2 Assignee: Reporter: Matt Hall Created: Mon, 21 Jul 2003 12:38 PM Updated: Mon, 21 Jul 2003 12:38 PM Description: This is a modification to BasicRenderer to generate a series of constants at the top of generated hibernate data objects that represent each property contained in the object. Looks something like: public static String FIELD_ID = "com.whatever.Category.id"; public static String FIELD_TYPE = "com.whatever.Category.type"; public static String FIELD_TITLE = "com.whateverCategory.title"; If you then use these constants to name your fields in a web form, you can use the other part of this submissions, HttpFormUtil, to load your hibernate data objects from an HttpServletRequest automatically via reflection. --------------------------------------------------------------------- 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 |
|
From: <leg...@at...> - 2003-07-19 00:48:43
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Fri, 18 Jul 2003 7:47 PM
It isn't meant to be included. We are trying to keep the download small.
It -is- in the CVS checkout.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-205
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-205
Summary: Current 2.0.1 distribution doesn't contain hsqldb.jar driver
Type: Bug
Status: Closed
Priority: Trivial
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: Slava Imeshev
Created: Fri, 18 Jul 2003 1:01 PM
Updated: Fri, 18 Jul 2003 7:47 PM
Environment: hibernate-2.0.1.zip @ 07/17/2003
Description:
hibernate-2.0.1.zip @ 07/17/2003 doesn't have hsqldb.jar thought the build.xml refers to it. As a result "build junit" command fails as in
[junit] INFO: Hibernate connection pool size: 1
[junit] Jul 18, 2003 10:45:24 AM net.sf.hibernate.connection.DriverManagerConnectionProvider configure
[junit] SEVERE: JDBC Driver class not found: org.hsqldb.jdbcDriver
[junit] net.sf.hibernate.HibernateException: JDBC Driver class not found: org.hsqldb.jdbcDriver
[junit] at net.sf.hibernate.connection.DriverManagerConnectionProvider.configure(DriverManagerConnecti
onProvider.java:57)
[junit] at net.sf.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProvi
derFactory.java:83)
[junit] at net.sf.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:109)
[junit] at net.sf.hibernate.tool.hbm2ddl.SchemaExport.create(SchemaExport.java:78)
[junit] at net.sf.hibernate.test.TestCase.exportSchema(TestCase.java:32)
[junit] at net.sf.hibernate.test.SQLFunctionsTest.suite(SQLFunctionsTest.java:277)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[junit] at java.lang.reflect.Method.invoke(Method.java:324)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.<init>(JUnitTestRunner.java:25
7)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.<init>(JUnitTestRunner.java:21
0)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:532)
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
[junit] Jul 18, 2003 10:45:24 AM net.sf.hibernate.connection.DriverManagerConnectionProvider close
[junit] INFO: cleaning up connection pool: null
[junit] TEST net.sf.hibernate.test.SQLFunctionsTest FAILED
---------------------------------------------------------------------
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
|
|
From: <leg...@at...> - 2003-07-18 18:11:57
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-205 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-205 Summary: Current 2.0.1 distribution doesn't contain hsqldb.jar driver Type: Bug Status: Unassigned Priority: Trivial Project: Hibernate2 Components: core Versions: 2.0.1 Assignee: Reporter: Slava Imeshev Created: Fri, 18 Jul 2003 1:01 PM Updated: Fri, 18 Jul 2003 1:01 PM Environment: hibernate-2.0.1.zip @ 07/17/2003 Description: hibernate-2.0.1.zip @ 07/17/2003 doesn't have hsqldb.jar thought the build.xml refers to it. As a result "build junit" command fails as in [junit] INFO: Hibernate connection pool size: 1 [junit] Jul 18, 2003 10:45:24 AM net.sf.hibernate.connection.DriverManagerConnectionProvider configure [junit] SEVERE: JDBC Driver class not found: org.hsqldb.jdbcDriver [junit] net.sf.hibernate.HibernateException: JDBC Driver class not found: org.hsqldb.jdbcDriver [junit] at net.sf.hibernate.connection.DriverManagerConnectionProvider.configure(DriverManagerConnecti onProvider.java:57) [junit] at net.sf.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProvi derFactory.java:83) [junit] at net.sf.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:109) [junit] at net.sf.hibernate.tool.hbm2ddl.SchemaExport.create(SchemaExport.java:78) [junit] at net.sf.hibernate.test.TestCase.exportSchema(TestCase.java:32) [junit] at net.sf.hibernate.test.SQLFunctionsTest.suite(SQLFunctionsTest.java:277) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] at java.lang.reflect.Method.invoke(Method.java:324) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.<init>(JUnitTestRunner.java:25 7) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.<init>(JUnitTestRunner.java:21 0) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:532) [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec [junit] Jul 18, 2003 10:45:24 AM net.sf.hibernate.connection.DriverManagerConnectionProvider close [junit] INFO: cleaning up connection pool: null [junit] TEST net.sf.hibernate.test.SQLFunctionsTest FAILED --------------------------------------------------------------------- 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 |
|
From: <leg...@at...> - 2003-07-18 06:10:44
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Fri, 18 Jul 2003 1:09 AM
I have made a slightly different fix to CVS.
Please try it out, check that it works for you.
Thanks.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-202
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-202
Summary: Fetched collections are not cached
Type: Improvement
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Fix Fors:
2.0.2
Versions:
2.0 final
Assignee: Gavin King
Reporter: Peter Fassev
Created: Wed, 16 Jul 2003 1:29 PM
Updated: Fri, 18 Jul 2003 1:09 AM
Description:
If a collection is fetched together with an owner class using a query with the "left outher join fetch" construct, then the created collection is not added to the cache.
A tried a simple improvement and changed the PersistentCollectionType.getCollection() to add the collection to the cache:
....
PersistentCollection collection = session.endLoafingCollection(persister, id);
if (collection != null) {
// this is the patch...
persister.cache(id, collection, session);
return collection.getCachedValue();
}
...
I am not shure if this is the right place for the patch and if this patch is enough, so a am ascing for improvement.
---------------------------------------------------------------------
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
|
|
From: <leg...@at...> - 2003-07-18 05:29:43
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Fri, 18 Jul 2003 12:28 AM
Actually, it is even possible at mapping-file level, using the outer-join attribute. Silly me.
Closing this, because both options already exist!
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-196
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-196
Summary: Ability to specify lazy for many-to-one associations
Type: New Feature
Status: Closed
Priority: Major
Resolution: DUPLICATE
Project: Hibernate2
Components:
core
Assignee:
Reporter: Andrea Aime
Created: Wed, 16 Jul 2003 3:00 AM
Updated: Fri, 18 Jul 2003 12:28 AM
Description:
Using proxy to specify delayed loading of a class is a bit unflexible if more than one class has an association with it. It would be nicer to have the ability to specify lazy loading on the many to one side, since different navigation paths can have different requirements. (The ability to specify what to load in the HQL would be nicer, but probably more difficult to code...)
---------------------------------------------------------------------
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
|
|
From: <leg...@at...> - 2003-07-18 05:25:43
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Fri, 18 Jul 2003 12:24 AM
I already fixed this one in CVS. Try getting the latest code.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-204
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-204
Summary: Problem with Query and LIMIT (HSQL)
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.0.2
Versions:
2.0.1
Assignee:
Reporter: Sebastien Guimont
Created: Thu, 17 Jul 2003 9:15 AM
Updated: Fri, 18 Jul 2003 12:24 AM
Description:
Reference: http://sourceforge.net/forum/message.php?msg_id=2086382
I use HyperSQL 1.7.2 alpha M.
/** Code sampl **/
hibernateSession = getSession(session);
Query hibernateQuery = hibernateSession.createQuery(query);
for (int i = 0; i < params.length; i++) {
hibernateQuery.setParameter(i, params[i]);
}
hibernateQuery.setFirstResult(startRow);
hibernateQuery.setMaxResults(resultSize);
results = hibernateQuery.list();
/** Exception **/
When I call the list method I got this exception:
Could not execute query: Wrong data type: LIMIT n m in statement [select limit 'CA' 1 referenceValue.REF_VAL_ID as REF_VAL_ID, referenceValue.CITY_CNTRY_ID as CITY_CN11_, referenceValue.CITY_STATEPROV_ID as CITY_ST12_, referenceValue.UPID as UPID, referenceValue.CD as CD, referenceValue.CREATED as CREATED, referenceValue.CREATED_BY as CREATED_BY, referenceValue.LAST_UPD as LAST_UPD, referenceValue.LAST_UPD_BY as LAST_UPD8_, referenceValue.REF_ORDER as REF_ORDER, referenceValue.DESC_ID as DESC_ID from REF_VAL referenceValue, REF_VAL countryr0_, DESCRIPT descript1_ where referenceValue.TYP='SYS_CITY' and referenceValue.DESC_ID=descript1_.DESC_ID and (((countryr0_.CD=25 and referenceValue.CITY_CNTRY_ID=countryr0_.REF_VAL_ID))) order by descript1_.DEFAULT_DESC asc]
It looks like the parameters list for the prepared statement are not ordered correctly.
---------------------------------------------------------------------
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
|
|
From: <leg...@at...> - 2003-07-18 05:01:44
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Fri, 18 Jul 2003 12:00 AM
Thanks. I fixed this in CVS. Please try it out.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-200
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-200
Summary: subclass is not used when using query by criteria API
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Fix Fors:
2.0.2
Versions:
2.0.1
Assignee: Gavin King
Reporter: Machiel Groeneveld
Created: Wed, 16 Jul 2003 9:49 AM
Updated: Fri, 18 Jul 2003 12:00 AM
Description:
I have a problem with subclasses. For example an abstract Parent as the parent and Child1 and Child2 as subclasses of Parent.
When I use this:
Criteria criteria = sessie.createCriteria(Child2 .class);
criteria.add(anExpression);
Then criteria.list() gives me a list containing all subclasses of Parent which match the gives expressions.
I snippet from the config file (edited):
<class "Parent" table="table">
<id name="id" column="uid" type="long" unsaved-value="0">
<generator class="native"/>
</id>
<discriminator column="klasse" type="string"/>
<property name="message"/>
<subclass name="Child1"/>
<subclass name="Child2"/>
---------------------------------------------------------------------
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
|
93 messages has been excluded from this view by a project administrator.
