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-17 14:16:43
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-204 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-204 Summary: Problem with Query and LIMIT (HSQL) Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.0.1 Assignee: Reporter: Sebastien Guimont Created: Thu, 17 Jul 2003 9:15 AM Updated: Thu, 17 Jul 2003 9:15 AM Description: Reference: http://sourceforge.net/forum/message.php?msg_id=2086382 I use HyperSQL 1.7.2 alpha M. /** Code sampl **/ hibernateSession = getSession(session); Query hibernateQuery = hibernateSession.createQuery(query); for (int i = 0; i < params.length; i++) { hibernateQuery.setParameter(i, params[i]); } hibernateQuery.setFirstResult(startRow); hibernateQuery.setMaxResults(resultSize); results = hibernateQuery.list(); /** Exception **/ When I call the list method I got this exception: Could not execute query: Wrong data type: LIMIT n m in statement [select limit 'CA' 1 referenceValue.REF_VAL_ID as REF_VAL_ID, referenceValue.CITY_CNTRY_ID as CITY_CN11_, referenceValue.CITY_STATEPROV_ID as CITY_ST12_, referenceValue.UPID as UPID, referenceValue.CD as CD, referenceValue.CREATED as CREATED, referenceValue.CREATED_BY as CREATED_BY, referenceValue.LAST_UPD as LAST_UPD, referenceValue.LAST_UPD_BY as LAST_UPD8_, referenceValue.REF_ORDER as REF_ORDER, referenceValue.DESC_ID as DESC_ID from REF_VAL referenceValue, REF_VAL countryr0_, DESCRIPT descript1_ where referenceValue.TYP='SYS_CITY' and referenceValue.DESC_ID=descript1_.DESC_ID and (((countryr0_.CD=25 and referenceValue.CITY_CNTRY_ID=countryr0_.REF_VAL_ID))) order by descript1_.DEFAULT_DESC asc] It looks like the parameters list for the prepared statement are not ordered correctly. --------------------------------------------------------------------- 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-17 08:38:43
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-203 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-203 Summary: Re-use 1 class over multiple tables w/ same schema Type: New Feature Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.0 final Assignee: Reporter: Sam Bravard Created: Thu, 17 Jul 2003 3:38 AM Updated: Thu, 17 Jul 2003 3:38 AM Environment: All Description: As far as I can tell, hibernate forces you to apply a single bean against a single table. In comparison to how one normally handles larger multi-table applications in SQL, the one-class to one-table restriction is very limiting. In many rea-world cases you tend to use multiple tables with identical column layouts (deleted but archived entires, holding queues, etc). Hibernate doesn't appear to support this methodology easily without creating numerous duplicate bean objects that only differ in their 'table' attribute in the .hbm.xml file. It would be terrific if hibernate could support something along the lines of: 'select cat.name from eg.Cat("tablename") as cat' so we could easily retarget the table. (the above is just an example - better syntax welcome). --------------------------------------------------------------------- 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-17 01:38:43
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 16 Jul 2003 8:37 PM
Thanks, i fixed it.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-201
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-201
Summary: StringBuffer.indexOf is used in QueryJoinFragment - breaks JDK 1.3
Type: Bug
Status: Closed
Priority: Critical
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.0.2
Versions:
2.0 final
Assignee: Gavin King
Reporter: Mathias Bogaert
Created: Wed, 16 Jul 2003 10:41 AM
Updated: Wed, 16 Jul 2003 8:37 PM
Environment: 2.0.2 from CVS
Description:
StringBuffer.indexOf (a JDK 1.4 only method) is used in QueryJoinFragment - breaks JDK 1.3 required by eg. WLS 7.0.
---------------------------------------------------------------------
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-17 00:45:47
|
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-200 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-200 Summary: subclass is not used when using query by criteria API Type: Bug Status: Assigned Priority: Major Project: Hibernate2 Versions: 2.0.1 Assignee: Gavin King Reporter: Machiel Groeneveld Created: Wed, 16 Jul 2003 9:49 AM Updated: Wed, 16 Jul 2003 7:44 PM Description: I have a problem with subclasses. For example an abstract Parent as the parent and Child1 and Child2 as subclasses of Parent. When I use this: Criteria criteria = sessie.createCriteria(Child2 .class); criteria.add(anExpression); Then criteria.list() gives me a list containing all subclasses of Parent which match the gives expressions. I snippet from the config file (edited): <class "Parent" table="table"> <id name="id" column="uid" type="long" unsaved-value="0"> <generator class="native"/> </id> <discriminator column="klasse" type="string"/> <property name="message"/> <subclass name="Child1"/> <subclass name="Child2"/> --------------------------------------------------------------------- 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-17 00:45:45
|
Message:
The following issue has been re-assigned.
Assignee: Gavin King (mailto:ga...@in...)
Assigner: Gavin King (mailto:ga...@in...)
Date: Wed, 16 Jul 2003 7:44 PM
Comment:
Thanks! Lucky to catch this now
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-201
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-201
Summary: StringBuffer.indexOf is used in QueryJoinFragment - breaks JDK 1.3
Type: Bug
Status: Assigned
Priority: Critical
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee: Gavin King
Reporter: Mathias Bogaert
Created: Wed, 16 Jul 2003 10:41 AM
Updated: Wed, 16 Jul 2003 7:44 PM
Environment: 2.0.2 from CVS
Description:
StringBuffer.indexOf (a JDK 1.4 only method) is used in QueryJoinFragment - breaks JDK 1.3 required by eg. WLS 7.0.
---------------------------------------------------------------------
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-17 00:45: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-202 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-202 Summary: Fetched collections are not cached Type: Improvement Status: Assigned Priority: Major Project: Hibernate2 Fix Fors: 2.0.2 Versions: 2.0 final Assignee: Gavin King Reporter: Peter Fassev Created: Wed, 16 Jul 2003 1:29 PM Updated: Wed, 16 Jul 2003 7:43 PM Description: If a collection is fetched together with an owner class using a query with the "left outher join fetch" construct, then the created collection is not added to the cache. A tried a simple improvement and changed the PersistentCollectionType.getCollection() to add the collection to the cache: .... PersistentCollection collection = session.endLoafingCollection(persister, id); if (collection != null) { // this is the patch... persister.cache(id, collection, session); return collection.getCachedValue(); } ... I am not shure if this is the right place for the patch and if this patch is enough, so a am ascing for improvement. --------------------------------------------------------------------- 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-17 00:43:44
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 16 Jul 2003 7:43 PM
Contrary to what you posted in the forum, your actual test case DOES have a repeated column name. Once I fixed that the bug disappeared!
<index column="amenity_key" type="string"/>
<property name="amenity_key" type="string" not-null="true"/>
Please test things properly before sending them to me!!
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-193
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-193
Summary: ArrayIndexOutOfBoundsException with Map of composite-elements
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Versions:
2.0 final
Assignee:
Reporter: Will Glass-Husain
Created: Tue, 15 Jul 2003 1:09 PM
Updated: Wed, 16 Jul 2003 7:43 PM
Environment: Win XP, MySQL 3.23.53, JDK 1.3.1, MySQL Connector J (3.0.8)
Description:
Reference: forum msg http://sourceforge.net/forum/forum.php?thread_id=900653&forum_id=128638
Hibernate creates an invalid PreparedStatement when saving a map of composite elements. The arguments are incorrectly ordered, resulting in an ArrayIndexOutOfBoundsException with the MySql Connector J driver. There are no duplicate column names. See attached test case.
2003-07-15 11:07:59 DEBUG Flushing entities and processing referenced collections
2003-07-15 11:07:59 DEBUG Collection found: [com.wgh.Rent.amenities#1], was: [<unreferenced>]
2003-07-15 11:07:59 DEBUG Processing unreferenced collections
2003-07-15 11:07:59 DEBUG Scheduling collection removes/(re)creates/updates
2003-07-15 11:07:59 DEBUG Flushed: 0 insertions, 0 updates, 0 deletions to 1 objects
2003-07-15 11:07:59 DEBUG Flushed: 1 (re)creations, 0 updates, 0 removals to 1 collections
2003-07-15 11:07:59 DEBUG executing flush
2003-07-15 11:07:59 DEBUG Inserting collection: com.wgh.Rent.amenities#1
2003-07-15 11:07:59 DEBUG about to open: 0 open PreparedStatements, 0 open ResultSets
2003-07-15 11:07:59 DEBUG prepared statement get: insert into amenities (rent_id, category, amenity_key) values (?, ?, ?)
2003-07-15 11:07:59 DEBUG preparing statement
2003-07-15 11:07:59 DEBUG binding '1' to parameter: 1
2003-07-15 11:07:59 DEBUG binding '1' to parameter: 3
2003-07-15 11:07:59 DEBUG binding 'airconditioning' to parameter: 4
---------------------------------------------------------------------
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-17 00:41:43
|
Message:
The following issue has been reopened.
Reopener: Gavin King
Date: Wed, 16 Jul 2003 7:40 PM
Actually, perhaps not .... I will take a closer look at this....
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-202
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-202
Summary: Fetched collections are not cached
Type: Improvement
Status: Reopened
Priority: Major
Project: Hibernate2
Fix Fors:
2.0.2
Versions:
2.0 final
Assignee:
Reporter: Peter Fassev
Created: Wed, 16 Jul 2003 1:29 PM
Updated: Wed, 16 Jul 2003 7:40 PM
Description:
If a collection is fetched together with an owner class using a query with the "left outher join fetch" construct, then the created collection is not added to the cache.
A tried a simple improvement and changed the PersistentCollectionType.getCollection() to add the collection to the cache:
....
PersistentCollection collection = session.endLoafingCollection(persister, id);
if (collection != null) {
// this is the patch...
persister.cache(id, collection, session);
return collection.getCachedValue();
}
...
I am not shure if this is the right place for the patch and if this patch is enough, so a am ascing for improvement.
---------------------------------------------------------------------
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-17 00:39:44
|
Message:
The following issue has been resolved as DUPLICATE.
Resolver: Gavin King
Date: Wed, 16 Jul 2003 7:39 PM
I *think* this is already fixed in CVS.
Please test against the current CVS build of Hibernate.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-202
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-202
Summary: Fetched collections are not cached
Type: Improvement
Status: Resolved
Priority: Major
Resolution: DUPLICATE
Project: Hibernate2
Fix Fors:
2.0.2
Versions:
2.0 final
Assignee:
Reporter: Peter Fassev
Created: Wed, 16 Jul 2003 1:29 PM
Updated: Wed, 16 Jul 2003 7:39 PM
Description:
If a collection is fetched together with an owner class using a query with the "left outher join fetch" construct, then the created collection is not added to the cache.
A tried a simple improvement and changed the PersistentCollectionType.getCollection() to add the collection to the cache:
....
PersistentCollection collection = session.endLoafingCollection(persister, id);
if (collection != null) {
// this is the patch...
persister.cache(id, collection, session);
return collection.getCachedValue();
}
...
I am not shure if this is the right place for the patch and if this patch is enough, so a am ascing for improvement.
---------------------------------------------------------------------
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-16 18:29:43
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-202 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-202 Summary: Fetched collections are not cached Type: Improvement Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.0 final Assignee: Reporter: Peter Fassev Created: Wed, 16 Jul 2003 1:29 PM Updated: Wed, 16 Jul 2003 1:29 PM Description: If a collection is fetched together with an owner class using a query with the "left outher join fetch" construct, then the created collection is not added to the cache. A tried a simple improvement and changed the PersistentCollectionType.getCollection() to add the collection to the cache: .... PersistentCollection collection = session.endLoafingCollection(persister, id); if (collection != null) { // this is the patch... persister.cache(id, collection, session); return collection.getCachedValue(); } ... I am not shure if this is the right place for the patch and if this patch is enough, so a am ascing for improvement. --------------------------------------------------------------------- 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-16 15:42:43
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-201 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-201 Summary: StringBuffer.indexOf is used in QueryJoinFragment - breaks JDK 1.3 Type: Bug Status: Unassigned Priority: Critical Project: Hibernate2 Components: core Versions: 2.0 final Assignee: Reporter: Mathias Bogaert Created: Wed, 16 Jul 2003 10:41 AM Updated: Wed, 16 Jul 2003 10:41 AM Environment: 2.0.2 from CVS Description: StringBuffer.indexOf (a JDK 1.4 only method) is used in QueryJoinFragment - breaks JDK 1.3 required by eg. WLS 7.0. --------------------------------------------------------------------- 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-16 14:55:24
|
The following comment has been added to this issue:
Author: Gavin King
Created: Wed, 16 Jul 2003 9:47 AM
Body:
This was an intentional change made because *everyone* wanted to be able to "resave" deleted objects.
I'm not sure what a good solution to your problem is.
Why not just track deleted objects in your own collection, from onDelete()
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-191
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-191
Summary: Cannot now get postFlush on deletes
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.0.1
Assignee:
Reporter: Keith Manning
Created: Mon, 14 Jul 2003 9:43 AM
Updated: Mon, 14 Jul 2003 9:43 AM
Description:
In v1.2 we listened to onSave, onDelete & then on postFlush when we updated a listening form - this fixed a bug where we were updating the listening form even if commit failed. Now we've upgraded to 2.0 we see that in SessionImpl.postDelete the entitiesByKey is now deleted, so our listener never gets notified that the object has been successfully deleted in the interceptor.postFlush() call - i.e. the object is no longer in the entities iterator.
We believe that we are correctly using the interceptor object & I cannot see a workaround - if we are then this is a bug, but if not how should we be listening to these persistence events?
---------------------------------------------------------------------
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-16 14:53:44
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 16 Jul 2003 9:52 AM
After a quick few seconds thought on this, I am happy that the functionality is correct. It is postFlush() you are listening to, AFTER the session releases the reference.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-191
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-191
Summary: Cannot now get postFlush on deletes
Type: Bug
Status: Closed
Priority: Major
Resolution: WON'T FIX
Project: Hibernate2
Versions:
2.0.1
Assignee:
Reporter: Keith Manning
Created: Mon, 14 Jul 2003 9:43 AM
Updated: Wed, 16 Jul 2003 9:52 AM
Description:
In v1.2 we listened to onSave, onDelete & then on postFlush when we updated a listening form - this fixed a bug where we were updating the listening form even if commit failed. Now we've upgraded to 2.0 we see that in SessionImpl.postDelete the entitiesByKey is now deleted, so our listener never gets notified that the object has been successfully deleted in the interceptor.postFlush() call - i.e. the object is no longer in the entities iterator.
We believe that we are correctly using the interceptor object & I cannot see a workaround - if we are then this is a bug, but if not how should we be listening to these persistence events?
---------------------------------------------------------------------
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-16 14:51:05
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-200 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-200 Summary: subclass is not used when using query by criteria API Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.0.1 Assignee: Reporter: Machiel Groeneveld Created: Wed, 16 Jul 2003 9:49 AM Updated: Wed, 16 Jul 2003 9:49 AM Description: I have a problem with subclasses. For example an abstract Parent as the parent and Child1 and Child2 as subclasses of Parent. When I use this: Criteria criteria = sessie.createCriteria(Child2 .class); criteria.add(anExpression); Then criteria.list() gives me a list containing all subclasses of Parent which match the gives expressions. I snippet from the config file (edited): <class "Parent" table="table"> <id name="id" column="uid" type="long" unsaved-value="0"> <generator class="native"/> </id> <discriminator column="klasse" type="string"/> <property name="message"/> <subclass name="Child1"/> <subclass name="Child2"/> --------------------------------------------------------------------- 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-16 14:45:46
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 16 Jul 2003 9:45 AM
This bug report made no sense. I am closing it. It is not a bug and better discussed in the forum.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-198
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-198
Summary: persister specified in class not used in component
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Assignee:
Reporter: Uwe Weiss
Created: Wed, 16 Jul 2003 8:12 AM
Updated: Wed, 16 Jul 2003 9:45 AM
Description:
The persister specified for the containing CLASS will not be used for COMPONENTS of the CLASS. For Attributes of the component, a EntityPersister is used instead.
I think, it should be allowed to specify a persister for the component, or the class-persister should be used.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-07-16 14:45:45
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 16 Jul 2003 9:44 AM
sql-type affects SchemaExport tool
type adjusts the actual Hibernate type.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-194
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-194
Summary: Property type "date" sqltype "TIMETAMP" saves date only
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Assignee:
Reporter: Will Glass-Husain
Created: Tue, 15 Jul 2003 1:25 PM
Updated: Wed, 16 Jul 2003 9:44 AM
Environment: MySql 3.23.53, MySqlConnector J 3.0.8, JDK 1.3.1, Win XP
Description:
When saving a date, only the date is saved, not the time.
// create the record
Session session1 = sessionfactory.openSession();
AccessLog al = new AccessLog();
Date d = new Date();
Log.info("Date generated by Java: " + d);
al.setAccessDate(d);
session1.save(al);
session1.flush();
session1.connection().commit();
Long AccessLogId = al.getAccessLogId();
session1.close();
// retrieve the record
Session session2 = sessionfactory.openSession();
AccessLog al2 = (AccessLog) session2.load(AccessLog.class,AccessLogId);
session2.close();
Log.info("Date retrieved from database: " + al2.getAccessDate());
<class name="com.wgh.AccessLog" table="access_log" >
<id name="AccessLogId" column="ACCESS_LOG_ID" type="long">
<generator class="identity"/>
</id>
<property name="AccessDate" type="date">
<column name="ACCESS_DATE" sql-type="TIMESTAMP"/>
</property>
</class>
create table access_log (
ACCESS_LOG_ID BIGINT NOT NULL AUTO_INCREMENT,
ACCESS_DATE TIMESTAMP,
primary key (ACCESS_LOG_ID)
);
Produces:
INFO Date generated by Java: Tue Jul 15 11:22:31 PDT 2003
INFO Date retrieved from database: 2003-07-15
See attached test code.
---------------------------------------------------------------------
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-16 14:43:44
|
The following comment has been added to this issue:
Author: Gavin King
Created: Wed, 16 Jul 2003 9:42 AM
Body:
It is already possible to specify dynamically, using the HQL FETCH clause.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-196
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-196
Summary: Ability to specify lazy for many-to-one associations
Type: New Feature
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Assignee:
Reporter: Andrea Aime
Created: Wed, 16 Jul 2003 3:00 AM
Updated: Wed, 16 Jul 2003 3:00 AM
Description:
Using proxy to specify delayed loading of a class is a bit unflexible if more than one class has an association with it. It would be nicer to have the ability to specify lazy loading on the many to one side, since different navigation paths can have different requirements. (The ability to specify what to load in the HQL would be nicer, but probably more difficult to code...)
---------------------------------------------------------------------
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-16 14:43:43
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 16 Jul 2003 9:41 AM
We have discussed this issue over and over again. Hibernate now provides
(1) Session.evict() method
(2) Session.setFlushMode(FlushMode.NEVER)
I personally think that is sufficient.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-197
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-197
Summary: Session-less HQL
Type: New Feature
Status: Closed
Priority: Major
Resolution: DUPLICATE
Project: Hibernate2
Assignee:
Reporter: Andrea Aime
Created: Wed, 16 Jul 2003 3:04 AM
Updated: Wed, 16 Jul 2003 9:41 AM
Description:
There are pieces of code in the application that load or save huge quantities of data but don't really need session management, yet having the ability to use OR mapping is nice for code uniformity and to leverage Hibernate prepared statements caching and batching. The main limiting point is that using HQL attachs the object to the sessions, which may be unecessary work when you don't modify the objects after loading or saving, and fills up the memory (one of my apps easily triggered out of memory exceptions because of it, and I had to convert the code to a more complex direct jdbc...)
---------------------------------------------------------------------
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-16 14:41:46
|
The following comment has been added to this issue:
Author: Gavin King
Created: Wed, 16 Jul 2003 9:40 AM
Body:
Huh???
A component does not have a persister!
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-198
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-198
Summary: persister specified in class not used in component
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Assignee:
Reporter: Uwe Weiss
Created: Wed, 16 Jul 2003 8:12 AM
Updated: Wed, 16 Jul 2003 8:12 AM
Description:
The persister specified for the containing CLASS will not be used for COMPONENTS of the CLASS. For Attributes of the component, a EntityPersister is used instead.
I think, it should be allowed to specify a persister for the component, or the class-persister should be used.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-07-16 14:39:45
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 16 Jul 2003 9:39 AM
This is already fixed in the CVS version, by a change to Table.java, I thin=
k. Please test the current CVS and if there is still a problem, reopen this=
issue.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?=
key=3DHB-199
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-199
Summary: Problem with add column
Type: Bug
Status: Closed
Priority: Major
Resolution: DUPLICATE
Project: Hibernate2
Versions:
2.0.1
Assignee:=20
Reporter: Henrique Marcos Garcia
Created: Wed, 16 Jul 2003 8:44 AM
Updated: Wed, 16 Jul 2003 9:39 AM
Description:
We found a possible error at line 48 in class
net.sf.hibernate.dialect.MySQLDialect. we think it should return
"add column "(with space after column) instead of returning "add
column"(without space);
For exemple:
I'm trying to add a column called name, but hibernate creates a column
named "columnname" because there=C2=B4s no whitespace.
This is applied to almost all classes in package net.sf.hibernate.dialect
Henrique Garcia /Leonardo Marques=20
Bras=C3=ADlia - DF - Brazil
---------------------------------------------------------------------
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-16 13:45:48
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?= key=3DHB-199 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-199 Summary: Problem with add column Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.0.1 Assignee:=20 Reporter: Henrique Marcos Garcia Created: Wed, 16 Jul 2003 8:44 AM Updated: Wed, 16 Jul 2003 8:44 AM Description: We found a possible error at line 48 in class net.sf.hibernate.dialect.MySQLDialect. we think it should return "add column "(with space after column) instead of returning "add column"(without space); For exemple: I'm trying to add a column called name, but hibernate creates a column named "columnname" because there=C2=B4s no whitespace. This is applied to almost all classes in package net.sf.hibernate.dialect Henrique Garcia /Leonardo Marques=20 Bras=C3=ADlia - DF - Brazil --------------------------------------------------------------------- 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-16 13:13:44
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-198 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-198 Summary: persister specified in class not used in component Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Assignee: Reporter: Uwe Weiss Created: Wed, 16 Jul 2003 8:12 AM Updated: Wed, 16 Jul 2003 8:12 AM Description: The persister specified for the containing CLASS will not be used for COMPONENTS of the CLASS. For Attributes of the component, a EntityPersister is used instead. I think, it should be allowed to specify a persister for the component, or the class-persister should be used. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-07-16 08:05:43
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-197 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-197 Summary: Session-less HQL Type: New Feature Status: Unassigned Priority: Major Project: Hibernate2 Assignee: Reporter: Andrea Aime Created: Wed, 16 Jul 2003 3:04 AM Updated: Wed, 16 Jul 2003 3:04 AM Description: There are pieces of code in the application that load or save huge quantities of data but don't really need session management, yet having the ability to use OR mapping is nice for code uniformity and to leverage Hibernate prepared statements caching and batching. The main limiting point is that using HQL attachs the object to the sessions, which may be unecessary work when you don't modify the objects after loading or saving, and fills up the memory (one of my apps easily triggered out of memory exceptions because of it, and I had to convert the code to a more complex direct jdbc...) --------------------------------------------------------------------- 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-16 08:02:43
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-196 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-196 Summary: Ability to specify lazy for many-to-one associations Type: New Feature Status: Unassigned Priority: Major Project: Hibernate2 Components: core Assignee: Reporter: Andrea Aime Created: Wed, 16 Jul 2003 3:00 AM Updated: Wed, 16 Jul 2003 3:00 AM Description: Using proxy to specify delayed loading of a class is a bit unflexible if more than one class has an association with it. It would be nicer to have the ability to specify lazy loading on the many to one side, since different navigation paths can have different requirements. (The ability to specify what to load in the HQL would be nicer, but probably more difficult to code...) --------------------------------------------------------------------- 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-16 07:47:44
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-195 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-195 Summary: "literal" attribute on the property elements Type: New Feature Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.1 Assignee: Reporter: Jacky Created: Wed, 16 Jul 2003 2:46 AM Updated: Wed, 16 Jul 2003 2:46 AM Description: Maybe it would be nice to have the possibility to have a literal attribute to the property elements. This one would replace the ? in the update/insert values with the literal value. It would give the possibility to enter constants so we can set a column to a predefined constant but also set a column to some special calculated value like { fn Now() }, concatenates,.... In some cases this will require a re-select of the row to see the generated value. But in some cases, like a DB generated key, this is also the case. Regards, Dirk --------------------------------------------------------------------- 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.
