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-06-24 16:09:52
|
The following issue has been updated:
Updater: Max Rydahl Andersen (mailto:xa...@xa...)
Date: Tue, 24 Jun 2003 11:09 AM
Comment:
This is not a easy one to provide.
First: HQL is a query language, not a data manipulation language.
Second: It will probably not be affective anyway as to support LifeCycle, Interceptor and timestamp/versionstamp "affected" objects all objects have to be loaded before being updated.
Changing this to minor priority because of these two points.
Changes:
priority changed from Major to Minor
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-154&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-154
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-154
Summary: Mass updates
Type: New Feature
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: Andrea Aime
Created: Tue, 24 Jun 2003 10:43 AM
Updated: Tue, 24 Jun 2003 11:09 AM
Description:
Since it's a feature often requested on the forum and
it's definitely a nice to have, I would like to ask for mass
updates, that is, HQL that allows for the equivalent of
UPDATE tableXXX
SET value = ...
WHERE ...
---------------------------------------------------------------------
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/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-06-24 15:43:53
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-154 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-154 Summary: Mass updates Type: New Feature Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.0.1 Assignee: Reporter: Andrea Aime Created: Tue, 24 Jun 2003 10:43 AM Updated: Tue, 24 Jun 2003 10:43 AM Description: Since it's a feature often requested on the forum and it's definitely a nice to have, I would like to ask for mass updates, that is, HQL that allows for the equivalent of UPDATE tableXXX SET value = ... WHERE ... --------------------------------------------------------------------- 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/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-06-24 15:34:57
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-153 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-153 Summary: A method to get the next id in a database/generator independent way Type: New Feature Status: Unassigned Priority: Major Project: Hibernate2 Assignee: Reporter: Andrea Aime Created: Tue, 24 Jun 2003 10:34 AM Updated: Tue, 24 Jun 2003 10:34 AM Description: As you say in the developers guide, Hibernate is not well suited for mass updates. So, ok, let's do them the hard way with prepared statements and batching, but one question is open: how do I generate the same id that Hibernate would generate, so that I can avoid duplicated primary keys in a database independent manner? A method like Session.getNextId(Class class) would be useful (returning null if identity columns are used, or some other way to know that an identity column is used for the specific class). I've set major priority since I see no way to perform jdbc mass inserts in a database independent way and Hibernate could provide some support for this... (I mean, Hibernate is not only good for OR mapping, but also to write database independent applications, this problem is a limit when writing high performance apps that need mass inserts) --------------------------------------------------------------------- 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/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-06-24 15:31:52
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?= key=3DHB-152 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-152 Summary: Identity columns support for SAPD =C2=A0 =20 Type: Improvement Status: Unassigned Priority: Major Project: Hibernate2 Components:=20 core Versions: 2.0.1 Assignee:=20 Reporter: Andrea Aime Created: Tue, 24 Jun 2003 10:31 AM Updated: Tue, 24 Jun 2003 10:31 AM Description: Sapdb supports auto-increment fields since version=20 7.3, see:=20 http://www.sapdb.org/how_tos/numbergen/datentypserial_eng.htm=20 =20 Would it be possible to add support for this? Would it=20 be faster than sequences for row insertion? If so, it should=20 also be the preferred way to generate ids when the=20 "native" generator is used, I guess.=20 =20 --------------------------------------------------------------------- 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/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-06-24 09:34:55
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Tue, 24 Jun 2003 4:34 AM
Body:
yup - i'll commit it soon. Just need to rename it and add support for the config option.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-138
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-138
Summary: Ant task for hbm2java
Type: New Feature
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
toolset
Assignee: Max Rydahl Andersen
Reporter: Gavin King
Created: Tue, 17 Jun 2003 7:30 AM
Updated: Sat, 21 Jun 2003 10:49 PM
Description:
Would be very nice to wrap hbm2java in an Ant Task.
---------------------------------------------------------------------
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/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-06-23 14:13:59
|
The following comment has been added to this issue:
Author: Gavin King
Created: Mon, 23 Jun 2003 9:13 AM
Body:
Excellent!
Actually, it should go in the same package as hbm2java itself.
Max, would you please commit this work. TIA
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-138
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-138
Summary: Ant task for hbm2java
Type: New Feature
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
toolset
Assignee: Max Rydahl Andersen
Reporter: Gavin King
Created: Tue, 17 Jun 2003 7:30 AM
Updated: Sat, 21 Jun 2003 10:49 PM
Description:
Would be very nice to wrap hbm2java in an Ant Task.
---------------------------------------------------------------------
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/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-06-23 14:11:54
|
The following comment has been added to this issue:
Author: Gavin King
Created: Mon, 23 Jun 2003 9:11 AM
Body:
SQL server does not support SELECT ... FOR UPDATE. On the other hand, Hibernate should not have *tried* to use FOR UPDATE with SQL server. Might be a problem in the dialect.
The message in Oracle only occurs *sometimes* when you do something Oracle doesn't like.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-149
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-149
Summary: when trying to set an update lock on an object I get a crash in Oracle and SQL Server
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.0 final
Assignee:
Reporter: Hrituc Ovidiu
Created: Mon, 23 Jun 2003 5:21 AM
Updated: Mon, 23 Jun 2003 5:21 AM
Environment: W2k, OC4J, Oracle 9i, Sql Server 2k
Description:
when trying to do this:
dac = (MyClass)session.load(MyClass.class,Clazz,LockMode.UPGRADE );
or this
dac = (MyClass)session.load(MyClass.class);
session.lock(dac,LockMode.UPGRADE );
in a stateless session EJB I get with SQL Server:
"FOR UPDATE clause allowed only for DECLARE CURSOR."
and with Oracle: "Could not load object: ORA-01002: fetch out of sequence"
---------------------------------------------------------------------
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/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-06-23 12:30:51
|
The following comment has been added to this issue:
Author: Chris Webb
Created: Mon, 23 Jun 2003 7:30 AM
Body:
See discussion: http://sourceforge.net/forum/forum.php?thread_id=888024&forum_id=128638
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-151
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-151
Summary: Add getSession method to Transaction interface
Type: Improvement
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.0rc2
2.1
2.0 final
2.0.1
2.0.2
Assignee:
Reporter: Chris Webb
Created: Mon, 23 Jun 2003 7:28 AM
Updated: Mon, 23 Jun 2003 7:28 AM
Description:
It should be possible to retrieve the Session associated with a Transaction from a Transaction instance. This would assist some data access implentations by exposing the relationship in a convenient and logical manner.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/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-06-23 12:28:52
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-151 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-151 Summary: Add getSession method to Transaction interface Type: Improvement Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.0rc2 2.1 2.0 final 2.0.1 2.0.2 Assignee: Reporter: Chris Webb Created: Mon, 23 Jun 2003 7:28 AM Updated: Mon, 23 Jun 2003 7:28 AM Description: It should be possible to retrieve the Session associated with a Transaction from a Transaction instance. This would assist some data access implentations by exposing the relationship in a convenient and logical manner. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/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-06-23 11:35:52
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-150 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-150 Summary: odmg.jar give definitely exception Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: toolset Versions: 2.0.1 Assignee: Reporter: Rui Liu Created: Mon, 23 Jun 2003 6:35 AM Updated: Mon, 23 Jun 2003 6:35 AM Environment: win2000,resin-2.1.9 Description: missing odmg.jar...but confusing exception throwed.. more discuss here: http://sourceforge.net/forum/forum.php?thread_id=888181&forum_id=128638 java.lang.NoClassDefFoundError: net/sf/hibernate/collection/Set at net.sf.hibernate.type.TypeFactory.set(TypeFactory.java:184) at net.sf.hibernate.mapping.Set.getType(Set.java:29) at net.sf.hibernate.cfg.Binder.propertiesFromXML(Binder.java:856) at net.sf.hibernate.cfg.Binder.bindRootClass(Binder.java:288) at net.sf.hibernate.cfg.Binder.bindRoot(Binder.java:1076) at net.sf.hibernate.cfg.Configuration.add(Configuration.java:230) at net.sf.hibernate.cfg.Configuration.addInputStream(Configuration.java:252) at net.sf.hibernate.cfg.Configuration.addClass(Configuration.java:286) at eb.domain.Cfg.openSession(Unknown Source) at eb.web.webwork.action.signon.RegisterAction.doExecute(Unknown Source) at webwork.action.ActionSupport.execute(ActionSupport.java:116) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:113) at webwork.dispatcher.ServletDispatcher.service(ServletDispatcher.java:161) at javax.servlet.http.HttpServlet.service(HttpServlet.java:103) at com.caucho.server.http.FilterChainServlet.doFilter(FilterChainServlet.java:96) at com.caucho.server.http.Invocation.service(Invocation.java:315) at com.caucho.server.http.CacheInvocation.service(CacheInvocation.java:135) at com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:246) at com.caucho.server.http.HttpRequest.handleConnection(HttpRequest.java:163) at com.caucho.server.TcpConnection.run(TcpConnection.java:139) at java.lang.Thread.run(Thread.java:536) --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/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-06-23 10:21:51
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-149 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-149 Summary: when trying to set an update lock on an object I get a crash in Oracle and SQL Server Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.0 final Assignee: Reporter: Hrituc Ovidiu Created: Mon, 23 Jun 2003 5:21 AM Updated: Mon, 23 Jun 2003 5:21 AM Environment: W2k, OC4J, Oracle 9i, Sql Server 2k Description: when trying to do this: dac = (MyClass)session.load(MyClass.class,Clazz,LockMode.UPGRADE ); or this dac = (MyClass)session.load(MyClass.class); session.lock(dac,LockMode.UPGRADE ); in a stateless session EJB I get with SQL Server: "FOR UPDATE clause allowed only for DECLARE CURSOR." and with Oracle: "Could not load object: ORA-01002: fetch out of sequence" --------------------------------------------------------------------- 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/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-06-23 06:37:51
|
The following issue has been updated:
Updater: Hrituc Ovidiu (mailto:hri...@ya...)
Date: Mon, 23 Jun 2003 1:36 AM
Comment:
This is the mapping that gives me the error.Is it wrong? How?
Changes:
Attachment changed from to Copy of CdtDACPerson.hbm.xml
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-135&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-135
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-135
Summary: where attribute in many-to-many mapping applies to fields of one table
Type: New Feature
Status: Unassigned
Priority: Minor
Project: Hibernate2
Assignee:
Reporter: Hrituc Ovidiu
Created: Fri, 13 Jun 2003 9:55 AM
Updated: Mon, 23 Jun 2003 1:36 AM
Environment: Ms W2K Professional, Hibernate 2.0, OC4J
Description:
I wish it was possible to filter the resultset after attributes of the class we relate to; for now the where clause conditions are put on the "root" class.
For instance if we were to join A and B, the where conditions would automatically, no matter what, be stuck on A fields.
---------------------------------------------------------------------
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/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-06-22 22:10:51
|
The following comment has been added to this issue:
Author: Scott Payne
Created: Sun, 22 Jun 2003 5:10 PM
Body:
Eric,
You can add me to the project.xml if you like.
Cheers,
Scott.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-140
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-140
Summary: Changed Avalon component to work with cocoon 2.0.4
Type: Patch
Status: Assigned
Priority: Minor
Project: Hibernate2
Components:
toolset
Assignee: Eric Pugh
Reporter: Scott Payne
Created: Wed, 18 Jun 2003 12:47 AM
Updated: Fri, 20 Jun 2003 11:58 PM
Description:
Simple patch so that the CocoonComponentManager won't throw a ClassCastException when using the HibernateService. It seemed to try to cast it to a Component (fair enough) and this fixed it.
Also a change to the DTD used in the test case, to use the hibernate 2 DTD.
diff -riuwBb -x CVS avalon/src/java/net/sf/hibernate/avalon/HibernateService.java avalon-patched/src/java/net/sf/hibernate/avalon/HibernateService.java
--- avalon/src/java/net/sf/hibernate/avalon/HibernateService.java 2003-06-18 15:37:40.000000000 +1000
+++ avalon-patched/src/java/net/sf/hibernate/avalon/HibernateService.java 2003-06-18 15:21:00.000000000 +1000
@@ -11,7 +11,7 @@
* @author <a href="mailto:ne...@ap...">Neeme Praks</a>
* @version $Id: HibernateService.java,v 1.2 2003/06/04 10:44:25 nemecec Exp $
*/
-public interface HibernateService {
+public interface HibernateService extends org.apache.avalon.framework.component.Component {
public static final String ROLE = HibernateService.class.getName();
diff -riuwBb -x CVS avalon/src/test/net/sf/hibernate/avalon/Labor.hbm.xml avalon-patched/src/test/net/sf/hibernate/avalon/Labor.hbm.xml
--- avalon/src/test/net/sf/hibernate/avalon/Labor.hbm.xml 2003-06-18 15:37:50.000000000 +1000
+++ avalon-patched/src/test/net/sf/hibernate/avalon/Labor.hbm.xml 2003-06-18 15:25:31.000000000 +1000
@@ -1,7 +1,7 @@
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
- "-//Hibernate/Hibernate Mapping DTD//EN"
- "http://hibernate.sourceforge.net/hibernate-mapping.dtd">
+ "-//Hibernate/Hibernate Mapping DTD 2.0//EN"
+ "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd">
<hibernate-mapping>
<class name="net.sf.hibernate.avalon.Labor" table="LABOR" >
---------------------------------------------------------------------
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/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-06-22 09:10:05
|
The following issue has been updated:
Updater: Noel Kee (mailto:wj...@pa...)
Date: Sun, 22 Jun 2003 4:08 AM
Changes:
Attachment changed from to query_iterate_problem.tar.gz
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HBI-6&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HBI-6
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HBI-6
Summary: ClassCastException when using query.iterate() but works with query.list().iterator()
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate 1.2
Assignee:
Reporter: Noel Kee
Created: Sun, 22 Jun 2003 4:07 AM
Updated: Sun, 22 Jun 2003 4:08 AM
Environment: Mandrake Linux 9.1,
DB2 V7.2,
Sun's J2SDK 1.4.1_02,
Hibernate 1.2.4 (same situation with Hibernate 1.2.5)
Description:
A simple query, "from c in class itr.Product" throws a ClassCastException" when used with query.iterate(). If query.list().iterator() is used instead, it works fine.
The ClassCastException occured, when hibernate attempts to retrieve an associated class in the (itr.Pricing) in a bag and tries to cast the bag to a Long.
The complete set of java source, mapping and ddl is attached.
---------------------------------------------------------------------
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/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-06-22 09:08:15
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HBI-6 Here is an overview of the issue: --------------------------------------------------------------------- Key: HBI-6 Summary: ClassCastException when using query.iterate() but works with query.list().iterator() Type: Bug Status: Unassigned Priority: Major Project: Hibernate 1.2 Assignee: Reporter: Noel Kee Created: Sun, 22 Jun 2003 4:07 AM Updated: Sun, 22 Jun 2003 4:07 AM Environment: Mandrake Linux 9.1, DB2 V7.2, Sun's J2SDK 1.4.1_02, Hibernate 1.2.4 (same situation with Hibernate 1.2.5) Description: A simple query, "from c in class itr.Product" throws a ClassCastException" when used with query.iterate(). If query.list().iterator() is used instead, it works fine. The ClassCastException occured, when hibernate attempts to retrieve an associated class in the (itr.Pricing) in a bag and tries to cast the bag to a Long. The complete set of java source, mapping and ddl is attached. --------------------------------------------------------------------- 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/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-06-22 03:50:25
|
The following issue has been updated:
Updater: Geoff (mailto:gb...@ly...)
Date: Sat, 21 Jun 2003 10:49 PM
Comment:
Here is a working hbm2java ant task.
I didn't know how to package this, so I put it in org.apache.tools.ant.taskdefs.optional.hibernate
Changes:
Attachment changed from to Hibernate2JavaTask.java
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-138&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-138
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-138
Summary: Ant task for hbm2java
Type: New Feature
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
toolset
Assignee: Max Rydahl Andersen
Reporter: Gavin King
Created: Tue, 17 Jun 2003 7:30 AM
Updated: Sat, 21 Jun 2003 10:49 PM
Description:
Would be very nice to wrap hbm2java in an Ant Task.
---------------------------------------------------------------------
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/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-06-21 21:00:51
|
The following comment has been added to this issue:
Author: Eric Pugh
Created: Sat, 21 Jun 2003 4:00 PM
Body:
Scott,
Can I add you the project.xml file as a contributor?
Eric Pugh
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-140
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-140
Summary: Changed Avalon component to work with cocoon 2.0.4
Type: Patch
Status: Assigned
Priority: Minor
Project: Hibernate2
Components:
toolset
Assignee: Eric Pugh
Reporter: Scott Payne
Created: Wed, 18 Jun 2003 12:47 AM
Updated: Fri, 20 Jun 2003 11:58 PM
Description:
Simple patch so that the CocoonComponentManager won't throw a ClassCastException when using the HibernateService. It seemed to try to cast it to a Component (fair enough) and this fixed it.
Also a change to the DTD used in the test case, to use the hibernate 2 DTD.
diff -riuwBb -x CVS avalon/src/java/net/sf/hibernate/avalon/HibernateService.java avalon-patched/src/java/net/sf/hibernate/avalon/HibernateService.java
--- avalon/src/java/net/sf/hibernate/avalon/HibernateService.java 2003-06-18 15:37:40.000000000 +1000
+++ avalon-patched/src/java/net/sf/hibernate/avalon/HibernateService.java 2003-06-18 15:21:00.000000000 +1000
@@ -11,7 +11,7 @@
* @author <a href="mailto:ne...@ap...">Neeme Praks</a>
* @version $Id: HibernateService.java,v 1.2 2003/06/04 10:44:25 nemecec Exp $
*/
-public interface HibernateService {
+public interface HibernateService extends org.apache.avalon.framework.component.Component {
public static final String ROLE = HibernateService.class.getName();
diff -riuwBb -x CVS avalon/src/test/net/sf/hibernate/avalon/Labor.hbm.xml avalon-patched/src/test/net/sf/hibernate/avalon/Labor.hbm.xml
--- avalon/src/test/net/sf/hibernate/avalon/Labor.hbm.xml 2003-06-18 15:37:50.000000000 +1000
+++ avalon-patched/src/test/net/sf/hibernate/avalon/Labor.hbm.xml 2003-06-18 15:25:31.000000000 +1000
@@ -1,7 +1,7 @@
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
- "-//Hibernate/Hibernate Mapping DTD//EN"
- "http://hibernate.sourceforge.net/hibernate-mapping.dtd">
+ "-//Hibernate/Hibernate Mapping DTD 2.0//EN"
+ "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd">
<hibernate-mapping>
<class name="net.sf.hibernate.avalon.Labor" table="LABOR" >
---------------------------------------------------------------------
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/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-06-21 08:27:52
|
The following issue has been updated:
Updater: Gavin King (mailto:ga...@in...)
Date: Sat, 21 Jun 2003 3:26 AM
Changes:
type changed from Improvement to New Feature
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-143&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-143
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-143
Summary: Criteria.count() and Query.count()
Type: New Feature
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Assignee:
Reporter: Alexey Kaigorodov
Created: Wed, 18 Jun 2003 10:53 PM
Updated: Sat, 21 Jun 2003 3:26 AM
Description:
Add method count in classes Criteria and Query.
Example:
final int PAGE_SIZE;
int position;
...
Query query = ... // build complex query with many parameters
int pageNum = position / PAGE_SIZE + 1;
int pageCount = query.count() / PAGE_SIZE + 1; // <-- HERE
System.out.println("Page " + pageNum + " from " + pageCount);
query.setFirstResult(position);
query.setMaxResults(PAGE_SIZE);
List page = query.list();
System.out.println(page);
Not necessary will twice create the similar Query or Criteria.
By Criteria always easy build sql count query.
For Query.count() throw exception if create sql count query impossible.
---------------------------------------------------------------------
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/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-06-21 08:14:53
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Sat, 21 Jun 2003 3:14 AM
Ah. you threw me off by saying the two queries were equivalent. If you check your SQL, you will find that they are not. The criteria query is doing a bunch of outerjoin fetching that the other is not. You will see the same exception if you add a fetch clause to the HQL.
Anyway, the exception is a well-known problem that occurs only with non-lazy collections. It is one that we will not be fixing because of performance considerations. This is in the Hibernate FAQ.
Make the collection lay and the problem disappears. If you want to fetch it more aggressively, use HQL with a FETCH clause to fetch the collection by outerjoin.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-136
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-136
Summary: Criteria api appears to add elements to a SortedSet before setting their properties
Type: Bug
Status: Closed
Priority: Major
Resolution: WON'T FIX
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee: Gavin King
Reporter: Paul Rivers
Created: Sat, 14 Jun 2003 4:16 PM
Updated: Sat, 21 Jun 2003 3:14 AM
Environment: Eclipse 2.1, Tomcat4.1.24, jdk1.4.1_03
Description:
As I understand it, this query by criteria query:
Criteria criteria = session.createCriteria(EntryDAO.class);
criteria.setFirstResult(rangeStart);
criteria.setMaxResults(rangeSize);
criteria.addOrder(Order.desc("dateCreated"));
entries = criteria.list();
Should return the same results as this one:
Query query = session.createQuery("from EntryDAO order by dateCreated desc");
query.setFirstResult(rangeStart);
query.setMaxResults(rangeSize);
entries = query.list();
The problem is that the normal (second) query executes fine, but the Criteria (first) query throws a NullPointerException. Each entry has a SortedSet of Categories (It's specified in the mapping file). The stack trace for the null pointer exception leads to this line:
result = this.getName().compareTo(otherCategory.getName());
In this function:
public int compareTo(Object o) {
int result;
CategoryDAO otherCategory = (CategoryDAO) o;
result = this.getDisplayIndex() - otherCategory.getDisplayIndex();
if(result == 0) {
result = this.getName().compareTo(otherCategory.getName());
}
return result;
}
The problem appears to be, to me, that for some reason the Criteria API 1. does the database query, 2. adds the new object to the SortedSet, 3. THEN sets it's properties, where it should be 1. doing the query 2. setting the properties, 3. then adding the category to the sortedset.
PLEASE let me know if there's anything I can do to help with the issue, or if there's any other information you would like. Thanks.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/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-06-21 04:58:54
|
Message:
The following issue has been re-assigned.
Assignee: Eric Pugh (mailto:ep...@up...)
Assigner: Gavin King (mailto:ga...@in...)
Date: Fri, 20 Jun 2003 11:58 PM
Comment:
yours :)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-140
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-140
Summary: Changed Avalon component to work with cocoon 2.0.4
Type: Patch
Status: Assigned
Priority: Minor
Project: Hibernate2
Components:
toolset
Assignee: Eric Pugh
Reporter: Scott Payne
Created: Wed, 18 Jun 2003 12:47 AM
Updated: Fri, 20 Jun 2003 11:58 PM
Description:
Simple patch so that the CocoonComponentManager won't throw a ClassCastException when using the HibernateService. It seemed to try to cast it to a Component (fair enough) and this fixed it.
Also a change to the DTD used in the test case, to use the hibernate 2 DTD.
diff -riuwBb -x CVS avalon/src/java/net/sf/hibernate/avalon/HibernateService.java avalon-patched/src/java/net/sf/hibernate/avalon/HibernateService.java
--- avalon/src/java/net/sf/hibernate/avalon/HibernateService.java 2003-06-18 15:37:40.000000000 +1000
+++ avalon-patched/src/java/net/sf/hibernate/avalon/HibernateService.java 2003-06-18 15:21:00.000000000 +1000
@@ -11,7 +11,7 @@
* @author <a href="mailto:ne...@ap...">Neeme Praks</a>
* @version $Id: HibernateService.java,v 1.2 2003/06/04 10:44:25 nemecec Exp $
*/
-public interface HibernateService {
+public interface HibernateService extends org.apache.avalon.framework.component.Component {
public static final String ROLE = HibernateService.class.getName();
diff -riuwBb -x CVS avalon/src/test/net/sf/hibernate/avalon/Labor.hbm.xml avalon-patched/src/test/net/sf/hibernate/avalon/Labor.hbm.xml
--- avalon/src/test/net/sf/hibernate/avalon/Labor.hbm.xml 2003-06-18 15:37:50.000000000 +1000
+++ avalon-patched/src/test/net/sf/hibernate/avalon/Labor.hbm.xml 2003-06-18 15:25:31.000000000 +1000
@@ -1,7 +1,7 @@
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
- "-//Hibernate/Hibernate Mapping DTD//EN"
- "http://hibernate.sourceforge.net/hibernate-mapping.dtd">
+ "-//Hibernate/Hibernate Mapping DTD 2.0//EN"
+ "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd">
<hibernate-mapping>
<class name="net.sf.hibernate.avalon.Labor" table="LABOR" >
---------------------------------------------------------------------
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/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-06-21 04:27:52
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Fri, 20 Jun 2003 11:27 PM
Thanks. I applied this patch.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-144
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-144
Summary: Major (but easy fix) bug in SchemaUpdate
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.0.2
Versions:
2.0 final
Assignee: Gavin King
Reporter: Mathias Bogaert
Created: Thu, 19 Jun 2003 5:29 AM
Updated: Fri, 20 Jun 2003 11:27 PM
Environment: 2.0.1
Description:
It seems that there is a small but major bug in the code generation of SchemaUpdate. It doesn't add a space after 'add column'.
Here is my stacktrace:
alter table addresses add columnversion INTEGER
12:24:51,038 ERROR SchemaUpdate:121 - Error while executing alter table addresses add columnversion INTEGER
java.sql.SQLException: Unexpected token: COLUMNVERSION in statement [alter table addresses add columnversion INTEGER]
at org.hsqldb.Trace.getError(Unknown Source)
at org.hsqldb.jdbcResultSet.<init>(Unknown Source)
at org.hsqldb.jdbcConnection.executeStandalone(Unknown Source)
at org.hsqldb.jdbcConnection.execute(Unknown Source)
at org.hsqldb.jdbcStatement.fetchResult(Unknown Source)
at org.hsqldb.jdbcStatement.executeUpdate(Unknown Source)
at net.sf.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:116)
at com.intrasoft.persistence.hibernate.HibernatePersistenceManager.buildSessionFactory(HibernatePersistenceManager.java:59)
at com.intrasoft.persistence.hibernate.HibernatePersistenceManager.init(HibernatePersistenceManager.java:38)
at com.opensymphony.xwork.interceptor.component.DefaultComponentManager.loadResource(DefaultComponentManager.java:152)
at com.opensymphony.xwork.interceptor.component.DefaultComponentManager.loadResource(DefaultComponentManager.java:137)
at com.opensymphony.xwork.interceptor.component.DefaultComponentManager.initializeComponent(DefaultComponentManager.java:73)
at com.opensymphony.xwork.interceptor.component.ComponentInterceptor.before(ComponentInterceptor.java:29)
at com.opensymphony.xwork.interceptor.AbstractInterceptor.intercept(AbstractInterceptor.java:36)
at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:148)
at com.opensymphony.xwork.interceptor.AbstractInterceptor.intercept(AbstractInterceptor.java:37)
at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:148)
at com.opensymphony.xwork.interceptor.AbstractInterceptor.intercept(AbstractInterceptor.java:37)
at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:148)
at com.opensymphony.xwork.interceptor.AbstractInterceptor.intercept(AbstractInterceptor.java:37)
at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:148)
at com.opensymphony.xwork.interceptor.AbstractInterceptor.intercept(AbstractInterceptor.java:37)
at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:148)
at com.opensymphony.xwork.interceptor.TimerInterceptor.intercept(TimerInterceptor.java:66)
at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:148)
at com.opensymphony.xwork.DefaultActionProxy.execute(DefaultActionProxy.java:108)
at com.opensymphony.webwork.dispatcher.ServletDispatcher.service(ServletDispatcher.java:164)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:1264)
at com.caucho.server.http.FilterChainServlet.doFilter(FilterChainServlet.java:96)
at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:129)
at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:61)
at com.caucho.server.http.FilterChainFilter.doFilter(FilterChainFilter.java:88)
at com.intrasoft.security.LoginFilter.doFilter(LoginFilter.java:76)
at com.caucho.server.http.FilterChainFilter.doFilter(FilterChainFilter.java:88)
at com.intrasoft.security.SecurityFilter.doFilter(SecurityFilter.java:34)
at com.caucho.server.http.FilterChainFilter.doFilter(FilterChainFilter.java:88)
at com.opensymphony.webwork.lifecycle.RequestLifecycleFilter.doFilter(RequestLifecycleFilter.java:61)
at com.caucho.server.http.FilterChainFilter.doFilter(FilterChainFilter.java:88)
at com.caucho.server.http.Invocation.service(Invocation.java:315)
at com.caucho.server.http.CacheInvocation.service(CacheInvocation.java:135)
at com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:246)
at com.caucho.server.http.HttpRequest.handleConnection(HttpRequest.java:164)
at com.caucho.server.TcpConnection.run(TcpConnection.java:139)
at java.lang.Thread.run(Thread.java:534)
---------------------------------------------------------------------
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/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-06-21 03:31:54
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-148 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-148 Summary: Old JCS jar is faster than new one (?) Type: Task Status: Assigned Priority: Major Project: Hibernate2 Versions: 2.0.1 Assignee: Gavin King Reporter: Gavin King Created: Fri, 20 Jun 2003 10:30 PM Updated: Fri, 20 Jun 2003 10:30 PM Description: A user reported that the build of JCS that ships with Hibernate2 is MUCH slower than the earlier build that we were using. We need to verify this and find out why.... --------------------------------------------------------------------- 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/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-06-21 03:16:52
|
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-146 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-146 Summary: Eliminate array creation for single column queries Type: Patch Status: Assigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.0.1 Assignee: Gavin King Reporter: Chris Nokleberg Created: Fri, 20 Jun 2003 1:11 AM Updated: Fri, 20 Jun 2003 10:14 PM Description: IteratorImpl currently created a new Object[] for each row returned from a query. For single column queries the iterator then just pulls the single value out of the array before returning it. This patch removes the array creation for single column queries. BTW, why was the decision made to use a new array for each row? Even in the case of multiple value queries, it would be much more efficient to reuse the same array. The user could copy the values into a new array if so desired. It's probably too late to change this, unfortunately... --------------------------------------------------------------------- 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/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-06-21 03:14:54
|
The following comment has been added to this issue:
Author: Gavin King
Created: Fri, 20 Jun 2003 10:14 PM
Body:
It would be a source of bugs to re-use the same array each time. Anyway the cost of array creation is tiny compared to the cost of hitting the database.
But I will accept you patch. Thanks.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-146
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-146
Summary: Eliminate array creation for single column queries
Type: Patch
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: Chris Nokleberg
Created: Fri, 20 Jun 2003 1:11 AM
Updated: Fri, 20 Jun 2003 1:14 AM
Description:
IteratorImpl currently created a new Object[] for each row returned from a query. For single column queries the iterator then just pulls the single value out of the array before returning it. This patch removes the array creation for single column queries.
BTW, why was the decision made to use a new array for each row? Even in the case of multiple value queries, it would be much more efficient to reuse the same array. The user could copy the values into a new array if so desired. It's probably too late to change this, unfortunately...
---------------------------------------------------------------------
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/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-06-21 03:12:55
|
The following comment has been added to this issue:
Author: Gavin King
Created: Fri, 20 Jun 2003 10:11 PM
Body:
I like this idea. I don't think its hard to make Configuration be serializa=
ble.
However, note that there is additional work done in buildSessionFactory(), =
so you could not completely defray the startup cost.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?=
key=3DHB-147
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-147
Summary: Caching of Configuration
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:=20
core
Assignee:=20
Reporter: Thorsten Sch=C3=A4fer
Created: Fri, 20 Jun 2003 8:12 AM
Updated: Fri, 20 Jun 2003 8:12 AM
Environment: Client applications
Description:
If you use hibernate in a client application, you first have to create a co=
nfiguration. This can take a lot of time (I have four classes and it can ta=
ke up to 30 seconds), because XML processing is quite slow. For small appli=
cations this could be too much.
To solve this problem it would be fine if the created configuration is auto=
matically saved to a file. For the next start, the configuration should loo=
k if a persisted configuration exist and load this instead of parsing the X=
ML mappings again. If such a pre-initialized configuration does not exist, =
the normal approach is taken.
Thorsten
---------------------------------------------------------------------
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/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.
