Menu
▾
▴
hibernate-issues — Hibernate JIRA Notifications
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(32) |
Jun
(175) |
Jul
(209) |
Aug
(302) |
Sep
(287) |
Oct
(339) |
Nov
(314) |
Dec
(329) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(479) |
Feb
(389) |
Mar
(599) |
Apr
(307) |
May
(390) |
Jun
(300) |
Jul
(410) |
Aug
(458) |
Sep
(299) |
Oct
(315) |
Nov
(363) |
Dec
(529) |
| 2005 |
Jan
(568) |
Feb
(434) |
Mar
(1004) |
Apr
(823) |
May
(767) |
Jun
(763) |
Jul
(854) |
Aug
(862) |
Sep
(560) |
Oct
(853) |
Nov
(763) |
Dec
(731) |
| 2006 |
Jan
(776) |
Feb
(608) |
Mar
(657) |
Apr
(424) |
May
(559) |
Jun
(440) |
Jul
(448) |
Aug
(58) |
Sep
|
Oct
(17) |
Nov
(16) |
Dec
(8) |
| 2007 |
Jan
(1) |
Feb
(8) |
Mar
(2) |
Apr
(5) |
May
(3) |
Jun
(3) |
Jul
(3) |
Aug
(16) |
Sep
(10) |
Oct
(4) |
Nov
(4) |
Dec
(4) |
| 2008 |
Jan
(8) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: <leg...@at...> - 2003-07-10 05:27:44
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-170 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-170 Summary: Ablility to generate map file with assigned date as primary key using xdoclet Type: Bug Status: Unassigned Priority: Minor Project: Hibernate2 Components: toolset Versions: 2.0.1 Assignee: Reporter: Dan Tran Created: Thu, 10 Jul 2003 12:27 AM Updated: Thu, 10 Jul 2003 12:27 AM Environment: XDoclet 1.2 beta3 Description: The following class with hibernte tag generates exception when feeding thru xdoclet to generate hbm.xml file package org.glvnsjc.model; /** * @author Dan Tran * @hibernate.class table="day" */ public class Day implements java.io.Serializable { private java.util.Date day; public Day() { } /** * @hibernate.id generator-class="assigned" */ public java.util.Date getDay() { return this.day; } public void setDay(java.util.Date value) { this.day = value; } } here is the stack trace hibernatedoclet] Generating mapping file for org.glvnsjc.model.Day. [hibernatedoclet] org.glvnsjc.model.Day [hibernatedoclet] (TemplateEngine.invokeMethod 541 ) Invoking method fai led: xdoclet.modules.hibernate.HibernateTagsHandler.ifHasCompositeId, line=100 o f template file: jar:file:C:\dev\thirdparty\sourceforge\xdoclet\lib\xdoclet-hibe rnate-module-1.2b4.jar!/xdoclet/modules/hibernate/resources/hibernate.xdt [hibernatedoclet] java.lang.reflect.InvocationTargetException [hibernatedoclet] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native M ethod) --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-07-09 23:39:44
|
The following issue has been updated:
Updater: Gavin King (mailto:ga...@in...)
Date: Wed, 9 Jul 2003 6:39 PM
Changes:
priority changed from Blocker
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-155&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-155
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-155
Summary: Optimistic locking by columns' original values
Type: New Feature
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: Christian Bauer
Created: Tue, 8 Jul 2003 3:36 PM
Updated: Wed, 9 Jul 2003 6:39 PM
Description:
Ability to support optimistic locking by columns' original values. When UPDATE statements
are generated, in addition to the primary key, the WHERE clause includes either all of the
columns' original values, or just the changed columns' original values. This allows
optimistic locking without requiring the datamodel to have a "timestamp" or "version"
column.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-07-09 23:37:43
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-169 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-169 Summary: FK to class with composite PK Type: Bug Status: Assigned Priority: Major Project: Hibernate2 Components: core Versions: 2.0.1 Assignee: Gavin King Reporter: Gavin King Created: Wed, 9 Jul 2003 6:37 PM Updated: Wed, 9 Jul 2003 6:37 PM Description: https://sourceforge.net/forum/forum.php?thread_id=894732&forum_id=128638 I think I found the cause. NormalisedEntityPersister.postInstantiate() seems to lack knowledge of composite objects within ID types (doesn't use getColumnSpan()). By adding / replacing the following code (from EntityPersister) I got it to work: ... Type[] subtypes = actype.getSubtypes(); ... int j = 0; for (int i = 0; i < props.length; i++) { String subidpath = idpath + StringHelper.DOT + props[i]; String[] componentColumns = new String[subtypes[i].getColumnSpan(factory)]; for (int k = 0; k < componentColumns.length; k++) { componentColumns[k] = columns[j++]; } columnNamesByPropertyPath.put(subidpath, componentColumns); mods.put(subidpath, actype.getSubtypes()[i]); } --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-07-09 23:15:48
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 9 Jul 2003 6:14 PM
That should be <many-to-one>, not <property>
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-167
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-167
Summary: Cannot Handle Circular Subclass Reference
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: Hao Chen
Created: Wed, 9 Jul 2003 10:06 AM
Updated: Wed, 9 Jul 2003 6:14 PM
Description:
A super class has a field whose type is a subclass. Looks like Hibernate failed to load the subclass because the super class has not been initialized.
Can we have a better algorithm to deal with this situation?
==============================================================
My configurations:
<hibernate-mapping>
<class
name="BaseEntity"
dynamic-update="false"
dynamic-insert="false"
>
<id name="id" column="id" type="java.lang.Long">
<generator class="native">
</generator>
</id>
<property
name="name"
type="java.lang.String"
update="true"
insert="true"
column="name"
length="100"
not-null="true"
/>
<subclass
name="resource.BaseResource"
dynamic-update="false"
dynamic-insert="false"
>
<property
name="description"
type="java.lang.String"
update="true"
insert="true"
column="description"
length="300"
not-null="true"
/>
<property
name="status"
type="classification.Status"
update="true"
insert="true"
column="status"
not-null="true"
/>
...
<subclass
name="classification.Status"
dynamic-update="false"
dynamic-insert="false"
>
<property
name="description"
type="java.lang.String"
update="true"
insert="true"
column="description"
length="100"
not-null="true"
/>
</subclass>
</subclass>
</class>
</hibernate-mapping>
================================================================================
INFO - Mapping subclass: resource.BaseResource -> BaseEntity
DEBUG - Mapped property: description -> description, type: string
ERROR - Could not compile the mapping document
net.sf.hibernate.MappingException: Could not interpret type: classification.Status
at net.sf.hibernate.cfg.Binder.getTypeFromXML(Binder.java:769)
at net.sf.hibernate.cfg.Binder.bindValue(Binder.java:348)
at net.sf.hibernate.cfg.Binder.propertiesFromXML(Binder.java:872)
at net.sf.hibernate.cfg.Binder.bindSubclass(Binder.java:123)
at net.sf.hibernate.cfg.Binder.propertiesFromXML(Binder.java:882)
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 util.HibernateUtil.getSessionFactory(HibernateUtil.java:29)
at util.HibernateUtil.main(HibernateUtil.java:53)
Exception in thread "main" exception.SystemException: net.sf.hibernate.MappingException: Could not int
erpret type: classification.Status
at util.HibernateUtil.getSessionFactory(HibernateUtil.java:43)
at util.HibernateUtil.main(HibernateUtil.java:53)
Caused by: net.sf.hibernate.MappingException: Could not interpret type: classification.Status
at net.sf.hibernate.cfg.Binder.getTypeFromXML(Binder.java:769)
at net.sf.hibernate.cfg.Binder.bindValue(Binder.java:348)
at net.sf.hibernate.cfg.Binder.propertiesFromXML(Binder.java:872)
at net.sf.hibernate.cfg.Binder.bindSubclass(Binder.java:123)
at net.sf.hibernate.cfg.Binder.propertiesFromXML(Binder.java:882)
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 util.HibernateUtil.getSessionFactory(HibernateUtil.java:29)
... 1 more
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-07-09 22:44:45
|
The following issue has been updated:
Updater: Mike Mosiewicz (mailto:mi...@pr...)
Date: Wed, 9 Jul 2003 5:44 PM
Changes:
Attachment changed to hibernate.jca.multiclassloader.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-168&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-168
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-168
Summary: JCA delayed session factory initialization
Type: Patch
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: Mike Mosiewicz
Created: Wed, 9 Jul 2003 5:43 PM
Updated: Wed, 9 Jul 2003 5:44 PM
Description:
By delaying session factory creation we can use the runtime classloader, not the resource-configuration-time classloader. Thus we are able to configure hibernate for proper set of classes.
This enables connector to deal with multiple or changing classloaders.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-07-09 22:44:44
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-168 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-168 Summary: JCA delayed session factory initialization Type: Patch Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.0.1 Assignee: Reporter: Mike Mosiewicz Created: Wed, 9 Jul 2003 5:43 PM Updated: Wed, 9 Jul 2003 5:43 PM Description: By delaying session factory creation we can use the runtime classloader, not the resource-configuration-time classloader. Thus we are able to configure hibernate for proper set of classes. This enables connector to deal with multiple or changing classloaders. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-07-09 15:07:44
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-167 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-167 Summary: Cannot Handle Circular Subclass Reference Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.0.1 Assignee: Reporter: Hao Chen Created: Wed, 9 Jul 2003 10:06 AM Updated: Wed, 9 Jul 2003 10:06 AM Description: A super class has a field whose type is a subclass. Looks like Hibernate failed to load the subclass because the super class has not been initialized. Can we have a better algorithm to deal with this situation? ============================================================== My configurations: <hibernate-mapping> <class name="BaseEntity" dynamic-update="false" dynamic-insert="false" > <id name="id" column="id" type="java.lang.Long"> <generator class="native"> </generator> </id> <property name="name" type="java.lang.String" update="true" insert="true" column="name" length="100" not-null="true" /> <subclass name="resource.BaseResource" dynamic-update="false" dynamic-insert="false" > <property name="description" type="java.lang.String" update="true" insert="true" column="description" length="300" not-null="true" /> <property name="status" type="classification.Status" update="true" insert="true" column="status" not-null="true" /> ... <subclass name="classification.Status" dynamic-update="false" dynamic-insert="false" > <property name="description" type="java.lang.String" update="true" insert="true" column="description" length="100" not-null="true" /> </subclass> </subclass> </class> </hibernate-mapping> ================================================================================ INFO - Mapping subclass: resource.BaseResource -> BaseEntity DEBUG - Mapped property: description -> description, type: string ERROR - Could not compile the mapping document net.sf.hibernate.MappingException: Could not interpret type: classification.Status at net.sf.hibernate.cfg.Binder.getTypeFromXML(Binder.java:769) at net.sf.hibernate.cfg.Binder.bindValue(Binder.java:348) at net.sf.hibernate.cfg.Binder.propertiesFromXML(Binder.java:872) at net.sf.hibernate.cfg.Binder.bindSubclass(Binder.java:123) at net.sf.hibernate.cfg.Binder.propertiesFromXML(Binder.java:882) 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 util.HibernateUtil.getSessionFactory(HibernateUtil.java:29) at util.HibernateUtil.main(HibernateUtil.java:53) Exception in thread "main" exception.SystemException: net.sf.hibernate.MappingException: Could not int erpret type: classification.Status at util.HibernateUtil.getSessionFactory(HibernateUtil.java:43) at util.HibernateUtil.main(HibernateUtil.java:53) Caused by: net.sf.hibernate.MappingException: Could not interpret type: classification.Status at net.sf.hibernate.cfg.Binder.getTypeFromXML(Binder.java:769) at net.sf.hibernate.cfg.Binder.bindValue(Binder.java:348) at net.sf.hibernate.cfg.Binder.propertiesFromXML(Binder.java:872) at net.sf.hibernate.cfg.Binder.bindSubclass(Binder.java:123) at net.sf.hibernate.cfg.Binder.propertiesFromXML(Binder.java:882) 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 util.HibernateUtil.getSessionFactory(HibernateUtil.java:29) ... 1 more --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-07-09 00:13:44
|
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-145 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-145 Summary: insert for classes with composite-id crashes Type: Bug Status: Assigned Priority: Minor Project: Hibernate2 Assignee: Gavin King Reporter: Hrituc Ovidiu Created: Thu, 19 Jun 2003 10:21 AM Updated: Tue, 8 Jul 2003 7:13 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/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-07-09 00:11:48
|
Message:
The following issue has been resolved as REJECTED.
Resolver: Gavin King
Date: Tue, 8 Jul 2003 7:10 PM
I suppose that the reason for this is that Hibernate is calling setA() while the collection is being initialized.
You just need to make a different setter that your app will use, from the one that Hibernate uses.
---------------------------------------------------------------------
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: Using Sets Before Fully Initialized causes NullPointerException
Type: Bug
Status: Resolved
Priority: Minor
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee: Gavin King
Reporter: Christian Bauer
Created: Tue, 8 Jul 2003 3:30 PM
Updated: Tue, 8 Jul 2003 7:10 PM
Environment: JDK 1.4.1
Description:
one-to-man from A -> B
A.addB(B foo) {
if(null != foo) {
set_of_bs.add(foo);
foo.setA(this);
}
}
B.setA(A bar) {
a = bar;
if(null != a && !a.getBs().contains(this)) {
a.addB(b);
}
}
I'm not sure why but the tempList in the net.sf.hibernate.collection.Set ends up being null
at some point during initialization. endRead is being called twice, the first time its ok
the second time it throws a NullPointerException.
I'm not sure this is a bug with Hibernate or if I should not be maintaining the backwards
pointers in this way.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-07-09 00:04:45
|
The following comment has been added to this issue:
Author: Gavin King
Created: Tue, 8 Jul 2003 7:04 PM
Body:
How exactly is this different to the existing <set where="..."> attribute?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-156
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-156
Summary: Qualified one-to-many
Type: New Feature
Status: Unassigned
Priority: Minor
Project: Hibernate2
Versions:
2.0.1
Assignee:
Reporter: Christian Bauer
Created: Tue, 8 Jul 2003 3:36 PM
Updated: Tue, 8 Jul 2003 3:36 PM
Description:
Ability to add static criteria to what would otherwise be a one-to-many relationship, to
make it into a one-to-one relationship. Example: Account has one-to-many relationship to
Address by way of address.account_id foreign key. However, there is only one "primary"
address for a given account, indicated in the datamodel by address.is_primary = 'Y' for
exactly one row for any given Account. Enhancement would let me create a property
"primaryAddress" on Account that is mapped like a one-to-many except that it also includes
something like "...AND primary = true".
This allows me to obtain an Account object and call getPrimaryAddress and have that SQL
query the address table "WHERE account_id = ? AND is_primary = 'Y'".
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-07-09 00:02:46
|
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-149 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-149 Summary: Using Sets Before Fully Initialized causes NullPointerException Type: Bug Status: Assigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.0.1 Assignee: Gavin King Reporter: Christian Bauer Created: Tue, 8 Jul 2003 3:30 PM Updated: Tue, 8 Jul 2003 7:00 PM Environment: JDK 1.4.1 Description: one-to-man from A -> B A.addB(B foo) { if(null != foo) { set_of_bs.add(foo); foo.setA(this); } } B.setA(A bar) { a = bar; if(null != a && !a.getBs().contains(this)) { a.addB(b); } } I'm not sure why but the tempList in the net.sf.hibernate.collection.Set ends up being null at some point during initialization. endRead is being called twice, the first time its ok the second time it throws a NullPointerException. I'm not sure this is a bug with Hibernate or if I should not be maintaining the backwards pointers in this way. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-07-09 00:00:43
|
The following comment has been added to this issue:
Author: Gavin King
Created: Tue, 8 Jul 2003 6:58 PM
Body:
The you would cast to JDBCTransaction in code?? yuck!
I think there are nicer ways to get your current session....
---------------------------------------------------------------------
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: Add getSession method to Transaction interface
Type: New Feature
Status: Unassigned
Priority: Major
Project: Hibernate2
Fix Fors:
2.1
Versions:
2.0.1
2.0.2
Assignee:
Reporter: Christian Bauer
Created: Tue, 8 Jul 2003 3:31 PM
Updated: Tue, 8 Jul 2003 3:31 PM
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/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-07-08 23:58:43
|
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-151 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-151 Summary: Traversing several joined-subclasses in where clause leaves out inner joins Type: Bug Status: Assigned Priority: Critical Project: Hibernate2 Components: core Versions: 2.0.1 Assignee: Gavin King Reporter: Christian Bauer Created: Tue, 8 Jul 2003 3:32 PM Updated: Tue, 8 Jul 2003 6:57 PM Environment: WSAD 5.0.1, JDK 1.3.1, Oracle 9i, Windows 2000 Description: Class-diagram: a-->b a inherits from b a==b a has relationship to b (Sorry, classnames are in Dutch) Persoon == Beroepsuitoefening Beroepsuitoefening <-- Jurist Jurist == Bevoegdheid Bevoegdheid <-- Beediging <-- Procureurschap If my query contains 'where jurist.persoon.naam like ?', the generated SQL looks like this (which is OK): select count(*) as x0_0_ from jurist persiste0_ inner join beroepsuitoefening persiste0__1 on persiste0_.beg_id=persiste0__1.id, persoon persiste1_ where ( ( persiste1_.naam like ? and persiste0__1.psn_id=persiste1_.id ) ) However, if I start one level deeper in the hierarchy ('where procureurschap.jurist.persoon.naam like ?') the SQL query looks like this: select count(*) as x0_0_ from procureurschap persiste0_ inner join beediging persiste0__1 on persiste0_.bvh_id=persiste0__1.bvh_id inner join bevoegdheid persiste0__2 on persiste0_.bvh_id=persiste0__2.id, jurist persiste1_, persoon persiste2_ where ( ( persiste2_.naam=? and persiste0__2.beg_id=persiste1_.beg_id and persiste1__1.psn_id=persiste2_.id ) ) [Queries are indented to show outline] As you can see, the last clause references persiste1__1, which isn't listed in the from clause. It's intended to, because the pattern matches with the previous example (_1 begin the first innerjoin for persiste1_). It should be an alias for beroepsuitoefening just as it is in the previous example. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-07-08 23:56:43
|
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-153 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-153 Summary: discriminator force true doesn't work Type: Bug Status: Assigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.0.1 Assignee: Gavin King Reporter: Christian Bauer Created: Tue, 8 Jul 2003 3:34 PM Updated: Tue, 8 Jul 2003 6:55 PM Environment: win2000, WSAD v5, DB2, websphere v5 Description: A discriminator force true does not cause Hibernate to ignore unmapped discriminator values, instead WrongClassException is thrown. see http://sourceforge.net/forum/forum.php?thread_id=889426&forum_id=128638 for more info --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-07-08 23:54:43
|
Message:
The following issue has been re-assigned.
Assignee: Gavin King (mailto:ga...@in...)
Assigner: Gavin King (mailto:ga...@in...)
Date: Tue, 8 Jul 2003 6:54 PM
Comment:
Thanks! I will apply this patch :)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-166
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-166
Summary: firebird dialect with support for LIMIT
Type: Patch
Status: Assigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee: Gavin King
Reporter: Christian Bauer
Created: Tue, 8 Jul 2003 3:48 PM
Updated: Tue, 8 Jul 2003 6:54 PM
Description:
Ludovic Orban
tested with firebird 1.0.2 and JayBird type 4 driver
(Patch got lost during JIRA downtime, Christian)
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-07-08 23:54:43
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Tue, 8 Jul 2003 6:52 PM
Remove the column attribute, or Hibernate will ignore the <column> element.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-161
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-161
Summary: sql-type is ignored by net.sf.hibernate.tool.hbm2ddl.SchemaExport
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Versions:
2.0.1
Assignee: Max Rydahl Andersen
Reporter: Christian Bauer
Created: Tue, 8 Jul 2003 3:40 PM
Updated: Tue, 8 Jul 2003 6:52 PM
Description:
I've tried this in a hbm:
<property name="description" column="description" type="string">
<column name="description" sql-type="text" />
</property>
but the SchemaExport generates this in the DDL:
description VARCHAR(255)
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-07-08 23:52:43
|
The following issue has been updated:
Updater: Gavin King (mailto:ga...@in...)
Date: Tue, 8 Jul 2003 6:51 PM
Comment:
Is this really needed? Creating a new Query instance is simple enough....
Changes:
type changed from Bug
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-162&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-162
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-162
Summary: No way to reset the maxResults() on a Query
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: Christian Bauer
Created: Tue, 8 Jul 2003 3:41 PM
Updated: Tue, 8 Jul 2003 6:51 PM
Description:
There is currently no way to reset the maximum number of results (query.setMaxResults(int))
returned from a Query once it has been set to a value. While you can certainly set it to
Integer.MAX_VALUE, that seems impractical. I have tried query.setMaxResults(0) which
produces "zero" results, and query.setMaxResults(-1) which produces an exception.
I have looked at the source code and noticed that internally the value is maintained as an
Integer and initially starts as "null", however they current interface provides no mechanism
to reset the value to "null" as the calling signature is as show above
Query.setMaxResults(int).
My suggestion would be to simply take any value < 1 as a reset.
Cheers, Dawson
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-07-08 23:50:43
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Tue, 8 Jul 2003 6:50 PM
You can easily execute any JDBC you like against the Hibernate connection. It should be easy to develop your own DB abstraction layer to maintain database independence.
This feature request is out of scope of Hibernate.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-163
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-163
Summary: Table locking
Type: New Feature
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: Christian Bauer
Created: Tue, 8 Jul 2003 3:43 PM
Updated: Tue, 8 Jul 2003 6:50 PM
Description:
I would like to have a way to lock objects in a more database
independent way, and in particular to lock a table. Now I need
to make it impossible for two instances of my client application
to perform a long task in parallel, but the present locking doesn't
work with databases that does not provide a "select for update".
On the other side, I guess that most databases provide table level
locking "LOCK TABLE ...". I would be a nice to have, currently I have
to isolate databases that don't support Hibernate locking and do my
own...
Oh, in the case of SapDb the locking problem could be solved by
using a row level lock (available) instead of a select for update.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-07-08 23:48:43
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Tue, 8 Jul 2003 6:47 PM
On some databases you need to set hibernate.query.substitutions, as per the example hibernate.properties.
Perhaps this should be a dialect default property. Resubmit a feature request if you think so...
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-165
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-165
Summary: Where clause not recognising booleans.
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: Christian Bauer
Created: Tue, 8 Jul 2003 3:47 PM
Updated: Tue, 8 Jul 2003 6:47 PM
Environment: jdk1.4.1 on win32(XP) with a MySQL (v3.23.55) back-end.
Description:
SQLException (Column not found) thrown when using 'where blah = false' in a query. Work
around is to change where clause to 'where blah = 0'.
Query (broken version):
"select booking from " +
"from au.com.octarine.bookingengine.model.Booking as booking " +
"where " +
"booking.sheet.courseId = ? and " +
"booking.sheet.year = ? and " +
"booking.sheet.month = ? and " +
"booking.sheet.day = ? and " +
"booking.booked = false and " +
"booking.time between ? and ? "
Query (working version):
"select booking from " +
"from au.com.octarine.bookingengine.model.Booking as booking " +
"where " +
"booking.sheet.courseId = ? and " +
"booking.sheet.year = ? and " +
"booking.sheet.month = ? and " +
"booking.sheet.day = ? and " +
"booking.booked = 0 and " +
"booking.time between ? and ? "
Booking.java:
/**
* Booking.java
*
* Created on Jan 30, 2003, 4:15:10 PM
*/
package au.com.octarine.bookingengine.model;
import java.sql.Time;
/**
* The <code>Booking</code> instance captures the booking information.
*
* @author Andrew
* @version $Revision: $
*/
public class Booking {
// Booking unique id
private int id;
// Owning sheet.
private Sheet sheet;
// Tee
private int teeNumber;
// Time of booking.
private Time time;
// Booked? (yes/no)
private boolean booked;
// Temporary booking? (yes/no)
private boolean temporary;
// Booking userid
private String bookedBy;
// When the booking was made.
private Time bookedWhen;
// Playing userid
private String playerId;
// Player name (if not person who booked).
private String publicName;
/** Default constructor. */
public Booking() {
}
public Booking( Sheet sheet, int teeNumber, Time time ) {
this.sheet = sheet;
this.teeNumber = teeNumber;
this.time = time;
}
public int getId() {
return id;
}
public void setId( int id ) {
this.id = id;
}
public Sheet getSheet() {
return sheet;
}
public void setSheet( Sheet sheet ) {
this.sheet = sheet;
}
public int getTeeNumber() {
return teeNumber;
}
public void setTeeNumber( int teeNumber ) {
this.teeNumber = teeNumber;
}
public Time getTime() {
return time;
}
public void setTime( Time time ) {
this.time = time;
}
public boolean isBooked() {
return booked;
}
public void setBooked( boolean booked ) {
this.booked = booked;
}
public boolean isTemporary() {
return temporary;
}
public void setTemporary( boolean temporary ) {
this.temporary = temporary;
}
public String getBookedBy() {
return bookedBy;
}
public void setBookedBy( String bookedBy ) {
this.bookedBy = bookedBy;
}
public Time getBookedWhen() {
return bookedWhen;
}
public void setBookedWhen( Time bookedWhen ) {
this.bookedWhen = bookedWhen;
}
public String getPlayerId() {
return playerId;
}
public void setPlayerId( String playerId ) {
this.playerId = playerId;
}
public String getPublicName() {
return publicName;
}
public void setPublicName( String publicName ) {
this.publicName = publicName;
}
/** Generate human-readable representation. */
public String toString() {
StringBuffer buf = new StringBuffer( super.toString() );
buf.append( " Booking { " );
// todo: insert contents here
buf.append( " }" );
return buf.toString();
}
}
Booking.hbm.xml:
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd">
<hibernate-mapping>
<class name="au.com.octarine.bookingengine.model.Booking" table="bookings">
<id name="id" column="id" type="int" >
<generator class="identity" />
</id>
<many-to-one name="sheet" column="sheet_id"
class="au.com.octarine.bookingengine.model.Sheet" />
<property name="teeNumber" column="tee_number" type="integer"/>
<property name="time" column="time" type="time"/>
<property name="booked" column="booked" type="boolean"/>
<property name="temporary" column="temporary" type="boolean"/>
<property name="bookedBy" column="booked_by" type="string" length="20" />
<property name="bookedWhen" column="booked_when" type="time"/>
<property name="playerId" column="player_id" type="string" length="20" />
<property name="publicName" column="name" type="string" length="50" />
</class>
</hibernate-mapping>
Generated SQL:
Hibernate: select booking0_.id as id, booking0_.sheet_id as sheet_id, booking0_.tee_number
as tee_number, booking0_.time as time, booking0_.booked as booked, booking0_.temporary as
temporary, booking0_.booked_by as booked_by, booking0_.booked_when as booked_w8_,
booking0_.player_id as player_id, booking0_.name as name from bookings booking0_, sheets
sheet1_ where (sheet1_.course_id=? and booking0_.sheet_id=sheet1_.id)and(sheet1_.year=?
and booking0_.sheet_id=sheet1_.id)and(sheet1_.month=? and
booking0_.sheet_id=sheet1_.id)and(sheet1_.day=? and
booking0_.sheet_id=sheet1_.id)and(booking0_.booked=false )and(booking0_.time between ? and ?
) order by booking0_.tee_number , booking0_.time
Stack trace:
Caused by: java.sql.SQLException: Column not found, message from server: "Unknown column
'false' in 'where clause'"
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1651)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:889)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:956)
at com.mysql.jdbc.Connection.execSQL(Connection.java:1874)
at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1538)
at net.sf.hibernate.impl.BatcherImpl.getResultSet(BatcherImpl.java:62)
at net.sf.hibernate.loader.Loader.getResultSet(Loader.java:537)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:140)
at net.sf.hibernate.loader.Loader.find(Loader.java:604)
at net.sf.hibernate.hql.QueryTranslator.find(QueryTranslator.java:912)
at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1356)
... 44 more
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-07-08 20:50:43
|
The following comment has been added to this issue:
Author: Christian Bauer
Created: Tue, 8 Jul 2003 3:48 PM
Body:
can't find any attachment button so here's the code:
package net.sf.hibernate.dialect;
import java.sql.Types;
import net.sf.hibernate.cfg.Environment;
/**
* An SQL dialect for Firebird.
* @author Ludovic Orban
*/
public class FirebirdDialect extends Dialect {
public FirebirdDialect() {
super();
register( Types.BIT, "SMALLINT" );
register( Types.BIGINT, "NUMERIC(18,0)" );
register( Types.SMALLINT, "SMALLINT" );
register( Types.TINYINT, "SMALLINT" );
register( Types.INTEGER, "INTEGER" );
register( Types.CHAR, "CHAR(1)" );
register( Types.VARCHAR, "VARCHAR($l)" );
register( Types.FLOAT, "FLOAT" );
register( Types.DOUBLE, "DOUBLE PRECISION" );
register( Types.DATE, "DATE" );
register( Types.TIME, "TIME" );
register( Types.TIMESTAMP, "TIMESTAMP" );
register( Types.VARBINARY, "BLOB" );
register( Types.NUMERIC, "NUMERIC(18, $l)" );
register( Types.BLOB, "BLOB" );
register( Types.CLOB, "BLOB SUB_TYPE 1" );
getDefaultProperties().setProperty(Environment.USE_OUTER_JOIN, "true");
getDefaultProperties().setProperty(Environment.STATEMENT_BATCH_SIZE, NO_BATCH);
getDefaultProperties().setProperty(Environment.STATEMENT_CACHE_SIZE, "0");
}
public String getAddColumnString() {
return "add";
}
public String getSequenceNextValString(String sequenceName) {
return "select gen_id( " + sequenceName + ", 1 ) from RDB$DATABASE";
}
public String getCreateSequenceString(String sequenceName) {
return "create generator " + sequenceName;
}
public String getDropSequenceString(String sequenceName) {
return "delete from RDB$GENERATORS where RDB$GENERATOR_NAME = '" +
sequenceName.toUpperCase() + "'";
}
public boolean supportsSequences() {
return true;
}
public boolean supportsLimit() {
return true;
}
public String getLimitString(String sql) {
StringBuffer pagingSelect = new StringBuffer(100);
pagingSelect.append("select first ? skip ?");
int idx = sql.toLowerCase().indexOf("select");
pagingSelect.append(sql.substring(idx + "select".length()));
return pagingSelect.toString();
}
}
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-166
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-166
Summary: firebird dialect with support for LIMIT
Type: Patch
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: Christian Bauer
Created: Tue, 8 Jul 2003 3:48 PM
Updated: Tue, 8 Jul 2003 3:48 PM
Description:
Ludovic Orban
tested with firebird 1.0.2 and JayBird type 4 driver
(Patch got lost during JIRA downtime, Christian)
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-07-08 20:48:44
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-166 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-166 Summary: firebird dialect with support for LIMIT Type: Patch Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.0.1 Assignee: Reporter: Christian Bauer Created: Tue, 8 Jul 2003 3:48 PM Updated: Tue, 8 Jul 2003 3:48 PM Description: Ludovic Orban tested with firebird 1.0.2 and JayBird type 4 driver (Patch got lost during JIRA downtime, Christian) --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-07-08 20:48:43
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-165 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-165 Summary: Where clause not recognising booleans. Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.0.1 Assignee: Reporter: Christian Bauer Created: Tue, 8 Jul 2003 3:47 PM Updated: Tue, 8 Jul 2003 3:47 PM Environment: jdk1.4.1 on win32(XP) with a MySQL (v3.23.55) back-end. Description: SQLException (Column not found) thrown when using 'where blah = false' in a query. Work around is to change where clause to 'where blah = 0'. Query (broken version): "select booking from " + "from au.com.octarine.bookingengine.model.Booking as booking " + "where " + "booking.sheet.courseId = ? and " + "booking.sheet.year = ? and " + "booking.sheet.month = ? and " + "booking.sheet.day = ? and " + "booking.booked = false and " + "booking.time between ? and ? " Query (working version): "select booking from " + "from au.com.octarine.bookingengine.model.Booking as booking " + "where " + "booking.sheet.courseId = ? and " + "booking.sheet.year = ? and " + "booking.sheet.month = ? and " + "booking.sheet.day = ? and " + "booking.booked = 0 and " + "booking.time between ? and ? " Booking.java: /** * Booking.java * * Created on Jan 30, 2003, 4:15:10 PM */ package au.com.octarine.bookingengine.model; import java.sql.Time; /** * The <code>Booking</code> instance captures the booking information. * * @author Andrew * @version $Revision: $ */ public class Booking { // Booking unique id private int id; // Owning sheet. private Sheet sheet; // Tee private int teeNumber; // Time of booking. private Time time; // Booked? (yes/no) private boolean booked; // Temporary booking? (yes/no) private boolean temporary; // Booking userid private String bookedBy; // When the booking was made. private Time bookedWhen; // Playing userid private String playerId; // Player name (if not person who booked). private String publicName; /** Default constructor. */ public Booking() { } public Booking( Sheet sheet, int teeNumber, Time time ) { this.sheet = sheet; this.teeNumber = teeNumber; this.time = time; } public int getId() { return id; } public void setId( int id ) { this.id = id; } public Sheet getSheet() { return sheet; } public void setSheet( Sheet sheet ) { this.sheet = sheet; } public int getTeeNumber() { return teeNumber; } public void setTeeNumber( int teeNumber ) { this.teeNumber = teeNumber; } public Time getTime() { return time; } public void setTime( Time time ) { this.time = time; } public boolean isBooked() { return booked; } public void setBooked( boolean booked ) { this.booked = booked; } public boolean isTemporary() { return temporary; } public void setTemporary( boolean temporary ) { this.temporary = temporary; } public String getBookedBy() { return bookedBy; } public void setBookedBy( String bookedBy ) { this.bookedBy = bookedBy; } public Time getBookedWhen() { return bookedWhen; } public void setBookedWhen( Time bookedWhen ) { this.bookedWhen = bookedWhen; } public String getPlayerId() { return playerId; } public void setPlayerId( String playerId ) { this.playerId = playerId; } public String getPublicName() { return publicName; } public void setPublicName( String publicName ) { this.publicName = publicName; } /** Generate human-readable representation. */ public String toString() { StringBuffer buf = new StringBuffer( super.toString() ); buf.append( " Booking { " ); // todo: insert contents here buf.append( " }" ); return buf.toString(); } } Booking.hbm.xml: <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD//EN" "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd"> <hibernate-mapping> <class name="au.com.octarine.bookingengine.model.Booking" table="bookings"> <id name="id" column="id" type="int" > <generator class="identity" /> </id> <many-to-one name="sheet" column="sheet_id" class="au.com.octarine.bookingengine.model.Sheet" /> <property name="teeNumber" column="tee_number" type="integer"/> <property name="time" column="time" type="time"/> <property name="booked" column="booked" type="boolean"/> <property name="temporary" column="temporary" type="boolean"/> <property name="bookedBy" column="booked_by" type="string" length="20" /> <property name="bookedWhen" column="booked_when" type="time"/> <property name="playerId" column="player_id" type="string" length="20" /> <property name="publicName" column="name" type="string" length="50" /> </class> </hibernate-mapping> Generated SQL: Hibernate: select booking0_.id as id, booking0_.sheet_id as sheet_id, booking0_.tee_number as tee_number, booking0_.time as time, booking0_.booked as booked, booking0_.temporary as temporary, booking0_.booked_by as booked_by, booking0_.booked_when as booked_w8_, booking0_.player_id as player_id, booking0_.name as name from bookings booking0_, sheets sheet1_ where (sheet1_.course_id=? and booking0_.sheet_id=sheet1_.id)and(sheet1_.year=? and booking0_.sheet_id=sheet1_.id)and(sheet1_.month=? and booking0_.sheet_id=sheet1_.id)and(sheet1_.day=? and booking0_.sheet_id=sheet1_.id)and(booking0_.booked=false )and(booking0_.time between ? and ? ) order by booking0_.tee_number , booking0_.time Stack trace: Caused by: java.sql.SQLException: Column not found, message from server: "Unknown column 'false' in 'where clause'" at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1651) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:889) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:956) at com.mysql.jdbc.Connection.execSQL(Connection.java:1874) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1538) at net.sf.hibernate.impl.BatcherImpl.getResultSet(BatcherImpl.java:62) at net.sf.hibernate.loader.Loader.getResultSet(Loader.java:537) at net.sf.hibernate.loader.Loader.doFind(Loader.java:140) at net.sf.hibernate.loader.Loader.find(Loader.java:604) at net.sf.hibernate.hql.QueryTranslator.find(QueryTranslator.java:912) at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1356) ... 44 more --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-07-08 20:46:44
|
The following comment has been added to this issue:
Author: Christian Bauer
Created: Tue, 8 Jul 2003 3:46 PM
Body:
I think this should be solved at the database level, not with ORM. Most good RDBMS support
some way to join databases/schemas. Even some kind of replication would work.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-159
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-159
Summary: Trans-database Support
Type: New Feature
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: Christian Bauer
Created: Tue, 8 Jul 2003 3:38 PM
Updated: Tue, 8 Jul 2003 3:38 PM
Description:
Ability to define an object model, and specify that some classes live in database A, and
some live in database B. Hibernate should assume that it can not join between the databases
and, in fact, the databases may be from different vendors.
I know this can be done by creating multiple Sessions, but I don't think this will make
trans-database relationships work. That is, I need to be able to have 1-1 and 1-M
relationships defined between objects that live in two different databases. When Hibernate
goes to lazily initialize a 1-1 or 1-M relationship, it needs to be able to do so using a
Connection connected to the appropriate database. If M-M can be achieved, as well, so much
the better (will require specification of which database the M-M table lives in, I believe.)
Goal is that a single Session can be used to obtain objects and resulting objects'
relationships all work, even though they may be using Connections from the other database.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-07-08 20:46:44
|
The following comment has been added to this issue:
Author: Christian Bauer
Created: Tue, 8 Jul 2003 3:45 PM
Body:
It seems that this works fine when a property of the second joined-subclass is used in the
query.
If my query only contains
where procureur.jurist.persoon.naam = ?
Hibernate fails, but if my query contains
where procureur.jurist.einddatum = ?
and procureur.jurist.persoon.naam = ?
then everything is fine. It seems that the parser interpretes the path-expression
incorrectly if too many entities are used...
---------------------------------------------------------------------
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: Traversing several joined-subclasses in where clause leaves out inner joins
Type: Bug
Status: Unassigned
Priority: Critical
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: Christian Bauer
Created: Tue, 8 Jul 2003 3:32 PM
Updated: Tue, 8 Jul 2003 3:32 PM
Environment: WSAD 5.0.1, JDK 1.3.1, Oracle 9i, Windows 2000
Description:
Class-diagram:
a-->b a inherits from b
a==b a has relationship to b
(Sorry, classnames are in Dutch)
Persoon == Beroepsuitoefening
Beroepsuitoefening <-- Jurist
Jurist == Bevoegdheid
Bevoegdheid <-- Beediging <-- Procureurschap
If my query contains 'where jurist.persoon.naam like ?', the generated SQL looks like this
(which is OK):
select count(*) as x0_0_
from jurist persiste0_
inner join beroepsuitoefening persiste0__1 on persiste0_.beg_id=persiste0__1.id,
persoon persiste1_
where (
(
persiste1_.naam like ?
and persiste0__1.psn_id=persiste1_.id
)
)
However, if I start one level deeper in the hierarchy ('where
procureurschap.jurist.persoon.naam like ?') the SQL query looks like this:
select count(*) as x0_0_
from procureurschap persiste0_
inner join beediging persiste0__1 on persiste0_.bvh_id=persiste0__1.bvh_id
inner join bevoegdheid persiste0__2 on persiste0_.bvh_id=persiste0__2.id,
jurist persiste1_,
persoon persiste2_
where (
(
persiste2_.naam=?
and persiste0__2.beg_id=persiste1_.beg_id
and persiste1__1.psn_id=persiste2_.id
)
)
[Queries are indented to show outline]
As you can see, the last clause references persiste1__1, which isn't listed in the from
clause. It's intended to, because the pattern matches with the previous example (_1 begin
the first innerjoin for persiste1_). It should be an alias for beroepsuitoefening just as it
is in the previous example.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-07-08 20:46:44
|
The following comment has been added to this issue:
Author: Christian Bauer
Created: Tue, 8 Jul 2003 3:44 PM
Body:
Gavin, just saw your response in the discussion thread. I'm wondering if you removed/closed
the original issue that I raised because I couldn't find it (HB-151). I thought it must have
been lost so I've re-entered it as you can see.
I understand your comment regarding that the method should not be added to the interface
because a JTA transaction may not be associated with just one Session. This enhancement
would only be good for JDBC transactions which are bound to one session. How about adding
the getSession method to the JDBCTransaction class so then I can at least retrieve the
Session by casting. If the transaction is not an instance of JDBCTransaction my code will
throw some sort of exception.
---------------------------------------------------------------------
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: Add getSession method to Transaction interface
Type: New Feature
Status: Unassigned
Priority: Major
Project: Hibernate2
Fix Fors:
2.1
Versions:
2.0.1
2.0.2
Assignee:
Reporter: Christian Bauer
Created: Tue, 8 Jul 2003 3:31 PM
Updated: Tue, 8 Jul 2003 3:31 PM
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/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
93 messages has been excluded from this view by a project administrator.
