Menu
▾
▴
hibernate-issues — Hibernate JIRA Notifications
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(32) |
Jun
(175) |
Jul
(209) |
Aug
(302) |
Sep
(287) |
Oct
(339) |
Nov
(314) |
Dec
(329) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(479) |
Feb
(389) |
Mar
(599) |
Apr
(307) |
May
(390) |
Jun
(300) |
Jul
(410) |
Aug
(458) |
Sep
(299) |
Oct
(315) |
Nov
(363) |
Dec
(529) |
| 2005 |
Jan
(568) |
Feb
(434) |
Mar
(1004) |
Apr
(823) |
May
(767) |
Jun
(763) |
Jul
(854) |
Aug
(862) |
Sep
(560) |
Oct
(853) |
Nov
(763) |
Dec
(731) |
| 2006 |
Jan
(776) |
Feb
(608) |
Mar
(657) |
Apr
(424) |
May
(559) |
Jun
(440) |
Jul
(448) |
Aug
(58) |
Sep
|
Oct
(17) |
Nov
(16) |
Dec
(8) |
| 2007 |
Jan
(1) |
Feb
(8) |
Mar
(2) |
Apr
(5) |
May
(3) |
Jun
(3) |
Jul
(3) |
Aug
(16) |
Sep
(10) |
Oct
(4) |
Nov
(4) |
Dec
(4) |
| 2008 |
Jan
(8) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: <leg...@at...> - 2003-06-17 10:45:05
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Tue, 17 Jun 2003 5:44 AM
I fully reworked xtags.xml last night. All fixed in XDoclet CVS.
Thanks :)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-101
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-101
Summary: xtags.xml missing entry for joined subclass [XDoclet]
Type: Patch
Status: Closed
Priority: Minor
Resolution: FIXED
Project: Hibernate2
Versions:
2.0rc2
Assignee: Gavin King
Reporter: Low Heng Sin
Created: Sun, 25 May 2003 5:32 AM
Updated: Tue, 17 Jun 2003 5:44 AM
Description:
XDoclet hibernate module's xtags.xml doesn't contains entry for the hibernate.joined-subclass and hibernate.joined-subclass-key although the xdt is there.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-06-17 06:47:03
|
Message:
The following issue has been resolved as WON'T FIX.
Resolver: Gavin King
Date: Tue, 17 Jun 2003 1:45 AM
This works fine for me with the latest release and current CVS build of HSQL. Please try a more recent build of HSQL.
I am inclined to NOT fix this, unless other users also report problems.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-137
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-137
Summary: Error with limit clause using HSQL Dialect, setFirstResult and named parameters
Type: Bug
Status: Resolved
Priority: Minor
Resolution: WON'T FIX
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee: Gavin King
Reporter: William Drai
Created: Mon, 16 Jun 2003 6:50 AM
Updated: Tue, 17 Jun 2003 1:45 AM
Description:
When using the setFirstResult and setMaxResults on a HSQLDB Query with named parameters, the results is incorrect because the parameters are populated in the wrong order.
In HSQLDialect the limit syntax is 'select limit ? ? xxx from yyy where zzz'
In all other dialects using the limit syntax it is something like 'select xxx from yyy where zzz limit ?, ?'.
The problem is in the method prepareQueryStatement of the class net.sf.hibernate.loader.Loader. The bindPagingSelectParameters is always called after the bindNamedParameters and that does not work with an HSQL statement.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-06-16 11:51:01
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-137 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-137 Summary: Error with limit clause using HSQL Dialect, setFirstResult and named parameters Type: Bug Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.0 final Assignee: Reporter: William Drai Created: Mon, 16 Jun 2003 6:50 AM Updated: Mon, 16 Jun 2003 6:50 AM Description: When using the setFirstResult and setMaxResults on a HSQLDB Query with named parameters, the results is incorrect because the parameters are populated in the wrong order. In HSQLDialect the limit syntax is 'select limit ? ? xxx from yyy where zzz' In all other dialects using the limit syntax it is something like 'select xxx from yyy where zzz limit ?, ?'. The problem is in the method prepareQueryStatement of the class net.sf.hibernate.loader.Loader. The bindPagingSelectParameters is always called after the bindNamedParameters and that does not work with an HSQL statement. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-06-16 10:01:01
|
The following comment has been added to this issue:
Author: Chris Webb
Created: Mon, 16 Jun 2003 5:00 AM
Body:
I've only tested it with MySQL but I'm sort of hoping that the alias concept is acceptable to other dialects. I am unable to test this fix on any other platform unfortunately. I'm farely confident that it will work with Oracle but I can't speak for any other dialects. To be honest I don't know for sure exactly what sort of SQL can be used to retrieve the identifier and therefore reliably know whether adding an alias is going to cause a problem.
I think conceptually this fix is the right approach. My implementation might be a little unsophisticated though. What would help is a mechanism that could either reliably add a column alias to any arbitary SQL select statement, or retrieve the column alias already associated with the select statement. This would probably require some extra meta data or more sophisticated string parsing.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-92
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-92
Summary: Retrieving native generated identifiers does not support generic Hibernate types
Type: Patch
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee: Gavin King
Reporter: Chris Webb
Created: Wed, 21 May 2003 5:00 AM
Updated: Wed, 11 Jun 2003 8:01 AM
Description:
At present Hibernate does not support identifier types other than Short, Integer or Long for native generated identifiers. This presents a problem when a user defined type is used to encapsulate an identifier that can support natively generated identifiers. An example is where a identifier type is defined that stores the natively generated value internally as a long, thus is similiar to a Long type but not actually a Long type.
The solution is to use the actual identifier type to extract the identifer value from the appropriate retrieve identifier SQL result set rather than the method IdentifierGeneratorFactory.get(ResultSet, Class) which in fact has been flagged as inappropriate in the source code documentation.
A patch has been supplied that does the following:
1. Removes the method get(ResultSet, Class) from IdentifierGeneratorFactory.
2. Changes SequenceGenerator and AbstractEntityPersister to add an 'id' column alias to the SQL used for retrieving the natively generated identifier.
3 Changes SequenceGenerator, EntityPersister and NormalizedEntityPersister to retrieve the identifier value from the SQL result set using the identifer type via the method nullSafeGet(ResultSet rs, String colName, SessionImplementor session, Object owner).
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-06-16 08:46:01
|
Message:
The following issue has been closed.
Resolver: Max Rydahl Andersen
Date: Mon, 16 Jun 2003 3:44 AM
completing this one - future additons should have their own issue.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-103
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-103
Summary: Move tools et.al. to HibernateExt
Type: Improvement
Status: Closed
Priority: Minor
Resolution: FIXED
Project: Hibernate2
Components:
toolset
Fix Fors:
2.1
Versions:
2.1
Assignee: Max Rydahl Andersen
Reporter: Max Rydahl Andersen
Created: Sun, 25 May 2003 11:46 AM
Updated: Mon, 16 Jun 2003 3:44 AM
Description:
1.Move hbm2java, class2hbm and ddl2hbm to HibernateExt/tools and create
a HibernateExt/tools/build.xml to generate hibernate-tools.jar
2. Move jca, jmx to HibernateExt/j2eeopt and create a
Hibernate/j2eeopt/build.xml to generate hibnerate-j2eeopt.jar
3. Move Hibern8IDE to HibernateExt/tools or is it to "heavy" for that
part ?
I guess the hibernateExt/xyz will have its own releases and be an
ADDITION to the hibernate.jar ?
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-06-16 08:46:01
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Mon, 16 Jun 2003 3:45 AM
Body:
damn! I'm sleepy! It should ofcourse be hibernateext/hibern8ide to avoid having to many extensions bulked under the tools directory!
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-103
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-103
Summary: Move tools et.al. to HibernateExt
Type: Improvement
Status: Closed
Priority: Minor
Resolution: FIXED
Project: Hibernate2
Components:
toolset
Fix Fors:
2.1
Versions:
2.1
Assignee: Max Rydahl Andersen
Reporter: Max Rydahl Andersen
Created: Sun, 25 May 2003 11:46 AM
Updated: Mon, 16 Jun 2003 3:44 AM
Description:
1.Move hbm2java, class2hbm and ddl2hbm to HibernateExt/tools and create
a HibernateExt/tools/build.xml to generate hibernate-tools.jar
2. Move jca, jmx to HibernateExt/j2eeopt and create a
Hibernate/j2eeopt/build.xml to generate hibnerate-j2eeopt.jar
3. Move Hibern8IDE to HibernateExt/tools or is it to "heavy" for that
part ?
I guess the hibernateExt/xyz will have its own releases and be an
ADDITION to the hibernate.jar ?
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-06-16 08:27:01
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Mon, 16 Jun 2003 3:25 AM
Body:
That should ofcousr be HibernateExt/tools/hibern8IDE
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-103
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-103
Summary: Move tools et.al. to HibernateExt
Type: Improvement
Status: In Progress
Priority: Minor
Project: Hibernate2
Components:
toolset
Versions:
2.1
Assignee: Max Rydahl Andersen
Reporter: Max Rydahl Andersen
Created: Sun, 25 May 2003 11:46 AM
Updated: Sun, 25 May 2003 11:46 AM
Description:
1.Move hbm2java, class2hbm and ddl2hbm to HibernateExt/tools and create
a HibernateExt/tools/build.xml to generate hibernate-tools.jar
2. Move jca, jmx to HibernateExt/j2eeopt and create a
Hibernate/j2eeopt/build.xml to generate hibnerate-j2eeopt.jar
3. Move Hibern8IDE to HibernateExt/tools or is it to "heavy" for that
part ?
I guess the hibernateExt/xyz will have its own releases and be an
ADDITION to the hibernate.jar ?
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-06-16 08:25:00
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Mon, 16 Jun 2003 3:24 AM
Body:
I agree. I'll probably (at some point ;) add HibernateExt/hibern8IDE when I get the time to clean it up...
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-103
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-103
Summary: Move tools et.al. to HibernateExt
Type: Improvement
Status: In Progress
Priority: Minor
Project: Hibernate2
Components:
toolset
Versions:
2.1
Assignee: Max Rydahl Andersen
Reporter: Max Rydahl Andersen
Created: Sun, 25 May 2003 11:46 AM
Updated: Sun, 25 May 2003 11:46 AM
Description:
1.Move hbm2java, class2hbm and ddl2hbm to HibernateExt/tools and create
a HibernateExt/tools/build.xml to generate hibernate-tools.jar
2. Move jca, jmx to HibernateExt/j2eeopt and create a
Hibernate/j2eeopt/build.xml to generate hibnerate-j2eeopt.jar
3. Move Hibern8IDE to HibernateExt/tools or is it to "heavy" for that
part ?
I guess the hibernateExt/xyz will have its own releases and be an
ADDITION to the hibernate.jar ?
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-06-16 07:21:01
|
The following comment has been added to this issue:
Author: Christian Bauer
Created: Mon, 16 Jun 2003 2:20 AM
Body:
I think we can integrate things like GUI frontends in the HibernateExt package. Should be a new directory, though, not in the /tools/.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-103
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-103
Summary: Move tools et.al. to HibernateExt
Type: Improvement
Status: In Progress
Priority: Minor
Project: Hibernate2
Components:
toolset
Versions:
2.1
Assignee: Max Rydahl Andersen
Reporter: Max Rydahl Andersen
Created: Sun, 25 May 2003 11:46 AM
Updated: Sun, 25 May 2003 11:46 AM
Description:
1.Move hbm2java, class2hbm and ddl2hbm to HibernateExt/tools and create
a HibernateExt/tools/build.xml to generate hibernate-tools.jar
2. Move jca, jmx to HibernateExt/j2eeopt and create a
Hibernate/j2eeopt/build.xml to generate hibnerate-j2eeopt.jar
3. Move Hibern8IDE to HibernateExt/tools or is it to "heavy" for that
part ?
I guess the hibernateExt/xyz will have its own releases and be an
ADDITION to the hibernate.jar ?
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-06-16 06:56:01
|
Message:
The following issue has been re-assigned.
Assignee: Christian Bauer (mailto:chr...@bl...)
Assigner: Gavin King (mailto:ga...@in...)
Date: Mon, 16 Jun 2003 1:55 AM
Comment:
Reassigning this to you, Christian, since you are working on the examples at present.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-42
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-42
Summary: hibernate-examples-2.0
Type: Patch
Status: Assigned
Priority: Minor
Project: Hibernate2
Assignee: Christian Bauer
Reporter: Max Rydahl Andersen
Created: Sat, 3 May 2003 10:26 AM
Updated: Mon, 16 Jun 2003 1:55 AM
Description:
hibernate-examples-2.0
Annexed is a ZIP of the hibernate-example refitted for
version 2.0 beta 3.
I'm also finishing up a Struts application based on the
eg examples. I'll release it at the Struts SourceForge
site (where Matt's Resume application now lives), and
let you know.
-Ted.
http://sourceforge.net/tracker/index.php?func=detail&aid=699668&group_id=40712&atid=428710
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-06-16 06:56:01
|
Message:
The following issue has been re-assigned.
Assignee: Max Rydahl Andersen (mailto:xa...@xa...)
Assigner: Gavin King (mailto:ga...@in...)
Date: Mon, 16 Jun 2003 1:54 AM
Comment:
Why was this assigned to *me*? This is for you, Max....
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-48
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-48
Summary: More finder generation
Type: Patch
Status: Assigned
Priority: Major
Project: Hibernate2
Assignee: Max Rydahl Andersen
Reporter: Max Rydahl Andersen
Created: Sat, 3 May 2003 10:31 AM
Updated: Mon, 16 Jun 2003 1:54 AM
Description:
More finder generation
Finder generator now supports generation based on class
relationships, a la:
<set name="games" inverse="true" lazy="true"
table="GamePlayers">
<meta
attribute="foreign-finder-name">findSavedGames</meta>
<meta attribute="foreign-finder-field">save</meta>
<meta attribute="foreign-join-field">players</meta>
<key column="playerID"/>
<many-to-many class="com.whatever.Game"
column="gameID"/>
</set>
There's more information in the updated javadocs in
FinderRenderer.java.
The new classes MethodSignatureBuilder and QueryBuilder
are a start at extracting this kind of functionality
into seperate classes. I'll improve the javadocs as
they mature a bit.
http://sourceforge.net/tracker/index.php?func=detail&aid=722221&group_id=40712&atid=428710
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-06-16 06:54:04
|
The following comment has been added to this issue:
Author: Gavin King
Created: Mon, 16 Jun 2003 1:53 AM
Body:
How many platforms have you tested the ID_COLUMN_NAME thing for?
Could it possibly break for some dialects?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-92
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-92
Summary: Retrieving native generated identifiers does not support generic Hibernate types
Type: Patch
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee: Gavin King
Reporter: Chris Webb
Created: Wed, 21 May 2003 5:00 AM
Updated: Wed, 11 Jun 2003 8:01 AM
Description:
At present Hibernate does not support identifier types other than Short, Integer or Long for native generated identifiers. This presents a problem when a user defined type is used to encapsulate an identifier that can support natively generated identifiers. An example is where a identifier type is defined that stores the natively generated value internally as a long, thus is similiar to a Long type but not actually a Long type.
The solution is to use the actual identifier type to extract the identifer value from the appropriate retrieve identifier SQL result set rather than the method IdentifierGeneratorFactory.get(ResultSet, Class) which in fact has been flagged as inappropriate in the source code documentation.
A patch has been supplied that does the following:
1. Removes the method get(ResultSet, Class) from IdentifierGeneratorFactory.
2. Changes SequenceGenerator and AbstractEntityPersister to add an 'id' column alias to the SQL used for retrieving the natively generated identifier.
3 Changes SequenceGenerator, EntityPersister and NormalizedEntityPersister to retrieve the identifier value from the SQL result set using the identifer type via the method nullSafeGet(ResultSet rs, String colName, SessionImplementor session, Object owner).
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-06-16 06:50:01
|
Message:
The following issue has been resolved as REJECTED.
Resolver: Gavin King
Date: Mon, 16 Jun 2003 1:49 AM
I am inclined *not* to provide a Maven build. Our current Ant build is very nice. I have found Maven a pain in other projects, and I think I'm not the only one. Opinion was certainly divided when we discussed this in the mainling list.
Thanks for the hard work, though :(
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-45
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-45
Summary: Working maven build descriptors
Type: Patch
Status: Resolved
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Assignee: Gavin King
Reporter: Max Rydahl Andersen
Created: Sat, 3 May 2003 10:29 AM
Updated: Mon, 16 Jun 2003 1:49 AM
Description:
Working maven build descriptors
I finally produced working maven build descriptors.
Unit test are disabled ( they need some more
configuration - I will
provide it over weekend )
It does not require tweaking of existing source
structure, just 3 files in root directory
Project.xml needs to be updated with correct
developer names/roles
http://sourceforge.net/tracker/index.php?func=detail&aid=715148&group_id=40712&atid=428710
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-06-16 06:48:02
|
The following comment has been added to this issue:
Author: Markus Menner
Created: Mon, 16 Jun 2003 1:47 AM
Body:
Yeah, thanx, sometimes I'm too lazy ;-)
Okay, if I'd use the .cfg.xml, it would be easier to define the jcs-cache settings there ...
But since I have my own cfg section (which is part of another configuration structure im my framework) I use a Properties instance to configure the SessionFactory and thus can't make use of it.
It would be perfect, if we just had a property to globally switch any (factory level) caching on/off.
Is this difficult ?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-122
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-122
Summary: Global "on/off" property for SessionFactory-level cache
Type: New Feature
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.0rc2
Assignee:
Reporter: Markus Menner
Created: Fri, 6 Jun 2003 1:41 AM
Updated: Fri, 6 Jun 2003 1:41 AM
Description:
It would be nice to have a property to switch on/off SessionFactory-level cache (for example to check performance improvements caching vs. no-caching).
At the moment you have to remove/add the jcs-cache tags in the mapping files.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-06-16 06:46:01
|
Message: The following issue has been resolved as REJECTED. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-40 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-40 Summary: Fetch profiles Type: Patch Status: Resolved Priority: Minor Resolution: REJECTED Project: Hibernate2 Assignee: Gavin King Reporter: Max Rydahl Andersen Created: Sat, 3 May 2003 10:24 AM Updated: Mon, 16 Jun 2003 1:44 AM Description: Fetch profiles Here's my code for fetch profiles. No test case is currently developed (though I have my own). I hope you can test on your own model http://sourceforge.net/tracker/index.php?func=detail&aid=688610&group_id=40712&atid=428710 --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-06-16 06:46:01
|
The following comment has been added to this issue:
Author: Gavin King
Created: Mon, 16 Jun 2003 1:44 AM
Body:
Hibernate is beginning to provide support for fetch profiles integrated into HQL and the QBC API. The advantage of this is that the fetching is done ina single select.
I won't integrating this code into Hibernate, though I will leave it here, if anyone wants to use it (as an addon to Hibernate).
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-40
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-40
Summary: Fetch profiles
Type: Patch
Status: Assigned
Priority: Major
Project: Hibernate2
Assignee: Gavin King
Reporter: Max Rydahl Andersen
Created: Sat, 3 May 2003 10:24 AM
Updated: Tue, 6 May 2003 5:34 AM
Description:
Fetch profiles
Here's my code for fetch profiles. No test case is
currently developed (though I have my own). I hope you
can test on your own model
http://sourceforge.net/tracker/index.php?func=detail&aid=688610&group_id=40712&atid=428710
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-06-16 06:46:01
|
The following issue has been updated:
Updater: Gavin King (mailto:ga...@in...)
Date: Mon, 16 Jun 2003 1:44 AM
Changes:
priority changed from Major to Minor
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-40&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-40
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-40
Summary: Fetch profiles
Type: Patch
Status: Assigned
Priority: Minor
Project: Hibernate2
Assignee: Gavin King
Reporter: Max Rydahl Andersen
Created: Sat, 3 May 2003 10:24 AM
Updated: Mon, 16 Jun 2003 1:44 AM
Description:
Fetch profiles
Here's my code for fetch profiles. No test case is
currently developed (though I have my own). I hope you
can test on your own model
http://sourceforge.net/tracker/index.php?func=detail&aid=688610&group_id=40712&atid=428710
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-06-16 06:35:04
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Mon, 16 Jun 2003 1:34 AM
We have real Ant tasks now, so don't need this.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-41
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-41
Summary: build-schema.xml
Type: Patch
Status: Closed
Priority: Major
Resolution: WON'T FIX
Project: Hibernate2
Assignee: Gavin King
Reporter: Max Rydahl Andersen
Created: Sat, 3 May 2003 10:25 AM
Updated: Mon, 16 Jun 2003 1:34 AM
Description:
build-schema.xml
Attached is complete Ant build file for running the
schemaExport and schemaUpdater utilities. This instance
is setup for use with the eg Examples. (I'm in the
process of updating the eg Examples for 2.0, if anyone
is interested in that.)
http://sourceforge.net/tracker/index.php?func=detail&aid=698344&group_id=40712&atid=428710
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-06-16 05:14:01
|
Message: The following issue has been closed. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-124 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-124 Summary: Hibernate thinks unmodified <set> of value objects is dirty Type: Bug Status: Closed Priority: Major Resolution: REJECTED Project: Hibernate2 Components: core Versions: 2.0 final Assignee: Gavin King Reporter: Chris Richardson Created: Sun, 8 Jun 2003 7:36 PM Updated: Mon, 16 Jun 2003 12:13 AM Environment: Win2k Description: Hibernate thinks that a collection of value objects is modified when it really isn't. It tries to save it to the DB everytime it is loaded. This line from Set.snapshot looks suspect: clonedSet.put(copied, copied); Shouldn't the key be the original value - not the copy? Here is an excerpt of my mapping file: <set name="timeRanges" table="FTGO_RESTAURANT_TIME_RANGE" cascade="all"> <key column="RESTAURANT_ID"/> <composite-element class="net.chrisrichardson.foodToGo.order.hibernateImpl.HibernateTimeRange"> <property name="dayOfWeek" column="day_Of_Week"/> <property name="openHour" column="open_Hour"/> <property name="openMinute" column="open_Minute"/> <property name="closeHour" column="close_Hour"/> <property name="closeMinute" column="close_Minute"/> </composite-element> </set> --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-06-16 04:57:02
|
The following comment has been added to this issue:
Author: Chris Richardson
Created: Sun, 15 Jun 2003 11:56 PM
Body:
Looks like this is my mistake. Oops!
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-124
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-124
Summary: Hibernate thinks unmodified <set> of value objects is dirty
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee:
Reporter: Chris Richardson
Created: Sun, 8 Jun 2003 7:36 PM
Updated: Sun, 8 Jun 2003 7:36 PM
Environment: Win2k
Description:
Hibernate thinks that a collection of value objects is modified when it really isn't. It tries to save it to the DB everytime it is loaded.
This line from Set.snapshot looks suspect:
clonedSet.put(copied, copied);
Shouldn't the key be the original value - not the copy?
Here is an excerpt of my mapping file:
<set name="timeRanges" table="FTGO_RESTAURANT_TIME_RANGE" cascade="all">
<key column="RESTAURANT_ID"/>
<composite-element class="net.chrisrichardson.foodToGo.order.hibernateImpl.HibernateTimeRange">
<property name="dayOfWeek" column="day_Of_Week"/>
<property name="openHour" column="open_Hour"/>
<property name="openMinute" column="open_Minute"/>
<property name="closeHour" column="close_Hour"/>
<property name="closeMinute" column="close_Minute"/>
</composite-element>
</set>
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-06-16 03:27:03
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Sun, 15 Jun 2003 10:26 PM
I applied this patch. Nice :)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-107
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-107
Summary: JdbcDatabaseInfo improvement
Type: Patch
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
toolset
Fix Fors:
2.0.1
Versions:
2.0rc2
Assignee: Gavin King
Reporter: Teodor Danciu
Created: Mon, 26 May 2003 3:51 AM
Updated: Sun, 15 Jun 2003 10:26 PM
Description:
The JdbcDatabaseInfo class tries to load all the
database metadata information when it is instantiated.
We found this inconvenient since in our Oracle database
we already have thousands of tables and retrieving the
whole metadata is time-consuming and inefficient in
case of simple updates (one or two tables).
We made some modifications in the JdbcDatabaseInfo
class so that the metadata information for each table be
loaded only when needed. Once the metadata for a table
loaded, it is kept in memory for later use.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-06-16 03:24:02
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Sun, 15 Jun 2003 10:22 PM
Thanks. I applied this fix.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-114
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-114
Summary: SchemaExportTask tries to open files as URLs
Type: Patch
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
toolset
Fix Fors:
2.0.1
Versions:
2.0rc2
Assignee: Gavin King
Reporter: Ken Geis
Created: Thu, 29 May 2003 7:20 PM
Updated: Sun, 15 Jun 2003 10:22 PM
Environment: Windows XP, ant
Description:
I was using the SchemaExportTask for Ant in Windows. The input file name started with C:, so the SAXReader interpreted this as a URL with protocol "c." It should not be treated as a URL at all.
In net.sf.hibernate.cfg.Configuration, change the method addFile from
----------------------------------------------------------
log.info("Mapping file: " + xmlFile);
try {
add( XMLHelper.createSAXReader(xmlFile).read(xmlFile) );
}
catch (Exception e) {
-----------------------------------------------------------
to
-----------------------------------------------------------
log.info("Mapping file: " + xmlFile);
try {
add( XMLHelper.createSAXReader(xmlFile).read(new File(xmlFile)) );
}
catch (Exception e) {
-----------------------------------------------------------
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-06-15 13:28:56
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Sun, 15 Jun 2003 8:25 AM
All done.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-3
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-3
Summary: Javadoc for Hibernate 2
Type: Task
Status: Closed
Priority: Trivial
Resolution: FIXED
Project: Hibernate2
Fix Fors:
2.0.1
Assignee: Gavin King
Reporter: Jesper Matthiesen
Created: Wed, 30 Apr 2003 6:55 AM
Updated: Sun, 15 Jun 2003 8:25 AM
Description:
How about online API Javadoc for Hibernate 2 on the Hibernate web site (like there is for 1.x)..
I often link to online documentation from my own generated javadoc, so it's nice to just being able to paste in a URL in the genration process..
regards...
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-06-15 13:13:08
|
The following comment has been added to this issue:
Author: Gavin King
Created: Sun, 15 Jun 2003 8:12 AM
Body:
Check the DTD.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-122
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-122
Summary: Global "on/off" property for SessionFactory-level cache
Type: New Feature
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.0rc2
Assignee:
Reporter: Markus Menner
Created: Fri, 6 Jun 2003 1:41 AM
Updated: Fri, 6 Jun 2003 1:41 AM
Description:
It would be nice to have a property to switch on/off SessionFactory-level cache (for example to check performance improvements caching vs. no-caching).
At the moment you have to remove/add the jcs-cache tags in the mapping files.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-06-15 05:45:04
|
The following comment has been added to this issue:
Author: Gavin King
Created: Sun, 15 Jun 2003 12:44 AM
Body:
I am unable to reproduce this problem, and I am inclined to disbelieve it exists. Please see FooBarTest.testSortables in CVS.
If you want to progress this further, please submit a VERY simple test case.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-136
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-136
Summary: Criteria api appears to add elements to a SortedSet before setting their properties
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee:
Reporter: Paul Rivers
Created: Sat, 14 Jun 2003 4:16 PM
Updated: Sat, 14 Jun 2003 4:16 PM
Environment: Eclipse 2.1, Tomcat4.1.24, jdk1.4.1_03
Description:
As I understand it, this query by criteria query:
Criteria criteria = session.createCriteria(EntryDAO.class);
criteria.setFirstResult(rangeStart);
criteria.setMaxResults(rangeSize);
criteria.addOrder(Order.desc("dateCreated"));
entries = criteria.list();
Should return the same results as this one:
Query query = session.createQuery("from EntryDAO order by dateCreated desc");
query.setFirstResult(rangeStart);
query.setMaxResults(rangeSize);
entries = query.list();
The problem is that the normal (second) query executes fine, but the Criteria (first) query throws a NullPointerException. Each entry has a SortedSet of Categories (It's specified in the mapping file). The stack trace for the null pointer exception leads to this line:
result = this.getName().compareTo(otherCategory.getName());
In this function:
public int compareTo(Object o) {
int result;
CategoryDAO otherCategory = (CategoryDAO) o;
result = this.getDisplayIndex() - otherCategory.getDisplayIndex();
if(result == 0) {
result = this.getName().compareTo(otherCategory.getName());
}
return result;
}
The problem appears to be, to me, that for some reason the Criteria API 1. does the database query, 2. adds the new object to the SortedSet, 3. THEN sets it's properties, where it should be 1. doing the query 2. setting the properties, 3. then adding the category to the sortedset.
PLEASE let me know if there's anything I can do to help with the issue, or if there's any other information you would like. Thanks.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
93 messages has been excluded from this view by a project administrator.
