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: Todd S. \(tshoenfe\) <tsh...@ci...> - 2003-06-21 00:33:42
|
Hi, I'm just beginning to experiment with Hibernate. While creating new tables/classes works beautifully, I'm having difficulty integrating new tables with existing ones. The new tables must contain keys to existing legacy Oracle tables, but the new tables will be created in a different schema. I need the classes for the new tables to reference the existing tables as foreign keys. I've written two separate mapping files for this. One intended to map to the new tables and the other to map to the existing tables. I'm running CodeGenerator with both, but SchemaExport only with the former because I can't modify the existing tables. Naturally when I run SchemaExport with the latter, I receive the expected Oracle errors telling me I can't modify the existing tables. That's a good thing, since I don't want to do that anyway. The mapping for the new tables is: <hibernate-mapping> <class name="foo" schema="New" table="new_table"> <id>...</id> <property name="bar_key" type="java.lang.Integer" length="64" not-null="true" column="bar_key"/> <many-to-one name="bar" class="bar" column="bar_key"/> </class> </hibernate-mapping> The mapping for the existing tables is: <hibernate-mapping> <class name="bar" schema="Old" table="existing_table"> <id>...</id> <property name="bar_key" type="java.lang.Integer" length="64" not-null="true" column="bar_key"> </class> </hibernate-mapping> When I run SchemaExport with the new table's mapping file, the error I receive is: [java] Error creating schema An association refers to an unmapped class: bar [java] net.sf.hibernate.MappingException: An association refers to an unmapped class: bar It appears SchemaExport doesn't "know" about the legacy tables, because it didn't make them. How do I get SchemaExport to create tables for one mapping file but not for the other, while allowing foreign key references from the new to the old? TIA, Todd |
|
From: <leg...@at...> - 2003-06-20 13:13:52
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- 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 |
|
From: <leg...@at...> - 2003-06-20 07:38:52
|
The following issue has been updated:
Updater: Mathias Bogaert (mailto:pa...@pa...)
Date: Fri, 20 Jun 2003 2:38 AM
Comment:
Attached patch.
Changes:
Attachment changed from to hb144.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-144&page=history
---------------------------------------------------------------------
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: Assigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee: Gavin King
Reporter: Mathias Bogaert
Created: Thu, 19 Jun 2003 5:29 AM
Updated: Fri, 20 Jun 2003 2:38 AM
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-20 06:14:51
|
The following issue has been updated:
Updater: Chris Nokleberg (mailto:ch...@si...)
Date: Fri, 20 Jun 2003 1:14 AM
Changes:
Attachment changed from to one-column-no-array.txt
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-146&page=history
---------------------------------------------------------------------
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-20 06:11:52
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- 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:11 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-20 00:11:56
|
Message:
The following issue has been re-assigned.
Assignee: Gavin King (mailto:ga...@in...)
Assigner: Gavin King (mailto:ga...@in...)
Date: Thu, 19 Jun 2003 7:10 PM
Comment:
Woops!
Must be a problem with one of the Dialects. Which dialect are you using?
---------------------------------------------------------------------
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: Assigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee: Gavin King
Reporter: Mathias Bogaert
Created: Thu, 19 Jun 2003 5:29 AM
Updated: Thu, 19 Jun 2003 7:10 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-20 00:11:55
|
The following comment has been added to this issue:
Author: Gavin King
Created: Thu, 19 Jun 2003 7:10 PM
Body:
Oh. Silly question .... HSQLDB...
---------------------------------------------------------------------
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: Assigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee: Gavin King
Reporter: Mathias Bogaert
Created: Thu, 19 Jun 2003 5:29 AM
Updated: Thu, 19 Jun 2003 7:10 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-20 00:09:53
|
The following comment has been added to this issue:
Author: Gavin King
Created: Thu, 19 Jun 2003 7:08 PM
Body:
Well, this is certainly not a generic problem with composite-id mappings, since they work perfectly in the test suite.
So it looks like something special in your case.
(1) You would need to give much more information.
(2) What reason do you have for believing that this is a problem with *Hibernate* and not with your code or the JDBC driver?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-145
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-145
Summary: insert for classes with composite-id crashes
Type: Bug
Status: Unassigned
Priority: Critical
Project: Hibernate2
Assignee:
Reporter: Hrituc Ovidiu
Created: Thu, 19 Jun 2003 10:21 AM
Updated: Thu, 19 Jun 2003 10:21 AM
Environment: W2k professional, SQL Server 2k, OC4J
Description:
Insert for classes with composite-id crashes when persisting to SQL Server 2000.
The composite id consists of the COD, DATA_FIN combination. I am trying to keep the history of a person in the same table and the current record to be the combination (COD_Value, 01/01/3000)
The current manager's data gets pulled out with a many-to-one relationship with a composite fk (MGR_ID, BOGUS_DT_FIN).
Loading goes ok.
Insert doesn't, the exceptions look like this:
Hibernate: insert into PERSON (PKID, NAME, DATA_INI, DEPT_ID, MGR_ID, BOGUS_DT_FIN, COD, DATA_FIN) values (?, ?, ?, ?, ?, ?, ?, ?)
Jun 19, 2003 6:02:16 PM net.sf.hibernate.util.JDBCExceptionReporter logExceptions
WARNING: SQL Error: 0, SQLState: 07009
Jun 19, 2003 6:02:16 PM net.sf.hibernate.util.JDBCExceptionReporter logExceptions
SEVERE: [Microsoft][SQLServer 2000 Driver for JDBC]Invalid parameter binding(s).
Jun 19, 2003 6:02:17 PM net.sf.hibernate.JDBCException <init>
SEVERE: Could not synchronize database state with session
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Invalid parameter binding(s).
at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.base.BasePreparedStatement.validateParameterIndex(Unknown Source)
at com.microsoft.jdbc.base.BasePreparedStatement.setObjectInternal(Unknown Source)
at com.microsoft.jdbc.base.BasePreparedStatement.setTimestamp(Unknown Source)
at com.evermind.sql.FilterPreparedStatement.setTimestamp(FilterPreparedStatement.java:394)
at com.evermind.sql.FilterPreparedStatement.setTimestamp(FilterPreparedStatement.java:394)
at net.sf.hibernate.type.TimestampType.set(TimestampType.java:27)
at net.sf.hibernate.type.NullableType.nullSafeSet(NullableType.java:46)
at net.sf.hibernate.type.NullableType.nullSafeSet(NullableType.java:31)
at net.sf.hibernate.type.ComponentType.nullSafeSet(ComponentType.java:163)
at net.sf.hibernate.persister.EntityPersister.dehydrate(EntityPersister.java:369)
at net.sf.hibernate.persister.EntityPersister.insert(EntityPersister.java:446)
at net.sf.hibernate.impl.ScheduledInsertion.execute(ScheduledInsertion.java:20)
at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2064)
at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2036)
at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:1980)
at it.saga.library.commonDataTypes.impl.CdtBLGBaseSessionBean.save(CdtBLGBaseSessionBean.java:247)
at CdtBLGPerson_StatelessSessionBeanWrapper10.save(CdtBLGPerson_StatelessSessionBeanWrapper10.java:133)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:119)
at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:48)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:797)
at java.lang.Thread.run(Thread.java:536)
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/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-20 00:09:53
|
The following issue has been updated:
Updater: Gavin King (mailto:ga...@in...)
Date: Thu, 19 Jun 2003 7:09 PM
Changes:
priority changed from Critical to Minor
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-145&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-145
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-145
Summary: insert for classes with composite-id crashes
Type: Bug
Status: Unassigned
Priority: Minor
Project: Hibernate2
Assignee:
Reporter: Hrituc Ovidiu
Created: Thu, 19 Jun 2003 10:21 AM
Updated: Thu, 19 Jun 2003 7:09 PM
Environment: W2k professional, SQL Server 2k, OC4J
Description:
Insert for classes with composite-id crashes when persisting to SQL Server 2000.
The composite id consists of the COD, DATA_FIN combination. I am trying to keep the history of a person in the same table and the current record to be the combination (COD_Value, 01/01/3000)
The current manager's data gets pulled out with a many-to-one relationship with a composite fk (MGR_ID, BOGUS_DT_FIN).
Loading goes ok.
Insert doesn't, the exceptions look like this:
Hibernate: insert into PERSON (PKID, NAME, DATA_INI, DEPT_ID, MGR_ID, BOGUS_DT_FIN, COD, DATA_FIN) values (?, ?, ?, ?, ?, ?, ?, ?)
Jun 19, 2003 6:02:16 PM net.sf.hibernate.util.JDBCExceptionReporter logExceptions
WARNING: SQL Error: 0, SQLState: 07009
Jun 19, 2003 6:02:16 PM net.sf.hibernate.util.JDBCExceptionReporter logExceptions
SEVERE: [Microsoft][SQLServer 2000 Driver for JDBC]Invalid parameter binding(s).
Jun 19, 2003 6:02:17 PM net.sf.hibernate.JDBCException <init>
SEVERE: Could not synchronize database state with session
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Invalid parameter binding(s).
at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.base.BasePreparedStatement.validateParameterIndex(Unknown Source)
at com.microsoft.jdbc.base.BasePreparedStatement.setObjectInternal(Unknown Source)
at com.microsoft.jdbc.base.BasePreparedStatement.setTimestamp(Unknown Source)
at com.evermind.sql.FilterPreparedStatement.setTimestamp(FilterPreparedStatement.java:394)
at com.evermind.sql.FilterPreparedStatement.setTimestamp(FilterPreparedStatement.java:394)
at net.sf.hibernate.type.TimestampType.set(TimestampType.java:27)
at net.sf.hibernate.type.NullableType.nullSafeSet(NullableType.java:46)
at net.sf.hibernate.type.NullableType.nullSafeSet(NullableType.java:31)
at net.sf.hibernate.type.ComponentType.nullSafeSet(ComponentType.java:163)
at net.sf.hibernate.persister.EntityPersister.dehydrate(EntityPersister.java:369)
at net.sf.hibernate.persister.EntityPersister.insert(EntityPersister.java:446)
at net.sf.hibernate.impl.ScheduledInsertion.execute(ScheduledInsertion.java:20)
at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2064)
at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2036)
at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:1980)
at it.saga.library.commonDataTypes.impl.CdtBLGBaseSessionBean.save(CdtBLGBaseSessionBean.java:247)
at CdtBLGPerson_StatelessSessionBeanWrapper10.save(CdtBLGPerson_StatelessSessionBeanWrapper10.java:133)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:119)
at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:48)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:797)
at java.lang.Thread.run(Thread.java:536)
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/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-19 15:22:51
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-145 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-145 Summary: insert for classes with composite-id crashes Type: Bug Status: Unassigned Priority: Critical Project: Hibernate2 Assignee: Reporter: Hrituc Ovidiu Created: Thu, 19 Jun 2003 10:21 AM Updated: Thu, 19 Jun 2003 10:21 AM Environment: W2k professional, SQL Server 2k, OC4J Description: Insert for classes with composite-id crashes when persisting to SQL Server 2000. The composite id consists of the COD, DATA_FIN combination. I am trying to keep the history of a person in the same table and the current record to be the combination (COD_Value, 01/01/3000) The current manager's data gets pulled out with a many-to-one relationship with a composite fk (MGR_ID, BOGUS_DT_FIN). Loading goes ok. Insert doesn't, the exceptions look like this: Hibernate: insert into PERSON (PKID, NAME, DATA_INI, DEPT_ID, MGR_ID, BOGUS_DT_FIN, COD, DATA_FIN) values (?, ?, ?, ?, ?, ?, ?, ?) Jun 19, 2003 6:02:16 PM net.sf.hibernate.util.JDBCExceptionReporter logExceptions WARNING: SQL Error: 0, SQLState: 07009 Jun 19, 2003 6:02:16 PM net.sf.hibernate.util.JDBCExceptionReporter logExceptions SEVERE: [Microsoft][SQLServer 2000 Driver for JDBC]Invalid parameter binding(s). Jun 19, 2003 6:02:17 PM net.sf.hibernate.JDBCException <init> SEVERE: Could not synchronize database state with session java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Invalid parameter binding(s). at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source) at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source) at com.microsoft.jdbc.base.BasePreparedStatement.validateParameterIndex(Unknown Source) at com.microsoft.jdbc.base.BasePreparedStatement.setObjectInternal(Unknown Source) at com.microsoft.jdbc.base.BasePreparedStatement.setTimestamp(Unknown Source) at com.evermind.sql.FilterPreparedStatement.setTimestamp(FilterPreparedStatement.java:394) at com.evermind.sql.FilterPreparedStatement.setTimestamp(FilterPreparedStatement.java:394) at net.sf.hibernate.type.TimestampType.set(TimestampType.java:27) at net.sf.hibernate.type.NullableType.nullSafeSet(NullableType.java:46) at net.sf.hibernate.type.NullableType.nullSafeSet(NullableType.java:31) at net.sf.hibernate.type.ComponentType.nullSafeSet(ComponentType.java:163) at net.sf.hibernate.persister.EntityPersister.dehydrate(EntityPersister.java:369) at net.sf.hibernate.persister.EntityPersister.insert(EntityPersister.java:446) at net.sf.hibernate.impl.ScheduledInsertion.execute(ScheduledInsertion.java:20) at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2064) at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2036) at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:1980) at it.saga.library.commonDataTypes.impl.CdtBLGBaseSessionBean.save(CdtBLGBaseSessionBean.java:247) at CdtBLGPerson_StatelessSessionBeanWrapper10.save(CdtBLGPerson_StatelessSessionBeanWrapper10.java:133) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:119) at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:48) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:797) at java.lang.Thread.run(Thread.java:536) --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/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-19 10:29:55
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- 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: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.0 final Assignee: Reporter: Mathias Bogaert Created: Thu, 19 Jun 2003 5:29 AM Updated: Thu, 19 Jun 2003 5:29 AM 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-19 06:31:01
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Thu, 19 Jun 2003 1:30 AM
Body:
aargh - it's because <set>'s sort defaults to "unsorted" in the DTD, but <map>'s set is just "implied" ;(
Why is that ? Gavin ?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-142
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-142
Summary: Wrong java code genaration with <map> element
Type: Bug
Status: Assigned
Priority: Minor
Project: Hibernate2
Components:
toolset
Versions:
2.0 final
Assignee: Max Rydahl Andersen
Reporter: Oscar Picasso
Created: Wed, 18 Jun 2003 10:13 PM
Updated: Thu, 19 Jun 2003 12:34 AM
Description:
The CodeGenerator produce amap property of type java.util.SortedMap instead of a java.util.Map for a <map> element with no sort attribute.
This produce a ClassCastException if we try to save an entity of the generated 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/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-19 06:29:11
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Thu, 19 Jun 2003 1:28 AM
Body:
Things would go a lot faster if you provided an example hbm.xml file - because the current test I got works....?
Can you provide a small(!) hbm.xml file that "misbehaves" ?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-142
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-142
Summary: Wrong java code genaration with <map> element
Type: Bug
Status: Assigned
Priority: Minor
Project: Hibernate2
Components:
toolset
Versions:
2.0 final
Assignee: Max Rydahl Andersen
Reporter: Oscar Picasso
Created: Wed, 18 Jun 2003 10:13 PM
Updated: Thu, 19 Jun 2003 12:34 AM
Description:
The CodeGenerator produce amap property of type java.util.SortedMap instead of a java.util.Map for a <map> element with no sort attribute.
This produce a ClassCastException if we try to save an entity of the generated 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/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-19 05:35:07
|
Message:
The following issue has been re-assigned.
Assignee: Max Rydahl Andersen (mailto:xa...@xa...)
Assigner: Gavin King (mailto:ga...@in...)
Date: Thu, 19 Jun 2003 12:34 AM
Comment:
this ones for you....
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-142
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-142
Summary: Wrong java code genaration with <map> element
Type: Bug
Status: Assigned
Priority: Minor
Project: Hibernate2
Components:
toolset
Versions:
2.0 final
Assignee: Max Rydahl Andersen
Reporter: Oscar Picasso
Created: Wed, 18 Jun 2003 10:13 PM
Updated: Thu, 19 Jun 2003 12:34 AM
Description:
The CodeGenerator produce amap property of type java.util.SortedMap instead of a java.util.Map for a <map> element with no sort attribute.
This produce a ClassCastException if we try to save an entity of the generated 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/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-19 03:55:10
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- 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: Improvement Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Assignee: Reporter: Alexey Kaigorodov Created: Wed, 18 Jun 2003 10:53 PM Updated: Wed, 18 Jun 2003 10:53 PM 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-19 03:16:12
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-142 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-142 Summary: Wrong java code genaration with <map> element Type: Bug Status: Unassigned Priority: Minor Project: Hibernate2 Components: toolset Versions: 2.0 final Assignee: Reporter: Oscar Picasso Created: Wed, 18 Jun 2003 10:13 PM Updated: Wed, 18 Jun 2003 10:13 PM Description: The CodeGenerator produce amap property of type java.util.SortedMap instead of a java.util.Map for a <map> element with no sort attribute. This produce a ClassCastException if we try to save an entity of the generated 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/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-19 02:42:02
|
The following comment has been added to this issue:
Author: Paul Rivers
Created: Wed, 18 Jun 2003 9:41 PM
Body:
<p>Unfortunately I got sick today so I wasn't able to go on vacation, but I came up with as simple as a test case as I could get.
<p>Source code is at:
<br>http://paulrivers.dnsalias.com/HibernateBug.zip
<br>Install source code (It's an Eclipse2.1.0 project)
<p>Start up a MySQL server.
<br>Create a database named "hibernatebug"
<br>Create a user for the database named "hibernatebug" with a password of "hibernatebug"
<p>Run hibernatebug.MainInitializeTestData to create the tables and the data
<br>Run hibernatebug.MainDoQueryThatCrashes. A NullPointerException is thrown that shouldn't be thrown.
<p>If you add
<br>this.setName("");
<br>in the CategoryDAO default constructor, no NullPointerException
<br>is thrown because the name is set by the default constructor. (Although it hasn't been set
<br>by a call to setName() yet)
---------------------------------------------------------------------
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: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee:
Reporter: Paul Rivers
Created: Sat, 14 Jun 2003 4:16 PM
Updated: Sat, 14 Jun 2003 4:16 PM
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-18 16:00:01
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-141 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-141 Summary: NullpointerException Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.0 final Assignee: Reporter: Mathias Bogaert Created: Wed, 18 Jun 2003 10:58 AM Updated: Wed, 18 Jun 2003 10:58 AM Description: Probably a bug in my own XML files, but a nullpointer is always wrong: java.lang.NullPointerException at net.sf.hibernate.cfg.Binder.getTypeFromXML(Binder.java:762) at net.sf.hibernate.cfg.Binder.bindValue(Binder.java:348) at net.sf.hibernate.cfg.Binder.bindIntegerValue(Binder.java:489) at net.sf.hibernate.cfg.Binder.bindListSecondPass(Binder.java:919) at net.sf.hibernate.cfg.Binder$ListSecondPass.secondPass(Binder.java:1178) at net.sf.hibernate.cfg.Binder$SecondPass.doSecondPass(Binder.java:1116) at net.sf.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:495) at net.sf.hibernate.cfg.Configuration.generateSchemaUpdateScript(Configuration.java:433) at net.sf.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:105) 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.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:82) 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:163) 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-18 06:40:11
|
The following comment has been added to this issue:
Author: Antoni Reus
Created: Wed, 18 Jun 2003 1:39 AM
Body:
AFAIK "true" is standard SQL-92.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-134
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-134
Summary: the "where" attribute in collection mapping generates incorrect sql
Type: Bug
Status: Closed
Priority: Major
Resolution: WON'T FIX
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee: Gavin King
Reporter: Antoni Reus
Created: Fri, 13 Jun 2003 6:47 AM
Updated: Sat, 14 Jun 2003 4:54 AM
Environment: RedHat Linux 7.2, JBoss 3.2.1, J2SDK 1.4.1_02, PostgreSQL 7.3.2
Description:
I have a mapping with the following set:
....
<set
name="fillsPublicats"
order-by="data desc"
inverse="true"
lazy="true"
cascade="all"
where="publicat = true" >
<jcs-cache usage="read-write"/>
<key column="pare_id" />
<one-to-many class="org.ibit.foros.model.Missatge"/>
</set>
....
When the Collection gets initialized it generates the query with this where clause:
WHERE FO_MI0_.pare_id=? and FO_MI0_.publicat = FO_MI0_.true
^^^^^^^^
ORDER BY FO_MI0_.data desc;
that throws a JDBCException
while the expected would be:
WHERE FO_MI0_.pare_id=? and FO_MI0_.publicat = true
ORDER BY FO_MI0_.data desc;
---------------------------------------------------------------------
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-18 05:48:02
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- 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: Unassigned Priority: Minor Project: Hibernate2 Components: toolset Assignee: Reporter: Scott Payne Created: Wed, 18 Jun 2003 12:47 AM Updated: Wed, 18 Jun 2003 12:47 AM 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-17 19:09:16
|
The following comment has been added to this issue:
Author: Paul Rivers
Created: Tue, 17 Jun 2003 2:07 PM
Body:
I will be on vacation for the rest of the week, but I will work on a simple test case when I return.
---------------------------------------------------------------------
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: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee:
Reporter: Paul Rivers
Created: Sat, 14 Jun 2003 4:16 PM
Updated: Sat, 14 Jun 2003 4:16 PM
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-17 19:07:20
|
The following comment has been added to this issue:
Author: Paul Rivers
Created: Tue, 17 Jun 2003 2:06 PM
Body:
FYI: I will be on vacation, but I will work on creating a simple test case when I get back.
---------------------------------------------------------------------
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: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee:
Reporter: Paul Rivers
Created: Sat, 14 Jun 2003 4:16 PM
Updated: Sat, 14 Jun 2003 4:16 PM
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-17 15:16:03
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-139 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-139 Summary: Relax rowcount to be > instead of equal to account for triggers. Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.0 final Assignee: Reporter: Don Eddleman Created: Tue, 17 Jun 2003 10:15 AM Updated: Tue, 17 Jun 2003 10:15 AM Environment: All OSs, SQLServer and more than likely any other DB that supports triggers. Description: Within the NonBatchingBatcher class the check for row count to determine success should be relaxed to rowCount >= expected so that any triggers defined on tables affected by the insert/update will not cause a txn to fail just because they fired. --------------------------------------------------------------------- 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-17 12:31:01
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- 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: Tue, 17 Jun 2003 7:30 AM 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-17 10:48:16
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Tue, 17 Jun 2003 5:47 AM
CounterGenerator was not a good implementation. I have deprecated it in favor of IncremementGenerator.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-127
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-127
Summary: CounterGenerator Bug
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.0.1
Versions:
2.0 final
Assignee: Gavin King
Reporter: Maks Glukhovtsev
Created: Tue, 10 Jun 2003 8:23 AM
Updated: Tue, 17 Jun 2003 5:47 AM
Environment: Sybase 11.9.2
Description:
When using "vm" generator, experiencing problem of trying to insert a non-unique value of PK.
When sleep() inserted in generate() (just for test purposes), problem disappeared.
So, with minor changes:
private static long counter = 0;
protected long getCount() {
synchronized(CounterGenerator.class) {
if (counter==0) counter=System.currentTimeMillis();
return counter++;
}
}
public Serializable generate(SessionImplementor cache, Object obj) {
return new Long( getCount() );
}
problem has been resolved.
please.. do something more serious about it :)
---------------------------------------------------------------------
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.
