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
|
