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-15 19:34:44
|
Message:
The following issue has been closed.
Resolver: Max Rydahl Andersen
Date: Tue, 15 Jul 2003 2:34 PM
Not an error or bug (at least not if the sql is executed via preparedstatements which is the case with hibernate's hql/criteria stuff)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-192
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-192
Summary: net.sf.hibernate.type.StringType contains risky SQL generation
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: Paul Brown
Created: Mon, 14 Jul 2003 10:55 AM
Updated: Tue, 15 Jul 2003 2:34 PM
Description:
The method:
public String objectToSQLString(Object value) throws Exception {
return '\'' + (String) value + '\'';
}
risks creating dangerous SQL in the hands of a well-informed, malicious user.
---------------------------------------------------------------------
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-15 18:34:43
|
The following comment has been added to this issue:
Author: Will Glass-Husain
Created: Tue, 15 Jul 2003 1:34 PM
Body:
never mind, I'm a goofball.
The solution is to use
type="timestamp"
Did I miss this in the documentation?
Anyway, I tried
sql-type="timestamp"
but obviously, that's not the same thing.
Can someone please kill this bug report?
---------------------------------------------------------------------
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: Unassigned
Priority: Major
Project: Hibernate2
Assignee:
Reporter: Will Glass-Husain
Created: Tue, 15 Jul 2003 1:25 PM
Updated: Tue, 15 Jul 2003 1:27 PM
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-15 18:28:43
|
The following issue has been updated:
Updater: Will Glass-Husain (mailto:wg...@fo...)
Date: Tue, 15 Jul 2003 1:27 PM
Comment:
code, data, properties to duplicate this bug
Changes:
Attachment changed to testdate.zip
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-194&page=history
---------------------------------------------------------------------
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: Unassigned
Priority: Major
Project: Hibernate2
Assignee:
Reporter: Will Glass-Husain
Created: Tue, 15 Jul 2003 1:25 PM
Updated: Tue, 15 Jul 2003 1:27 PM
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-15 18:26:43
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- 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: Unassigned Priority: Major Project: Hibernate2 Assignee: Reporter: Will Glass-Husain Created: Tue, 15 Jul 2003 1:25 PM Updated: Tue, 15 Jul 2003 1:25 PM 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-15 18:11:44
|
The following issue has been updated:
Updater: Will Glass-Husain (mailto:wg...@fo...)
Date: Tue, 15 Jul 2003 1:11 PM
Comment:
test case for this bug. call com.wgh.Test hibernate.properties data.hbm.xml log4j.properties
Changes:
Attachment changed to test.zip
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-193&page=history
---------------------------------------------------------------------
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: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.0 final
Assignee:
Reporter: Will Glass-Husain
Created: Tue, 15 Jul 2003 1:09 PM
Updated: Tue, 15 Jul 2003 1:11 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-15 18:09:43
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- 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: Unassigned Priority: Major Project: Hibernate2 Versions: 2.0 final Assignee: Reporter: Will Glass-Husain Created: Tue, 15 Jul 2003 1:09 PM Updated: Tue, 15 Jul 2003 1:09 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: Arjun R. <arj...@my...> - 2003-07-15 18:04:21
|
Hi,
Im trying to get middlegen-hibernate to work. I was able to generate the hbm files for the table that I working on, but when I try to generate the java source using the hbm2java Codegenerator, I seem to get SAX parse exceptions all over the place. Here's an example of the expection im getting.
Am I doing simple mistake? Any help would be greatly appreciated.
Thanks
-Arjun
p.S: Attaching a sample hbm that was genrated by middlegen.
[java] 15 [main] ERROR hbm2java.CodeGenerator - Error parsing XML: file:/C:/Projects/Hibernate/build/gen-src/mysample/hibernate/Sasset
.hbm.xml(19)
[java] org.xml.sax.SAXParseException: Element "class" does not allow "property" here.
[java] at org.apache.crimson.parser.Parser2.error(Parser2.java:3160)
[java] at org.apache.crimson.parser.ValidatingParser$ChildrenValidator.consume(ValidatingParser.java:349)
[java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1317)
[java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)
[java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)
[java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)
[java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)
[java] at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:500)
[java] at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
[java] at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)
[java] at org.jdom.input.SAXBuilder.build(SAXBuilder.java:354)
[java] at org.jdom.input.SAXBuilder.build(SAXBuilder.java:707)
[java] at org.jdom.input.SAXBuilder.build(SAXBuilder.java:689)
[java] at net.sf.hibernate.tool.hbm2java.CodeGenerator.main(CodeGenerator.java:93)
_______________________________________________
No banners. No pop-ups. No kidding.
Introducing My Way - http://www.myway.com
|
|
From: <leg...@at...> - 2003-07-15 17:06:43
|
The following comment has been added to this issue:
Author: Paul Brown
Created: Tue, 15 Jul 2003 12:06 PM
Body:
Go ahead and close it out. Just thought that it was worth mentioning. (Of course, if Hibernate wasn't open source (thanks!), no one would have ever made a comment!)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-192
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-192
Summary: net.sf.hibernate.type.StringType contains risky SQL generation
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: Paul Brown
Created: Mon, 14 Jul 2003 10:55 AM
Updated: Mon, 14 Jul 2003 10:55 AM
Description:
The method:
public String objectToSQLString(Object value) throws Exception {
return '\'' + (String) value + '\'';
}
risks creating dangerous SQL in the hands of a well-informed, malicious user.
---------------------------------------------------------------------
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-15 06:34:43
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Tue, 15 Jul 2003 1:34 AM
Body:
I get your point, but is there much we can do about it ? The sql string you gave was a completely legal string ;) How would you escape away from it ?
But anyhow - the jdbc driver should handle this as the result of this method is passed to a preparedstatement, which per the standard should handle such escaping (IMHO, or at least that is my understanding ;)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-192
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-192
Summary: net.sf.hibernate.type.StringType contains risky SQL generation
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: Paul Brown
Created: Mon, 14 Jul 2003 10:55 AM
Updated: Mon, 14 Jul 2003 10:55 AM
Description:
The method:
public String objectToSQLString(Object value) throws Exception {
return '\'' + (String) value + '\'';
}
risks creating dangerous SQL in the hands of a well-informed, malicious user.
---------------------------------------------------------------------
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-14 22:43:45
|
The following comment has been added to this issue:
Author: Paul Brown
Created: Mon, 14 Jul 2003 5:43 PM
Body:
Sorry -- executing arbitrary SQL on the part of the application isn't the least bit dangerous and is sometimes desirable.
The problem comes when someone attempts to persist a String, perhaps entered as a name on a web form but it has the form:
' DROP ALL FROM SYSOBJECTS; COMMIT
Or something else silly. If it is incumbent on the implementer to perform any necessary escaping, then that should be documented somewhere.
If this is used in such a way that the JDBC layer performs the escaping, then I humbly withdraw my comment.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-192
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-192
Summary: net.sf.hibernate.type.StringType contains risky SQL generation
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: Paul Brown
Created: Mon, 14 Jul 2003 10:55 AM
Updated: Mon, 14 Jul 2003 10:55 AM
Description:
The method:
public String objectToSQLString(Object value) throws Exception {
return '\'' + (String) value + '\'';
}
risks creating dangerous SQL in the hands of a well-informed, malicious user.
---------------------------------------------------------------------
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-14 18:13:44
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Mon, 14 Jul 2003 1:13 PM
Body:
Yes ?
And session.getConnection().excute(abitrarySQL); is similar - what's ya' point ? ;)
What's the error/bug ?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-192
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-192
Summary: net.sf.hibernate.type.StringType contains risky SQL generation
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: Paul Brown
Created: Mon, 14 Jul 2003 10:55 AM
Updated: Mon, 14 Jul 2003 10:55 AM
Description:
The method:
public String objectToSQLString(Object value) throws Exception {
return '\'' + (String) value + '\'';
}
risks creating dangerous SQL in the hands of a well-informed, malicious user.
---------------------------------------------------------------------
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-14 15:56:48
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-192 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-192 Summary: net.sf.hibernate.type.StringType contains risky SQL generation Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.0.1 Assignee: Reporter: Paul Brown Created: Mon, 14 Jul 2003 10:55 AM Updated: Mon, 14 Jul 2003 10:55 AM Description: The method: public String objectToSQLString(Object value) throws Exception { return '\'' + (String) value + '\''; } risks creating dangerous SQL in the hands of a well-informed, malicious user. --------------------------------------------------------------------- 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-14 14: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-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-14 06:00:43
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Mon, 14 Jul 2003 12:59 AM
fixed, thanks :)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-187
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-187
Summary: Problem with limit clause and named parameters
Type: Bug
Status: Closed
Priority: Minor
Resolution: FIXED
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee: Gavin King
Reporter: William Drai
Created: Sun, 13 Jul 2003 12:36 PM
Updated: Mon, 14 Jul 2003 12:59 AM
Description:
When using a limit clause and named parameters in a query,
the limit parameters are not populated correctly when a parameter
is used multiple times.
for example the query
"from c where c.field1 = :arg and c.field2 = :arg"
won't work with a limit clause.
I think the problem is that the bindNamedParameters method in QueryTranslator always returns the namedParams map size, instead of counting all parameters instances.
---------------------------------------------------------------------
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-14 02:37:43
|
The following comment has been added to this issue:
Author: Will Glass-Husain
Created: Sun, 13 Jul 2003 9:37 PM
Body:
wow! that's quick.
version 2.0.1 17 June 2003
This was downloaded just a few days ago. sorry if I missed a duplicate issue, I'm new to Jira.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-190
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-190
Summary: codegenerator creates SortedMap when it should create Map
Type: Bug
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
toolset
Versions:
2.0 final
Assignee: Max Rydahl Andersen
Reporter: Will Glass-Husain
Created: Sun, 13 Jul 2003 9:30 PM
Updated: Sun, 13 Jul 2003 9:34 PM
Environment: Win XP/JDK 1.3.1
Description:
The code generator used a SortedMap to represent the following composite element.
<class name="com.wgh.om.Rent" table="rent">
<meta attribute="generated-class">com.wgh.om.base.Rent</meta>
<id name="rent_id" type="long" unsaved-value="null">
<generator class="identity"/>
</id>
<map name="amenities">
<key column="rent_id" />
<index column="name" type="string" />
<composite-element class="com.wgh.om.RentAmenity">
<meta attribute="generated-class">com.wgh.om.base.RentAmenity</meta>
<property name="name" type="string" not-null="true"/>
<property name="category" type="int" />
</composite-element>
</map>
</class>
When I saved the class with this code, I received a PropertyAccessException from cglib. (with the optimizer turned off).
hs = HibernateWrapper.getNewSession(ctx);
o = new Rent();
o.setAmenities(new TreeMap());
hs.close();
hs = HibernateWrapper.getNewSession(ctx);
hs.saveOrUpdate(o);
hs.flush();
hs.connection().commit();
hs.close();
2003-07-13 19:29:04 DEBUG java.lang.ClassCastException: net.sf.hibernate.collection.Map
at com.novogradac.valuation.om.RentMetaClass3.setPropertyValues(<generated>)
at net.sf.hibernate.persister.AbstractEntityPersister.setPropertyValues(AbstractEntityPersister.java:158)
at net.sf.hibernate.impl.SessionImpl.doSave(SessionImpl.java:724)
at net.sf.hibernate.impl.SessionImpl.save(SessionImpl.java:620)
at net.sf.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:1214)
The solution was to either (A) add sort="natural" to the map hbm.xml, or to change the generated code to use Map instead of SortedMap.
Recommendation-- have the codegenerator only use SortedMaps when the sorted attribute is present in the hbm.xml.
---------------------------------------------------------------------
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-14 02:37:43
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Sun, 13 Jul 2003 9:37 PM
Support requests should be directed to the Hibernate user forum, and should be accompanied by sufficient information. JIRA is for bugs in Hibernate.
eg. the actual SQL generated!
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-189
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-189
Summary: About "left join" at HQL
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: zhongjin
Created: Sun, 13 Jul 2003 7:52 PM
Updated: Sun, 13 Jul 2003 9:37 PM
Description:
I use "left join" at a HQL,when I use Oracle,this is not issue,but I use Sybase,the error is issue that "com.sybase.jdbc2.jdbc.SybSQLException: Incorrect syntax near 'left'. ",How can I solve this issue?
---------------------------------------------------------------------
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-14 02:37:43
|
Message:
The following issue has been re-assigned.
Assignee: Gavin King (mailto:ga...@in...)
Assigner: Gavin King (mailto:ga...@in...)
Date: Sun, 13 Jul 2003 9:35 PM
Comment:
I'll take a look. I though I fixed something like this before....
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-187
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-187
Summary: Problem with limit clause and named parameters
Type: Bug
Status: Assigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee: Gavin King
Reporter: William Drai
Created: Sun, 13 Jul 2003 12:36 PM
Updated: Sun, 13 Jul 2003 9:35 PM
Description:
When using a limit clause and named parameters in a query,
the limit parameters are not populated correctly when a parameter
is used multiple times.
for example the query
"from c where c.field1 = :arg and c.field2 = :arg"
won't work with a limit clause.
I think the problem is that the bindNamedParameters method in QueryTranslator always returns the namedParams map size, instead of counting all parameters instances.
---------------------------------------------------------------------
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-14 02:35:43
|
Message:
The following issue has been re-assigned.
Assignee: Max Rydahl Andersen (mailto:xa...@xa...)
Assigner: Gavin King (mailto:ga...@in...)
Date: Sun, 13 Jul 2003 9:34 PM
Comment:
Isn't this fixed already? I thought it was ....
What version are you using?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-190
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-190
Summary: codegenerator creates SortedMap when it should create Map
Type: Bug
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
toolset
Versions:
2.0 final
Assignee: Max Rydahl Andersen
Reporter: Will Glass-Husain
Created: Sun, 13 Jul 2003 9:30 PM
Updated: Sun, 13 Jul 2003 9:34 PM
Environment: Win XP/JDK 1.3.1
Description:
The code generator used a SortedMap to represent the following composite element.
<class name="com.wgh.om.Rent" table="rent">
<meta attribute="generated-class">com.wgh.om.base.Rent</meta>
<id name="rent_id" type="long" unsaved-value="null">
<generator class="identity"/>
</id>
<map name="amenities">
<key column="rent_id" />
<index column="name" type="string" />
<composite-element class="com.wgh.om.RentAmenity">
<meta attribute="generated-class">com.wgh.om.base.RentAmenity</meta>
<property name="name" type="string" not-null="true"/>
<property name="category" type="int" />
</composite-element>
</map>
</class>
When I saved the class with this code, I received a PropertyAccessException from cglib. (with the optimizer turned off).
hs = HibernateWrapper.getNewSession(ctx);
o = new Rent();
o.setAmenities(new TreeMap());
hs.close();
hs = HibernateWrapper.getNewSession(ctx);
hs.saveOrUpdate(o);
hs.flush();
hs.connection().commit();
hs.close();
2003-07-13 19:29:04 DEBUG java.lang.ClassCastException: net.sf.hibernate.collection.Map
at com.novogradac.valuation.om.RentMetaClass3.setPropertyValues(<generated>)
at net.sf.hibernate.persister.AbstractEntityPersister.setPropertyValues(AbstractEntityPersister.java:158)
at net.sf.hibernate.impl.SessionImpl.doSave(SessionImpl.java:724)
at net.sf.hibernate.impl.SessionImpl.save(SessionImpl.java:620)
at net.sf.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:1214)
The solution was to either (A) add sort="natural" to the map hbm.xml, or to change the generated code to use Map instead of SortedMap.
Recommendation-- have the codegenerator only use SortedMaps when the sorted attribute is present in the hbm.xml.
---------------------------------------------------------------------
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-14 02:30:43
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-190 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-190 Summary: codegenerator creates SortedMap when it should create Map Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: toolset Versions: 2.0 final Assignee: Reporter: Will Glass-Husain Created: Sun, 13 Jul 2003 9:30 PM Updated: Sun, 13 Jul 2003 9:30 PM Environment: Win XP/JDK 1.3.1 Description: The code generator used a SortedMap to represent the following composite element. <class name="com.wgh.om.Rent" table="rent"> <meta attribute="generated-class">com.wgh.om.base.Rent</meta> <id name="rent_id" type="long" unsaved-value="null"> <generator class="identity"/> </id> <map name="amenities"> <key column="rent_id" /> <index column="name" type="string" /> <composite-element class="com.wgh.om.RentAmenity"> <meta attribute="generated-class">com.wgh.om.base.RentAmenity</meta> <property name="name" type="string" not-null="true"/> <property name="category" type="int" /> </composite-element> </map> </class> When I saved the class with this code, I received a PropertyAccessException from cglib. (with the optimizer turned off). hs = HibernateWrapper.getNewSession(ctx); o = new Rent(); o.setAmenities(new TreeMap()); hs.close(); hs = HibernateWrapper.getNewSession(ctx); hs.saveOrUpdate(o); hs.flush(); hs.connection().commit(); hs.close(); 2003-07-13 19:29:04 DEBUG java.lang.ClassCastException: net.sf.hibernate.collection.Map at com.novogradac.valuation.om.RentMetaClass3.setPropertyValues(<generated>) at net.sf.hibernate.persister.AbstractEntityPersister.setPropertyValues(AbstractEntityPersister.java:158) at net.sf.hibernate.impl.SessionImpl.doSave(SessionImpl.java:724) at net.sf.hibernate.impl.SessionImpl.save(SessionImpl.java:620) at net.sf.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:1214) The solution was to either (A) add sort="natural" to the map hbm.xml, or to change the generated code to use Map instead of SortedMap. Recommendation-- have the codegenerator only use SortedMaps when the sorted attribute is present in the hbm.xml. --------------------------------------------------------------------- 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-14 00:52:43
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-189 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-189 Summary: About "left join" at HQL Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.0.1 Assignee: Reporter: zhongjin Created: Sun, 13 Jul 2003 7:52 PM Updated: Sun, 13 Jul 2003 7:52 PM Description: I use "left join" at a HQL,when I use Oracle,this is not issue,but I use Sybase,the error is issue that "com.sybase.jdbc2.jdbc.SybSQLException: Incorrect syntax near 'left'. ",How can I solve this issue? --------------------------------------------------------------------- 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-13 18:48:43
|
Message:
The following issue has been closed.
Resolver: Max Rydahl Andersen
Date: Sun, 13 Jul 2003 1:48 PM
is already fixed in cvs
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-188
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-188
Summary: Code generation for map is broken
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
toolset
Versions:
2.1
2.0 final
2.0.1
2.0.2
Assignee:
Reporter: Georg Schneemayer
Created: Sun, 13 Jul 2003 12:43 PM
Updated: Sun, 13 Jul 2003 1:48 PM
Environment: all
Description:
Problem:
The check for a sorted Collection in the class net.sf.hibernate.tool.hbm2java.ClassMapping in line 506 is broken for map Elements. It assumes that the sort attribute is defined for maps. But the sort attribute is optional for the map element according to the Hibernate Mapping DTD. (For the set element it is defined with the default value of "unsorted" by the DTD.)
Solution:
change DTD:
235 <!ATTLIST map sort CDATA #IMPLIED>
->
235 <!ATTLIST map sort CDATA "unsorted">
or
change net.sf.hibernate.tool.hbm2java.ClassMapping:
506 if (!"unsorted".equals(collection.getAttributeValue("sort"))) {
->
506 String sort = collection.getAttributeValue("sort");
507 if ((sort != null)&&
(!"unsorted".equals(sort))) {
---------------------------------------------------------------------
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-13 18:48:43
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Sun, 13 Jul 2003 1:47 PM
Body:
That is already fixed in CVS (is it not ?)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-188
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-188
Summary: Code generation for map is broken
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
toolset
Versions:
2.1
2.0 final
2.0.1
2.0.2
Assignee:
Reporter: Georg Schneemayer
Created: Sun, 13 Jul 2003 12:43 PM
Updated: Sun, 13 Jul 2003 12:43 PM
Environment: all
Description:
Problem:
The check for a sorted Collection in the class net.sf.hibernate.tool.hbm2java.ClassMapping in line 506 is broken for map Elements. It assumes that the sort attribute is defined for maps. But the sort attribute is optional for the map element according to the Hibernate Mapping DTD. (For the set element it is defined with the default value of "unsorted" by the DTD.)
Solution:
change DTD:
235 <!ATTLIST map sort CDATA #IMPLIED>
->
235 <!ATTLIST map sort CDATA "unsorted">
or
change net.sf.hibernate.tool.hbm2java.ClassMapping:
506 if (!"unsorted".equals(collection.getAttributeValue("sort"))) {
->
506 String sort = collection.getAttributeValue("sort");
507 if ((sort != null)&&
(!"unsorted".equals(sort))) {
---------------------------------------------------------------------
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-13 17:43:43
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-188 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-188 Summary: Code generation for map is broken Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: toolset Versions: 2.1 2.0 final 2.0.1 2.0.2 Assignee: Reporter: Georg Schneemayer Created: Sun, 13 Jul 2003 12:43 PM Updated: Sun, 13 Jul 2003 12:43 PM Environment: all Description: Problem: The check for a sorted Collection in the class net.sf.hibernate.tool.hbm2java.ClassMapping in line 506 is broken for map Elements. It assumes that the sort attribute is defined for maps. But the sort attribute is optional for the map element according to the Hibernate Mapping DTD. (For the set element it is defined with the default value of "unsorted" by the DTD.) Solution: change DTD: 235 <!ATTLIST map sort CDATA #IMPLIED> -> 235 <!ATTLIST map sort CDATA "unsorted"> or change net.sf.hibernate.tool.hbm2java.ClassMapping: 506 if (!"unsorted".equals(collection.getAttributeValue("sort"))) { -> 506 String sort = collection.getAttributeValue("sort"); 507 if ((sort != null)&& (!"unsorted".equals(sort))) { --------------------------------------------------------------------- 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-13 17: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-187 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-187 Summary: Problem with limit clause and named parameters Type: Bug Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.0 final Assignee: Reporter: William Drai Created: Sun, 13 Jul 2003 12:36 PM Updated: Sun, 13 Jul 2003 12:36 PM Description: When using a limit clause and named parameters in a query, the limit parameters are not populated correctly when a parameter is used multiple times. for example the query "from c where c.field1 = :arg and c.field2 = :arg" won't work with a limit clause. I think the problem is that the bindNamedParameters method in QueryTranslator always returns the namedParams map size, instead of counting all parameters instances. --------------------------------------------------------------------- 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-13 17:25:43
|
The following comment has been added to this issue:
Author: William Drai
Created: Sun, 13 Jul 2003 12:25 PM
Body:
I have seen that you have fixed this problem in the last CVS tree.
Thank you for this.
William
---------------------------------------------------------------------
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/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.
