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...> - 2004-01-06 05:10:15
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-608 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-608 Summary: Allow criteria queries on abstract classes from table-per-concrete-class mappings Type: Improvement Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.1.1 Assignee: Reporter: Shorn Tolley Created: Mon, 5 Jan 2004 11:09 PM Updated: Mon, 5 Jan 2004 11:09 PM Environment: Hibernate 2.1.1, Ingres 2.6 SP2 Description: I'm mapping a part of my domain model using the table-per-concrete-class strategy. I need to use hibernate's "implicit polymorphism" feature to query on the abstract class in the hierarchy to return specific instances of the class regardless of their concrete type. I can do it using the HQL query mechanism (as long as I fully qualify the name of the abstract class), but when I try to use the Criteria query mechanism I get a mapping exception with a "No persisten for: <Classname>" type message. The relevant section in the 2.1.1 documentation is "Chapter 16 Inheritance mappings". I posted my problem in a forum topic and am raising this issue as a result of instructions given by the hibernate team: http://forum.hibernate.org/viewtopic.php?t=926608 Even if you don't want to implement the functionality I'm talking about (or want to delay it's implementation for a while), it might be a good idea to update the table in the limitations section for the "polymorphic load()/get()" column that says "use a query" to note that you can't use a criteria query. It also might be worth mentioning that you need to use the fully qualified classname of the abstract class in the HQL query. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2004-01-06 02:10:15
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-607 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-607 Summary: <composite-element> does not accept <any> in it Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.1 Assignee: Reporter: Sankara N Alwar Created: Mon, 5 Jan 2004 8:10 PM Updated: Mon, 5 Jan 2004 8:10 PM Environment: Hibernate 2.1 Final, Oralce 8.1.7, Windows 2000 Description: <composite-element> does not accept <any> in it. I get the following error if I add any inside <composite-element>: ERROR [Thread-4] 2003-12-23 23:42:18,735 - net.sf.hibernate.util.XMLHelper - Error parsing XML: XML InputStream(180) The content of element type "composite-element" must match "(parent?,(property|many-to-one|nested-composite-element)*)". Even I verified the dtd, it doesn't accept it. Here is my mapping: <set name="Persons" table="groupmembership" lazy="true" inverse="true"> <key column="group_id"/> <composite-element class="net.sf.hibernate.examples.quickstart.GroupMembership"> <any name="members" id-type="string" meta-type="net.sf.hibernate.examples.quickstart.GroupTypeMapper"> <column name="child_type"/> <column name="child_id"/> </any> </composite-element> </set> --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2004-01-05 23:30:06
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-606 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-606 Summary: Add nested component in Query By Example Type: Improvement Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.1.1 Assignee: Reporter: Emmanuel Bernard Created: Mon, 5 Jan 2004 4:49 PM Updated: Mon, 5 Jan 2004 4:49 PM Environment: Head of 2.1 branch 01/06/2003 00h00 GMT+1 Description: Add nested component parsing during Query By Example. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2004-01-05 23:23:17
|
The following comment has been added to this issue:
Author: Edina Pimp
Created: Mon, 5 Jan 2004 4:31 PM
Body:
One case would be where I'm using a ThreadLocal Session object. The session may have been opened earlier in the callstack, and now I need to add an interceptor to handle callbacks for my specific domain area.
I could come up with others, but that's the one that sticks out the most to me.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-603
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-603
Summary: Add a hook to get at configured Interceptor on Session
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Versions:
2.1.1
Assignee:
Reporter: Edina Pimp
Created: Mon, 5 Jan 2004 11:23 AM
Updated: Mon, 5 Jan 2004 4:31 PM
Description:
It would be nice to have a handle to the configured Interceptor on the Session. Having one would allow runtime plugability of different Interceptors.
---------------------------------------------------------------------
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...> - 2004-01-05 22:52:15
|
The following issue has been updated:
Updater: Emmanuel Bernard (mailto:epb...@us...)
Date: Mon, 5 Jan 2004 4:50 PM
Comment:
Eclipse diff -u from root
Changes:
Attachment changed to qbenestedcomponent.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-606&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-606
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-606
Summary: Add nested component in Query By Example
Type: Improvement
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1.1
Assignee:
Reporter: Emmanuel Bernard
Created: Mon, 5 Jan 2004 4:49 PM
Updated: Mon, 5 Jan 2004 4:50 PM
Environment: Head of 2.1 branch 01/06/2003 00h00 GMT+1
Description:
Add nested component parsing during Query By Example.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2004-01-05 22:42:16
|
The following issue has been updated:
Updater: Michael Gloegl (mailto:gl...@ok...)
Date: Mon, 5 Jan 2004 4:42 PM
Changes:
Attachment changed to config_duplicate_import.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-605&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-605
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-605
Summary: No "duplicate import" error on DTD violation - includes Patch
Type: Improvement
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1.1
Assignee:
Reporter: Michael Gloegl
Created: Mon, 5 Jan 2004 4:41 PM
Updated: Mon, 5 Jan 2004 4:42 PM
Environment: Hibernate 2.1.1
Description:
When a mapping document violates the DTD, Hibernate will log the error and nertheless add the mapping to the session factory. Later on a "duplicate import" error gets produced when Hibernate tries to add the same mapping again. This patch intends to solve this by not adding the mapping if there is an error during parsing.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2004-01-05 22:42:16
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-605 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-605 Summary: No "duplicate import" error on DTD violation - includes Patch Type: Improvement Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.1.1 Assignee: Reporter: Michael Gloegl Created: Mon, 5 Jan 2004 4:41 PM Updated: Mon, 5 Jan 2004 4:41 PM Environment: Hibernate 2.1.1 Description: When a mapping document violates the DTD, Hibernate will log the error and nertheless add the mapping to the session factory. Later on a "duplicate import" error gets produced when Hibernate tries to add the same mapping again. This patch intends to solve this by not adding the mapping if there is an error during parsing. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2004-01-05 22:16:15
|
The following comment has been added to this issue:
Author: Emmanuel Bernard
Created: Mon, 5 Jan 2004 4:15 PM
Body:
Actually there is a mismatch between a not-null column and a not-null property. Hibernate is probably missing the first concept.
Checks could be done in the JAVA level for <subclass> properties.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-602
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-602
Summary: hbm2ddl create unexpected not-null constraints on <subclass>
Type: Bug
Status: Closed
Priority: Minor
Resolution: WON'T FIX
Project: Hibernate2
Components:
core
Versions:
2.1.1
Assignee:
Reporter: Emmanuel Bernard
Created: Mon, 5 Jan 2004 10:37 AM
Updated: Mon, 5 Jan 2004 4:15 PM
Description:
When declaring not-null property into <subclass> A and not in it's superclass (SuperA), then SuperA cannot be insert (constraints violation).
This is not expected.
---------------------------------------------------------------------
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...> - 2004-01-05 21:25:16
|
Message: The following issue has been resolved as CANNOT REPRODUCE. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-600 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-600 Summary: hbm2java can't mapping joined-subclasses correctly which are in independent files from the file of the super class. Type: Bug Status: Resolved Priority: Critical Resolution: CANNOT REPRODUCE Project: Hibernate2 Components: toolset Versions: 2.1 Assignee: Max Rydahl Andersen Reporter: Eileen Huan Created: Mon, 5 Jan 2004 6:16 AM Updated: Mon, 5 Jan 2004 3:21 PM Environment: Apache Ant version 1.5.4 compiled on August 12 2003 Buildfile: build.xml Detected Java version: 1.4 in: C:\j2sdk1.4.2_03\jre Detected OS: Windows 2000 Description: I have posted my problem on hibernate forum as "http://forum.hibernate.org/viewtopic.php?t=926802&sid=a04167043b0b8cd84c79b9d16b332a7e". --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2004-01-05 21:23:15
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Mon, 5 Jan 2004 3:20 PM
Body:
When i just run hbm2java with CimClass.hbm.xml Resource.hbm.xml CimProperty.hbm.xml BusinessUnit.hbm.xml as it's arguments i get 4 corresponding java files without a problem. And here BusinessUnit.hbm.xml extends Resource.hbm.xml
Your build.xml does not run out-of-da-box and require a ton of external libs (xdoclet etc.) that I don't have the time to get + it does not make the sample simple.
Make a smaller example that fails please.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-600
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-600
Summary: hbm2java can't mapping joined-subclasses correctly which are in independent files from the file of the super class.
Type: Bug
Status: Open
Priority: Critical
Project: Hibernate2
Components:
toolset
Versions:
2.1
Assignee: Max Rydahl Andersen
Reporter: Eileen Huan
Created: Mon, 5 Jan 2004 6:16 AM
Updated: Mon, 5 Jan 2004 3:20 PM
Environment: Apache Ant version 1.5.4 compiled on August 12 2003
Buildfile: build.xml
Detected Java version: 1.4 in: C:\j2sdk1.4.2_03\jre
Detected OS: Windows 2000
Description:
I have posted my problem on hibernate forum as "http://forum.hibernate.org/viewtopic.php?t=926802&sid=a04167043b0b8cd84c79b9d16b332a7e".
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2004-01-05 20:49:15
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Mon, 5 Jan 2004 2:48 PM
Body:
Why do you want to change interceptors during the lifetime of a session ? (curious to get a valid usecase for it ;)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-603
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-603
Summary: Add a hook to get at configured Interceptor on Session
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Versions:
2.1.1
Assignee:
Reporter: Edina Pimp
Created: Mon, 5 Jan 2004 11:23 AM
Updated: Mon, 5 Jan 2004 2:48 PM
Description:
It would be nice to have a handle to the configured Interceptor on the Session. Having one would allow runtime plugability of different Interceptors.
---------------------------------------------------------------------
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...> - 2004-01-05 20:47:15
|
Message:
The following issue has been closed.
Resolver: Max Rydahl Andersen
Date: Mon, 5 Jan 2004 2:47 PM
Then don't declare it as not-null!
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-602
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-602
Summary: hbm2ddl create unexpected not-null constraints on <subclass>
Type: Bug
Status: Closed
Priority: Minor
Resolution: WON'T FIX
Project: Hibernate2
Components:
core
Versions:
2.1.1
Assignee:
Reporter: Emmanuel Bernard
Created: Mon, 5 Jan 2004 10:37 AM
Updated: Mon, 5 Jan 2004 2:47 PM
Description:
When declaring not-null property into <subclass> A and not in it's superclass (SuperA), then SuperA cannot be insert (constraints violation).
This is not expected.
---------------------------------------------------------------------
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...> - 2004-01-05 17:52:19
|
The following issue has been updated:
Updater: Matt Ho (mailto:ma...@xt...)
Date: Mon, 5 Jan 2004 11:51 AM
Changes:
Attachment changed to Account.java
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-604&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-604
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-604
Summary: problems upgrading using a criteria with postgresql 7.4
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1.1
Assignee:
Reporter: Matt Ho
Created: Mon, 5 Jan 2004 11:49 AM
Updated: Mon, 5 Jan 2004 11:51 AM
Environment: sun jdk 1.4.2_03, postgresql 7.4, hibernate 2.1.1
Description:
Using Hibernate 2.1.1 and PostgreSQL 7.4, I'm trying to use the Criteria API to do a SELECT ... FOR UPDATE on a given table. If I include a
criteria.setLockMode(LockMode.UPGRADE);
I get the following Exception
132531 [tcpConnection-8080-2] WARN util.JDBCExceptionReporter - SQL Error: 0, SQLState: 0A000
132531 [tcpConnection-8080-2] ERROR util.JDBCExceptionReporter - ERROR: DECLARE CURSOR ... FOR UPDATE is not supported
132531 [tcpConnection-8080-2] WARN util.JDBCExceptionReporter - SQL Error: 0, SQLState: 0A000
132531 [tcpConnection-8080-2] ERROR util.JDBCExceptionReporter - ERROR: DECLARE CURSOR ... FOR UPDATE is not supported
However, if I remove the criteria.setLockMode() statement, life is good. I used p6spy to check the SQL generated when the setLockMode(LockMode.UPGRADE) is used and it looks fine. I copied it into a SquirrelSQL window and the SQL executes fine. The problem appears to occur after the response comes back.
I've attached a test case that reproduces the problem.
---------------------------------------------------------------------
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...> - 2004-01-05 17:52:17
|
The following issue has been updated:
Updater: Matt Ho (mailto:ma...@xt...)
Date: Mon, 5 Jan 2004 11:52 AM
Changes:
Attachment changed to AccountTest.java
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-604&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-604
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-604
Summary: problems upgrading using a criteria with postgresql 7.4
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1.1
Assignee:
Reporter: Matt Ho
Created: Mon, 5 Jan 2004 11:49 AM
Updated: Mon, 5 Jan 2004 11:52 AM
Environment: sun jdk 1.4.2_03, postgresql 7.4, hibernate 2.1.1
Description:
Using Hibernate 2.1.1 and PostgreSQL 7.4, I'm trying to use the Criteria API to do a SELECT ... FOR UPDATE on a given table. If I include a
criteria.setLockMode(LockMode.UPGRADE);
I get the following Exception
132531 [tcpConnection-8080-2] WARN util.JDBCExceptionReporter - SQL Error: 0, SQLState: 0A000
132531 [tcpConnection-8080-2] ERROR util.JDBCExceptionReporter - ERROR: DECLARE CURSOR ... FOR UPDATE is not supported
132531 [tcpConnection-8080-2] WARN util.JDBCExceptionReporter - SQL Error: 0, SQLState: 0A000
132531 [tcpConnection-8080-2] ERROR util.JDBCExceptionReporter - ERROR: DECLARE CURSOR ... FOR UPDATE is not supported
However, if I remove the criteria.setLockMode() statement, life is good. I used p6spy to check the SQL generated when the setLockMode(LockMode.UPGRADE) is used and it looks fine. I copied it into a SquirrelSQL window and the SQL executes fine. The problem appears to occur after the response comes back.
I've attached a test case that reproduces the problem.
---------------------------------------------------------------------
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...> - 2004-01-05 17:52:17
|
The following issue has been updated:
Updater: Matt Ho (mailto:ma...@xt...)
Date: Mon, 5 Jan 2004 11:51 AM
Changes:
Attachment changed to HibernateSessionFactory.java
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-604&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-604
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-604
Summary: problems upgrading using a criteria with postgresql 7.4
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1.1
Assignee:
Reporter: Matt Ho
Created: Mon, 5 Jan 2004 11:49 AM
Updated: Mon, 5 Jan 2004 11:51 AM
Environment: sun jdk 1.4.2_03, postgresql 7.4, hibernate 2.1.1
Description:
Using Hibernate 2.1.1 and PostgreSQL 7.4, I'm trying to use the Criteria API to do a SELECT ... FOR UPDATE on a given table. If I include a
criteria.setLockMode(LockMode.UPGRADE);
I get the following Exception
132531 [tcpConnection-8080-2] WARN util.JDBCExceptionReporter - SQL Error: 0, SQLState: 0A000
132531 [tcpConnection-8080-2] ERROR util.JDBCExceptionReporter - ERROR: DECLARE CURSOR ... FOR UPDATE is not supported
132531 [tcpConnection-8080-2] WARN util.JDBCExceptionReporter - SQL Error: 0, SQLState: 0A000
132531 [tcpConnection-8080-2] ERROR util.JDBCExceptionReporter - ERROR: DECLARE CURSOR ... FOR UPDATE is not supported
However, if I remove the criteria.setLockMode() statement, life is good. I used p6spy to check the SQL generated when the setLockMode(LockMode.UPGRADE) is used and it looks fine. I copied it into a SquirrelSQL window and the SQL executes fine. The problem appears to occur after the response comes back.
I've attached a test case that reproduces the problem.
---------------------------------------------------------------------
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...> - 2004-01-05 17:52:16
|
The following issue has been updated:
Updater: Matt Ho (mailto:ma...@xt...)
Date: Mon, 5 Jan 2004 11:51 AM
Changes:
Attachment changed to Account.hbm.xml
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-604&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-604
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-604
Summary: problems upgrading using a criteria with postgresql 7.4
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1.1
Assignee:
Reporter: Matt Ho
Created: Mon, 5 Jan 2004 11:49 AM
Updated: Mon, 5 Jan 2004 11:51 AM
Environment: sun jdk 1.4.2_03, postgresql 7.4, hibernate 2.1.1
Description:
Using Hibernate 2.1.1 and PostgreSQL 7.4, I'm trying to use the Criteria API to do a SELECT ... FOR UPDATE on a given table. If I include a
criteria.setLockMode(LockMode.UPGRADE);
I get the following Exception
132531 [tcpConnection-8080-2] WARN util.JDBCExceptionReporter - SQL Error: 0, SQLState: 0A000
132531 [tcpConnection-8080-2] ERROR util.JDBCExceptionReporter - ERROR: DECLARE CURSOR ... FOR UPDATE is not supported
132531 [tcpConnection-8080-2] WARN util.JDBCExceptionReporter - SQL Error: 0, SQLState: 0A000
132531 [tcpConnection-8080-2] ERROR util.JDBCExceptionReporter - ERROR: DECLARE CURSOR ... FOR UPDATE is not supported
However, if I remove the criteria.setLockMode() statement, life is good. I used p6spy to check the SQL generated when the setLockMode(LockMode.UPGRADE) is used and it looks fine. I copied it into a SquirrelSQL window and the SQL executes fine. The problem appears to occur after the response comes back.
I've attached a test case that reproduces the problem.
---------------------------------------------------------------------
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...> - 2004-01-05 17:50:15
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-604 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-604 Summary: problems upgrading using a criteria with postgresql 7.4 Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.1.1 Assignee: Reporter: Matt Ho Created: Mon, 5 Jan 2004 11:49 AM Updated: Mon, 5 Jan 2004 11:49 AM Environment: sun jdk 1.4.2_03, postgresql 7.4, hibernate 2.1.1 Description: Using Hibernate 2.1.1 and PostgreSQL 7.4, I'm trying to use the Criteria API to do a SELECT ... FOR UPDATE on a given table. If I include a criteria.setLockMode(LockMode.UPGRADE); I get the following Exception 132531 [tcpConnection-8080-2] WARN util.JDBCExceptionReporter - SQL Error: 0, SQLState: 0A000 132531 [tcpConnection-8080-2] ERROR util.JDBCExceptionReporter - ERROR: DECLARE CURSOR ... FOR UPDATE is not supported 132531 [tcpConnection-8080-2] WARN util.JDBCExceptionReporter - SQL Error: 0, SQLState: 0A000 132531 [tcpConnection-8080-2] ERROR util.JDBCExceptionReporter - ERROR: DECLARE CURSOR ... FOR UPDATE is not supported However, if I remove the criteria.setLockMode() statement, life is good. I used p6spy to check the SQL generated when the setLockMode(LockMode.UPGRADE) is used and it looks fine. I copied it into a SquirrelSQL window and the SQL executes fine. The problem appears to occur after the response comes back. I've attached a test case that reproduces the problem. --------------------------------------------------------------------- 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...> - 2004-01-05 17:24:16
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-603 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-603 Summary: Add a hook to get at configured Interceptor on Session Type: Improvement Status: Unassigned Priority: Minor Project: Hibernate2 Versions: 2.1.1 Assignee: Reporter: Edina Pimp Created: Mon, 5 Jan 2004 11:23 AM Updated: Mon, 5 Jan 2004 11:23 AM Description: It would be nice to have a handle to the configured Interceptor on the Session. Having one would allow runtime plugability of different Interceptors. --------------------------------------------------------------------- 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...> - 2004-01-05 16:38:16
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-602 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-602 Summary: hbm2ddl create unexpected not-null constraints on <subclass> Type: Bug Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.1.1 Assignee: Reporter: Emmanuel Bernard Created: Mon, 5 Jan 2004 10:37 AM Updated: Mon, 5 Jan 2004 10:37 AM Description: When declaring not-null property into <subclass> A and not in it's superclass (SuperA), then SuperA cannot be insert (constraints violation). This is not expected. --------------------------------------------------------------------- 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...> - 2004-01-05 14:56:15
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Mon, 5 Jan 2004 8:55 AM
Body:
hibernate needs to honor lifecycle and other stuff - so it is required to load the object.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-601
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-601
Summary: delete(Serializable pk) in session
Type: New Feature
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Assignee:
Reporter: belcore walter
Created: Mon, 5 Jan 2004 8:46 AM
Updated: Mon, 5 Jan 2004 8:55 AM
Description:
Why ther isn't a delete method like delete(Serializable pk) ? Where pk is a composite id o a primary key
Now, if want delete a object, I should before load it e after delete. So Hibernate makes two (select and delete) sql istance.
With my suggestion I can delete a object with this code:
MyCompositeId pk= new MyCompositeId("ABC22",2);
session.delete(pk);
and Hibernate will make only a sql like:
delete from FOO where COD='ABC22' and INCREMENT=2
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2004-01-05 14:47:15
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-601 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-601 Summary: delete(Serializable pk) in session Type: New Feature Status: Unassigned Priority: Major Project: Hibernate2 Components: core Assignee: Reporter: belcore walter Created: Mon, 5 Jan 2004 8:46 AM Updated: Mon, 5 Jan 2004 8:46 AM Description: Why ther isn't a delete method like delete(Serializable pk) ? Where pk is a composite id o a primary key Now, if want delete a object, I should before load it e after delete. So Hibernate makes two (select and delete) sql istance. With my suggestion I can delete a object with this code: MyCompositeId pk= new MyCompositeId("ABC22",2); session.delete(pk); and Hibernate will make only a sql like: delete from FOO where COD='ABC22' and INCREMENT=2 --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2004-01-05 13:46:16
|
The following comment has been added to this issue:
Author: Eileen Huan
Created: Mon, 5 Jan 2004 7:45 AM
Body:
I'm using hibernate 2.1-final and hibernate-extensions 2.0.2.
**************************************************************
All jars in F:\DB\hbm\lib are:
ant.jar
c3p0.jar
cglib-asm.jar
cglib2.jar
commons-beanutils.jar
commons-collections.jar
commons-dbcp.jar
commons-lang.jar
commons-logging.jar
commons-pool.jar
concurrent.jar
connector.jar
dom4j.jar
ehcache.jar
hibern8ide.jar
hibernate-tools.jar
hibernate2.jar
hsqldb.jar
jaas.jar
jboss-cache.jar
jboss-common.jar
jboss-jmx.jar
jboss-system.jar
jcs.jar
jdbc2_0-stdext.jar
jdom.jar
jgroups.jar
joi-ext.jar
jta.jar
junit.jar
log4j-1.2.8.jar
log4j.jar
maven-xdoclet-plugin-1.2b4.jar
middlegen-2.0-b2-dev.jar
middlegen-hibernate-plugin-2.0-b2-dev.jar
odmg.jar
optional.jar
oscache.jar
pf-joi-full.jar
proxool.jar
swarmcache.jar
tools.jar
velocity-1.4-dev.jar
xalan.jar
xdoclet-1.2b4.jar
xdoclet-hibernate-module-1.2b4.jar
xdoclet-xdoclet-module-1.2b4.jar
xerces.jar
xjavadoc-1.0.jar
xml-apis.jar
*****************************************************************
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-600
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-600
Summary: hbm2java can't mapping joined-subclasses correctly which are in independent files from the file of the super class.
Type: Bug
Status: Open
Priority: Critical
Project: Hibernate2
Components:
toolset
Versions:
2.1
Assignee: Max Rydahl Andersen
Reporter: Eileen Huan
Created: Mon, 5 Jan 2004 6:16 AM
Updated: Mon, 5 Jan 2004 7:45 AM
Environment: Apache Ant version 1.5.4 compiled on August 12 2003
Buildfile: build.xml
Detected Java version: 1.4 in: C:\j2sdk1.4.2_03\jre
Detected OS: Windows 2000
Description:
I have posted my problem on hibernate forum as "http://forum.hibernate.org/viewtopic.php?t=926802&sid=a04167043b0b8cd84c79b9d16b332a7e".
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2004-01-05 13:34:16
|
The following comment has been added to this issue:
Author: Eileen Huan
Created: Mon, 5 Jan 2004 7:34 AM
Body:
When I write the "joined-subclass" element inside the hbm file of the super class "Resource" instead of writing it in a independent hbm file, everything works very well!!
I bet what I reported is sure to be a bug.
BTW:
1> The build.xml is modified from the sample build.xml file of the hibernate toolset tutorial (http://www.hibernate.org/hib_docs/online/workshop_toolset/presentation/html).
2> The "error message of verbose.txt" file in the Attachment means its context is the error message I got when using the command "ant h2j -verbose". So as "error message of debug.txt" file.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-600
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-600
Summary: hbm2java can't mapping joined-subclasses correctly which are in independent files from the file of the super class.
Type: Bug
Status: Open
Priority: Critical
Project: Hibernate2
Components:
toolset
Versions:
2.1
Assignee: Max Rydahl Andersen
Reporter: Eileen Huan
Created: Mon, 5 Jan 2004 6:16 AM
Updated: Mon, 5 Jan 2004 7:34 AM
Environment: Apache Ant version 1.5.4 compiled on August 12 2003
Buildfile: build.xml
Detected Java version: 1.4 in: C:\j2sdk1.4.2_03\jre
Detected OS: Windows 2000
Description:
I have posted my problem on hibernate forum as "http://forum.hibernate.org/viewtopic.php?t=926802&sid=a04167043b0b8cd84c79b9d16b332a7e".
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2004-01-05 13:30:15
|
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-600 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-600 Summary: hbm2java can't mapping joined-subclasses correctly which are in independent files from the file of the super class. Type: Bug Status: Open Priority: Critical Project: Hibernate2 Components: toolset Versions: 2.1 Assignee: Max Rydahl Andersen Reporter: Eileen Huan Created: Mon, 5 Jan 2004 6:16 AM Updated: Mon, 5 Jan 2004 7:30 AM Environment: Apache Ant version 1.5.4 compiled on August 12 2003 Buildfile: build.xml Detected Java version: 1.4 in: C:\j2sdk1.4.2_03\jre Detected OS: Windows 2000 Description: I have posted my problem on hibernate forum as "http://forum.hibernate.org/viewtopic.php?t=926802&sid=a04167043b0b8cd84c79b9d16b332a7e". --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2004-01-05 13:08:17
|
The following issue has been updated:
Updater: Eileen Huan (mailto:ff...@16...)
Date: Mon, 5 Jan 2004 7:08 AM
Comment:
Please read readme.txt first.
Changes:
Attachment changed to related files.zip
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-600&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-600
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-600
Summary: hbm2java can't mapping joined-subclasses correctly which are in independent files from the file of the super class.
Type: Bug
Status: Unassigned
Priority: Critical
Project: Hibernate2
Components:
toolset
Versions:
2.1
Assignee:
Reporter: Eileen Huan
Created: Mon, 5 Jan 2004 6:16 AM
Updated: Mon, 5 Jan 2004 7:08 AM
Environment: Apache Ant version 1.5.4 compiled on August 12 2003
Buildfile: build.xml
Detected Java version: 1.4 in: C:\j2sdk1.4.2_03\jre
Detected OS: Windows 2000
Description:
I have posted my problem on hibernate forum as "http://forum.hibernate.org/viewtopic.php?t=926802&sid=a04167043b0b8cd84c79b9d16b332a7e".
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
93 messages has been excluded from this view by a project administrator.
