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-10-22 10:22:30
|
The following comment has been added to this issue:
Author: Nicolas Berthet
Created: Wed, 22 Oct 2003 3:49 AM
Body:
It finally seems to belong to BlobImpl
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-418
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-418
Summary: An large insert statement raise an java.lang.OutOfMemory
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1 beta 3
Assignee:
Reporter: Nicolas Berthet
Created: Wed, 22 Oct 2003 3:20 AM
Updated: Wed, 22 Oct 2003 3:20 AM
Environment: hiberate 2.1b3, webwork 2, resin
Description:
I'm trying to insert a 5 Mo file (BinaryType) and it raise an OutOfMemory.. i'm unable to trace where it come from... the same process works for files until about 4 Mo
---------------------------------------------------------------------
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-10-22 10:16:01
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-418 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-418 Summary: An large insert statement raise an java.lang.OutOfMemory Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.1 beta 3 Assignee: Reporter: Nicolas Berthet Created: Wed, 22 Oct 2003 3:20 AM Updated: Wed, 22 Oct 2003 3:20 AM Environment: hiberate 2.1b3, webwork 2, resin Description: I'm trying to insert a 5 Mo file (BinaryType) and it raise an OutOfMemory.. i'm unable to trace where it come from... the same process works for files until about 4 Mo --------------------------------------------------------------------- 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-10-22 09:45:46
|
The following issue has been updated:
Updater: Jenica Humphreys (mailto:je...@mv...)
Date: Tue, 21 Oct 2003 4:18 PM
Comment:
I am not sure how to create a diff file of the sort that are on most of the patches here. This is just a standard project diff for the hibernate source.
Changes:
Attachment changed to hibernate.diff
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-415&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-415
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-415
Summary: Set the isolation level for SELECT statements (add "with ur")
Type: New Feature
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0rc2
Assignee:
Reporter: Jenica Humphreys
Created: Tue, 21 Oct 2003 4:16 PM
Updated: Tue, 21 Oct 2003 4:18 PM
Environment: DB2 7.2+
Description:
DB2 allows you to set the isolation level for each select statement, and depending on environment can by default lock a page for every SELECT issued. Adding "with ur" to each SELECT statement allows an uncommitted read, increasing speed and decreasing the chances of database locks.
This patch adds a dialect feature which allows you to add the isolation level to the end of each SELECT generated by hibernate.
---------------------------------------------------------------------
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-10-22 08:45:55
|
Message:
The following issue has been closed.
Resolver: Daniel Bradby
Date: Tue, 21 Oct 2003 10:03 PM
Done.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-325
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-325
Summary: JCASessionFactoryImpl incompatible with WebLogic (8.1)
Type: Bug
Status: Closed
Priority: Minor
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1
Versions:
2.0.1
Assignee: Daniel Bradby
Reporter: Ethan Wolf
Created: Thu, 11 Sep 2003 4:39 PM
Updated: Tue, 21 Oct 2003 10:03 PM
Environment: Windows 2000, WebLogic 8.1 (Windows version)
Description:
JCASessionImplFactory.openSession() performs a cast of the Session returned from the application server's connection manager. The cast is to the implementation class (JCASessionImpl), not the interface (Session).
However, WebLogic's connection manager returns a proxy, resulting in a class cast exception.
The problem seems to be avoidable by casting to Session instead of the implementation 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-10-22 08:13:56
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-417 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-417 Summary: Criteria API and key-many-to-one Type: Bug Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.1 beta 4 Assignee: Reporter: Sebastien Cesbron Created: Wed, 22 Oct 2003 3:07 AM Updated: Wed, 22 Oct 2003 3:07 AM Environment: Win2k SQLServer with jTds driver Description: I have one class Bar with a primary key composed of a 'key-many-to-one' to a class Foo. I want to find a Bar instance with a Foo id so I have this criteria : Criteria criteria = session.createCriteria(Bar.class); criteria.createCriteria("foo").add(Expression.eq("id", new Integer(1))); Bar bar = (Bar) criteria.uniqueResult(); Then I have this sql statement select this.ID_FOO as ID_FOO0_, this.text as text0_ from BAR this where x0_.id=1 which fails because x0_ isn't defined. With an HQL query it works. --------------------------------------------------------------------- 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-10-22 07:24:06
|
Message:
The following issue has been re-assigned.
Assignee: Gavin King (mailto:ga...@in...)
Assigner: Gavin King (mailto:ga...@in...)
Date: Tue, 21 Oct 2003 7:45 PM
Comment:
Yes, I agree - I've been thinking about this. All thats really needed is a toList() method of the Session interface, or something like that. However, I don't want to clutter then Session API. So I'll give it some more thought.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-416
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-416
Summary: Cache browser
Type: New Feature
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
toolset
Assignee: Gavin King
Reporter: Yannick Menager
Created: Tue, 21 Oct 2003 5:55 PM
Updated: Tue, 21 Oct 2003 7:45 PM
Description:
It would be mindboggingly useful to have a "session cache browser", to allow to see which objects have been loaded in the cache. That would be very useful in applications that handles lots of data and manually "evict" the persisted objects, in which situation that kind of tool is a must to be able to spot "leaks"
---------------------------------------------------------------------
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-10-22 06:47:43
|
Message:
The following issue has been closed.
Resolver: Max Rydahl Andersen
Date: Tue, 21 Oct 2003 2:02 PM
commited my (maxs) patch
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-407
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-407
Summary: Composite keys do not work with native createSQLQuery
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Fix Fors:
2.1 beta 5
Versions:
2.1 beta 4
2.1 beta 5
Assignee: Max Rydahl Andersen
Reporter: David Morris
Created: Thu, 16 Oct 2003 12:19 PM
Updated: Tue, 21 Oct 2003 2:02 PM
Description:
Composite key columns are not found when replacing bracketed names. See thread http://forum.hibernate.org/viewtopic.php?t=924785 for more details.
---------------------------------------------------------------------
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-10-22 05:57:54
|
Message: The following issue has been re-assigned. Assignee: Gavin King (mailto:ga...@in...) --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?= key=3DHB-413 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-413 Summary: session.getCurrentLockMode(obj) and session.refresh() Type: Bug Status: Assigned Priority: Major Project: Hibernate2 Components:=20 core Versions: 2.0.3 Assignee: Gavin King Reporter: Philippe Chal=C3=A9at Created: Tue, 21 Oct 2003 5:33 AM Updated: Tue, 21 Oct 2003 7:39 PM Environment: Win XP, Linux, SAP DB Description: The following code doesn't have the expected behaviour : System.out.println("=3D> " + session.getCurrentLockMode(obj));=20 session.refresh(obj, LockMode.UPDGRADE); obj.getCode(); // To be sure that there is no pb with proxy (initialize) System.out.println("=3D> " + session.getCurrentLockMode(obj));=20 With "show sql", it gives me this : =3D> READ select ik, code, noSocCom, noCliLiv from SV_Commande where ik=3D? for upd= ate =3D> READ=20 Philippe --------------------------------------------------------------------- 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-10-22 05:07:31
|
The following comment has been added to this issue:
Author: Gavin King
Created: Wed, 22 Oct 2003 12:06 AM
Body:
Hibernate already has dependencies upon commons-logging and commons-collections and I will certainly pick up a dependency upon javagroups. So no problems there!
Unfortunately, when I try to run the test suite, Hibernate hangs in EntryUpdateState.wait() ( called from Cache.getFromCache() ).
Now this is probably my fault since I know nothing about configuring OSCache.
Any suggestions?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-412
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-412
Summary: OSCache support for Hibernate 2.1
Type: Improvement
Status: Assigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee: Gavin King
Reporter: Mathias Bogaert
Created: Mon, 20 Oct 2003 6:34 AM
Updated: Tue, 21 Oct 2003 1:53 AM
Environment: OSCache 2.0 and Hibernate 2.1 (CVS as from yesterday)
Description:
Attached is an example how to integrate OpenSymphony OSCache and Hibernate's 2.1 caching system. Because of the fact that the cache is not reponsible for refreshing, the nice fail-over feature of OSCache is not used (yet).
---------------------------------------------------------------------
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-10-22 04:16:40
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Tue, 21 Oct 2003 7:48 PM
This must have already been fixed in Hibernate 2.1, since FooBarTest.testRe=
fresh() tests this exact thing. Try the latest 2.1 release. :)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?=
key=3DHB-413
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-413
Summary: session.getCurrentLockMode(obj) and session.refresh()
Type: Bug
Status: Closed
Priority: Major
Resolution: DUPLICATE
Project: Hibernate2
Components:=20
core
Versions:
2.0.3
Assignee: Gavin King
Reporter: Philippe Chal=C3=A9at
Created: Tue, 21 Oct 2003 5:33 AM
Updated: Tue, 21 Oct 2003 7:48 PM
Environment: Win XP, Linux, SAP DB
Description:
The following code doesn't have the expected behaviour :
System.out.println("=3D> " + session.getCurrentLockMode(obj));=20
session.refresh(obj, LockMode.UPDGRADE);
obj.getCode(); // To be sure that there is no pb with proxy (initialize)
System.out.println("=3D> " + session.getCurrentLockMode(obj));=20
With "show sql", it gives me this :
=3D> READ
select ik, code, noSocCom, noCliLiv from SV_Commande where ik=3D? for upd=
ate
=3D> READ=20
Philippe
---------------------------------------------------------------------
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-10-22 01:05:30
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-415 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-415 Summary: Set the isolation level for SELECT statements (add "with ur") Type: New Feature Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.0rc2 Assignee: Reporter: Jenica Humphreys Created: Tue, 21 Oct 2003 4:16 PM Updated: Tue, 21 Oct 2003 4:16 PM Environment: DB2 7.2+ Description: DB2 allows you to set the isolation level for each select statement, and depending on environment can by default lock a page for every SELECT issued. Adding "with ur" to each SELECT statement allows an uncommitted read, increasing speed and decreasing the chances of database locks. This patch adds a dialect feature which allows you to add the isolation level to the end of each SELECT generated by hibernate. --------------------------------------------------------------------- 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-10-22 01:02:25
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-416 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-416 Summary: Cache browser Type: New Feature Status: Unassigned Priority: Major Project: Hibernate2 Components: toolset Assignee: Reporter: Yannick Menager Created: Tue, 21 Oct 2003 5:55 PM Updated: Tue, 21 Oct 2003 5:55 PM Description: It would be mindboggingly useful to have a "session cache browser", to allow to see which objects have been loaded in the cache. That would be very useful in applications that handles lots of data and manually "evict" the persisted objects, in which situation that kind of tool is a must to be able to spot "leaks" --------------------------------------------------------------------- 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-10-21 19:50:20
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Tue, 21 Oct 2003 11:51 AM
I committed a slightly simplified version of this patch to 2.1 branch
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-379
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-379
Summary: IN clause in an HQL query confuses the preprocessor.
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1 beta 5
Versions:
2.0.3
Assignee: Gavin King
Reporter: Bulent Erdemir
Created: Fri, 3 Oct 2003 3:52 PM
Updated: Tue, 21 Oct 2003 11:51 AM
Description:
check the related forum postings for detailed information at:
http://forum.hibernate.org/viewtopic.php?p=2173569&sid=298fed84e2b015aff203a1f1bd83ab80#2173569
For queries having an IN clause, this confuses the preprocessor and causes hibernate to call getImportedClass() in QueryTranslator.concreteQueries() for each token in the query.
This also causes long parsing time especially noticeable when running hibernate code under Jboss in which a different classloader is used.
---------------------------------------------------------------------
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-10-21 18:17:58
|
The following comment has been added to this issue:
Author: Gavin King
Created: Tue, 21 Oct 2003 12:06 PM
Body:
Ah yeah. OK, commit it. P.S. coding standard has a carriage return before "else" ;)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-407
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-407
Summary: Composite keys do not work with native createSQLQuery
Type: Bug
Status: Assigned
Priority: Major
Project: Hibernate2
Versions:
2.1 beta 4
2.1 beta 5
Assignee: Max Rydahl Andersen
Reporter: David Morris
Created: Thu, 16 Oct 2003 12:19 PM
Updated: Sun, 19 Oct 2003 3:13 PM
Description:
Composite key columns are not found when replacing bracketed names. See thread http://forum.hibernate.org/viewtopic.php?t=924785 for more details.
---------------------------------------------------------------------
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-10-21 18:12:47
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-414 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-414 Summary: Informix dialect creates syntax errors in IDS 9.4 Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.0.2 Assignee: Reporter: Finn McCann Created: Tue, 21 Oct 2003 11:01 AM Updated: Tue, 21 Oct 2003 11:01 AM Environment: Hibernate2 on JDK1.4 on Win2000, talking via Informix JDBC 2.21.JC5 driver to Informix IDS 9.4 on another Windows 2000 box. Description: Having tested Informix dialect in Hibernate2 against Informix IDS v9.4, we found a couple of issues: 1. Serial ids: <id name="id" column="ID" length="32" unsaved-value="null"> <generator class="uuid.hex"/> </id> creates a data type: INT8 SERIAL instead of: SERIAL8 The "INT8 SERIAL" causes a syntax error in IDS 9.4. 2. Foreign Key constraint names: <set name="upliftRates" lazy="true" cascade="all" order-by="EFFECTIVE_DATE desc"> <key column="NETWORK_ID" length="32"/> <one-to-many class="com.capetechnologies.multinet.domain.UpliftRate"/> </set> creates this ALTER TABLE statement: alter table MULTINET_TAX_RATES add constraint FKE1700D046924EC foreign key (NETWORK_ID) references MULTINET_NETWORK instead of: alter table MULTINET_TAX_RATES add constraint foreign key (NETWORK_ID) references MULTINET_NETWORK constraint FKE1700D046924EC Having "CONSTRAINT <constraint name>" within the statement instead of at the end causes a syntax error. This also applies to adding UNIQUE CONSTRAINTs. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-21 10:56:35
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?= key=3DHB-413 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-413 Summary: session.getCurrentLockMode(obj) and session.refresh() Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components:=20 core Versions: 2.0.3 Assignee:=20 Reporter: Philippe Chal=C3=A9at Created: Tue, 21 Oct 2003 5:33 AM Updated: Tue, 21 Oct 2003 5:33 AM Environment: Win XP, Linux, SAP DB Description: The following code doesn't have the expected behaviour : System.out.println("=3D> " + session.getCurrentLockMode(obj));=20 session.refresh(obj, LockMode.UPDGRADE); obj.getCode(); // To be sure that there is no pb with proxy (initialize) System.out.println("=3D> " + session.getCurrentLockMode(obj));=20 With "show sql", it gives me this : =3D> READ select ik, code, noSocCom, noCliLiv from SV_Commande where ik=3D? for upd= ate =3D> READ=20 Philippe --------------------------------------------------------------------- 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-10-21 10:11:06
|
The following comment has been added to this issue:
Author: Chris Miller
Created: Tue, 21 Oct 2003 3:11 AM
Body:
OSCache is pretty light on dependencies - the only required jar is commons-logging.
Other possible dependencies are:
- commons-collections. This is only used when running on JDK 1.3, and even then it is optional (although highly recommended for performance reasons).
- javagroups-all.jar. This is only required when using javagroups (now jgroups) for clustering. JMS clustering can be used instead, in which case you obviously need the support of your app server or other JMS provider.
I haven't had a chance to look at Hibernate recently so I can't comment on this issue much more except to say that I'll be happy to help out with any questions/problems you hit with OSCache integration.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-412
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-412
Summary: OSCache support for Hibernate 2.1
Type: Improvement
Status: Assigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee: Gavin King
Reporter: Mathias Bogaert
Created: Mon, 20 Oct 2003 6:34 AM
Updated: Tue, 21 Oct 2003 1:53 AM
Environment: OSCache 2.0 and Hibernate 2.1 (CVS as from yesterday)
Description:
Attached is an example how to integrate OpenSymphony OSCache and Hibernate's 2.1 caching system. Because of the fact that the cache is not reponsible for refreshing, the nice fail-over feature of OSCache is not used (yet).
---------------------------------------------------------------------
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-10-21 10:06:50
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Tue, 21 Oct 2003 4:58 AM
Ah. Hmmmm unfortunately it is not really possible to fix this elegantly w/o changing the API of ClassPersister. So I'm not going to fix it since
(a) it is only a problem on Sybase
(b) you can work around it using <key-many-to-one>
If this is really a big problem for you, email me. (There -is- an inelegant fix, I think.)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-374
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-374
Summary: Duplicate column in SQL select clause
Type: Bug
Status: Closed
Priority: Critical
Resolution: WON'T FIX
Project: Hibernate2
Versions:
2.0.3
Assignee: Gavin King
Reporter: Andrei Pavlenko
Created: Wed, 1 Oct 2003 9:32 AM
Updated: Tue, 21 Oct 2003 4:58 AM
Environment: Sybase
Description:
I have "composite-id" with two fields.
I want to create "many-to-one" reference for field "elementId" but generated by Hibernate SQL query is incorrect.
When I change column name to "elementOwnerId" it is generated correctly.
See attached files.
Wrong SQL:
select attribut0_.attributeId as attributeId, attribut0_.elementId as elementId, attribut0_.possibleAttributeValueId as possible3_, attribut0_.attributeValueFreeText as attribut4_, attribut0_.attributeId as attribut1_, attribut0_.elementId as elementId from AttributeValue attribut0_ where (attribut0_.elementId=? )and(attribut0_.attributeId=? )
Error message:
Select expression results in more than one column having same name. Column name 'elementId' is specified more than once
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/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-10-21 10:06:42
|
The following comment has been added to this issue:
Author: Gavin King
Created: Tue, 21 Oct 2003 2:16 AM
Body:
Daniel, what is the status of this?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-325
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-325
Summary: JCASessionFactoryImpl incompatible with WebLogic (8.1)
Type: Bug
Status: Assigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee: Daniel Bradby
Reporter: Ethan Wolf
Created: Thu, 11 Sep 2003 4:39 PM
Updated: Tue, 23 Sep 2003 6:33 PM
Environment: Windows 2000, WebLogic 8.1 (Windows version)
Description:
JCASessionImplFactory.openSession() performs a cast of the Session returned from the application server's connection manager. The cast is to the implementation class (JCASessionImpl), not the interface (Session).
However, WebLogic's connection manager returns a proxy, resulting in a class cast exception.
The problem seems to be avoidable by casting to Session instead of the implementation 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-10-21 10:06:24
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Tue, 21 Oct 2003 4:53 AM
We've agreed to close this issue for now.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-296
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-296
Summary: ConcurrentModificationException when initializing collection
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee: Gavin King
Reporter: Mathias Bogaert
Created: Thu, 28 Aug 2003 6:49 AM
Updated: Tue, 21 Oct 2003 4:53 AM
Environment: 2.1 beta 2 from CVS
Description:
When initializing a collection, I get the following stacktrace (not seen with Hibernate 2.0.3):
8047 ERROR [tcpConnection-81-0] (webwork.dispatcher.ServletDispatcher:188) - Could not execute action
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.remove(HashMap.java:801)
at net.sf.hibernate.impl.SessionImpl.endLoadingCollections(SessionImpl.java:2973)
at net.sf.hibernate.loader.Loader.doResultSet(Loader.java:224)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:113)
at net.sf.hibernate.loader.Loader.loadCollection(Loader.java:720)
at net.sf.hibernate.loader.Loader.loadCollection(Loader.java:703)
at net.sf.hibernate.loader.OneToManyLoader.initialize(OneToManyLoader.java:74)
at net.sf.hibernate.impl.SessionImpl.initialize(SessionImpl.java:3101)
at net.sf.hibernate.collection.PersistentCollection.forceLoad(PersistentCollection.java:236)
at net.sf.hibernate.Hibernate.initialize(Hibernate.java:255)
at com.intrasoft.persistence.hibernate.HibernatePersistenceService.initialize(HibernatePersistenceService.java:143)
at com.intrasoft.sysaudit.mission.action.wizard.AbstractMissionStepAction.initializeMission(AbstractMissionStepAction.java:112)
at com.intrasoft.sysaudit.mission.action.wizard.AbstractMissionStepAction.saveMissionInSession(AbstractMissionStepAction.java:74)
at com.intrasoft.sysaudit.mission.action.wizard.MissionStep1.doExecute(MissionStep1.java:173)
at com.opensymphony.xwork.ActionSupport.execute(ActionSupport.java:31)
Here is my code:
if (mission.getUnit() != null) {
persistenceService.initialize(mission.getUnit().getUsers());
}
and in HibernatePersistenceService:
public void initialize(Object objectToInitialize) {
try {
if (!Hibernate.isInitialized(objectToInitialize)) {
Hibernate.initialize(objectToInitialize);
}
}
catch (HibernateException e) {
throw new InfrastructureException(e);
}
}
---------------------------------------------------------------------
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-10-21 10:06:16
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Tue, 21 Oct 2003 2:10 AM
This is not a bug. You can specify SQL column types exactly using the jdbc-type attribute.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-366
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-366
Summary: Length and precision of Numeric
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.1 beta 3
Assignee:
Reporter: xfgdf
Created: Fri, 26 Sep 2003 5:27 AM
Updated: Tue, 21 Oct 2003 2:10 AM
Environment: Hibernate 2.1 beta 3 (7.9.2003)
Description:
The default mapping of java.util.BigDecimal is the Decimal hibernate type, which is translate in most dialect in "NUMBER(19, $l)". This don't allow us to specify the length of the number, only is precision.
The main problem come from the default value of the length use is the Column.DEFAULT_PROPERTY_LENGTH=255. This make an invalid type because the precision can't be greater than the length (NUMERIC(19, 255)).
It would be great to have a different default value for the length (something like 2), and also to be able to specify the precision in the mapping file (may be by something like <property name="price" length="19,4" />).
Adrien
---------------------------------------------------------------------
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-10-21 09:41:59
|
The following comment has been added to this issue:
Author: Gavin King
Created: Tue, 21 Oct 2003 2:10 AM
Body:
Jason, what is the status of this one?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-395
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-395
Summary: Lazy Initialization used even when collection mapping says lazy="false"
Type: Bug
Status: Unassigned
Priority: Blocker
Project: Hibernate2
Components:
core
Versions:
2.1 beta 3
2.1 beta 4
Assignee:
Reporter: Jason Carreira
Created: Mon, 13 Oct 2003 4:46 PM
Updated: Mon, 13 Oct 2003 4:47 PM
Environment: We use Oracle with WebLogic and WebSphere, but I've included a test case which fails as unit tests running against HSQL
Description:
If a child class has a Proxy (all the ones I've tested have themselves as the proxy class) and the parent class has a <set> mapping to the child class with lazy="false", then, if session.load(Parent.class, parentId) is called, then child collection will be lazily initialized. This doesn't happen with session.find(), for some reason.
---------------------------------------------------------------------
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-10-21 09:41:34
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Tue, 21 Oct 2003 2:09 AM
User did not supply test code to reproduce the problem against current Hibernate 2.1 CVS.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-377
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-377
Summary: Hibernate 2.1 appears to break jcs caching
Type: Bug
Status: Closed
Priority: Major
Resolution: CANNOT REPRODUCE
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: tekno
Created: Thu, 2 Oct 2003 4:34 AM
Updated: Tue, 21 Oct 2003 2:09 AM
Environment: Development Windows 2000 SP3, JSDK 4.1.2
Deployment Solaris 9
Database Postgresql 7.3
Description:
I am getting an AssertionFailure - cannot cache a reference to an object with a null id when I try to do an update. Here is the sample code -
NB: This has been working fine for me in hibernate versions 2.0 - 2.03
I have the following two mappings
<class name="Customer" table="customers" polymorphism="explicit">
<cache usage="read-write"/>
<id name="id" unsaved-value="0">
<generator class="sequence">
<param name="sequence">customers_id_seq</param>
</generator>
</id>
<property name="postcode"/>
<many-to-one name="csOwner" class="Employee" column="cs_owner" />
</class>
and
<class name="Employee" table="staff">
<id name="id">
<generator class="sequence">
<param name="sequence">staff_id_seq</param>
</generator>
</id>
<property name="name"/>
</class>
the following main() throws the exception
Session session = null;
Customer customer = null;
SessionFactory factory = null;
try {
// build factory
factory = new Configuration().configure().buildSessionFactory();
System.out.println("Starting first session");
// first session gets customer instance
session = factory.openSession();
customer = (Customer) session.load(Customer.class, new Long(1275));
System.out.println("Loaded customer " + customer.getId() + " has owner " + customer.getCsOwner().getId());
session.flush();
session.connection().commit();
session.close();
System.out.println("Updating address field");
// update a field
customer.setPostcode("TESTING");
System.out.println("Starting second session");
// second session persists update
session = factory.openSession();
session.update(customer);
session.flush();
session.connection().commit();
session.close();
System.out.println("Finished");
factory.close();
} catch (Exception ex){
ex.printStackTrace();
} finally {
if(session!=null)session.close();
if(factory!=null)factory.close();
System.exit(0);
}
If i remove the cache entry in the customer mapping everything is OK, but other wise i get
net.sf.hibernate.AssertionFailure: cannot cache a reference to an object with a null id
at net.sf.hibernate.type.EntityType.disassemble(EntityType.java:89)
at net.sf.hibernate.impl.CacheEntry.disassemble(CacheEntry.java:36)
at net.sf.hibernate.impl.CacheEntry.<init>(CacheEntry.java:27)
at net.sf.hibernate.impl.ScheduledUpdate.execute(ScheduledUpdate.java:42)
at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2278)
at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2235)
at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:2178)
at com.lab.model.HibBug.main(HibBug.java:46)
---------------------------------------------------------------------
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-10-21 09:12:22
|
Message: The following issue has been re-assigned. Assignee: Gavin King (mailto:ga...@in...) --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-278 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-278 Summary: calling Configuration.generateSchemaUpdateScript always generates create sql Type: Patch Status: Assigned Priority: Major Project: Hibernate2 Components: core Versions: 2.1 Assignee: Gavin King Reporter: Dylan Etkin Created: Thu, 21 Aug 2003 7:23 AM Updated: Tue, 21 Oct 2003 2:30 AM Environment: postgres, oracle, mysql Description: The call to generateSchemaUpdateScript was always creating the create sql when running in postgres. The problem was with the case of the table name and an uppercase version being sent as a parameter to the DatabaseMetaData. The sequences were also always comming back as in need of a create since none of the dialects implement the getQuerySequencesString method. The fk's were not matching on their hashed name since the metaData name had more info than just the display name. I have fixed these issues and tested it on postgres, oracle, and mysql. It seems to work for me so I am submitting the patch. I am by-passing the call to getQuerySequencesString and just using the metaData to get all sequences if they exist. There is an outstanding issue with mysql where the call to getIndexIterator in the Table class returns an empty iterator so the index create statements are always generated. I have not looked into this. Hope this helps. --------------------------------------------------------------------- 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-10-21 08:58:28
|
Message: The following issue has been re-assigned. Assignee: Gavin King (mailto:ga...@in...) --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-378 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-378 Summary: error generate SQL from a HQL who use LEFT JOIN(on more levels) Type: Bug Status: Assigned Priority: Blocker Project: Hibernate2 Components: core Versions: 2.0rc2 2.1 2.0 final 2.0.1 2.0.2 2.0.3 2.1 beta 1 2.1 beta 2 2.1 beta 3 2.1 final 2.1 beta 4 Assignee: Gavin King Reporter: Adrian Minciuna Created: Fri, 3 Oct 2003 9:51 AM Updated: Tue, 21 Oct 2003 2:04 AM Environment: Windows 2000 sp4, JDK 1.4.1_02 Description: Bug: i have 2 classes DACPerson and DACDepartment DACPerson has an inner object manager with DACPerson , and an object department with type DACDepartment. Thus, has 2 relations <many-to-one> I need an hql like this 1) using left join select als.name, als0.name, als1.name, als2.name from DACPerson as als left join als.manager as als0 left join als.manager.manager as als1 left join als.manager.department as als2 where als.pkid=als.hcod In this case hibernate generate a wrong SQL : select tstdacpe0_.PKID as x0_0_,tstdacde3_.NAME as x1_0_, tstdacpe2_.NAME as x2_0_, tstdacpe0_.NAME as x3_0_,tstdacpe1_.NAME as x4_0_ from PERSON2 tstdacpe0_ left outer join PERSON2 tstdacpe1_ on tstdacpe0_.MGR_ID=tstdacpe1_.PKID left outer join PERSON2 tstdacpe2_ on tstdacpe1_.MGR_ID=tstdacpe2_.PKID left outer join DEPT tstdacde3_ on tstdacpe1_.Dept_id=tstdacde3_.PKID where and and ((tstdacpe0_.PKID=tstdacpe0_.HCOD )) java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Incorrect syntax near the keyword 'and'. at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source) at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)..... ------------------------------------------- Obs. if i try a HQL,a little bit simple ex: select als.name, als0.name, als1.name from DACPerson as als left join als.manager as als0 left join als.manager.department as als1 where als.pkid=als.hcod i get following error FINE: net.sf.hibernate.hql.QueryTranslator.compile() - unexpected query compilation problem java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1480) at java.lang.String.substring(String.java:1447) at net.sf.hibernate.sql.QuerySelect.toQueryString(QuerySelect.java:109) at net.sf.hibernate.hql.QueryTranslator.renderSQL(QueryTranslator.java:515) at net.sf.hibernate.hql.QueryTranslator.compile(QueryTranslator.java:151) --------------------------------------------------------- 3) If i modify hql like this : select als.name, als0.name, als1.name, als2.name from DACPerson as als left join als.manager as als0 left join als0.manager as als1 left join als0.department as als2 where als.pkid=als.hcod and IT'S WORK fine --------------------------------------------------- Obs: i tested also on Hibern8 IDE --------------------------------------------------------------------- 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.
