The following issue has been updated:
Updater: Gavin King (mailto:ga...@in...)
Date: Wed, 15 Oct 2003 12:08 PM
Comment:
This is not a bug.
Note that you should be able to work around this by using functional form "sysdate()"
Changes:
type changed from Bug
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-402&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-402
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-402
Summary: where clause in collection mapping ignores dialect keywords
Type: Improvement
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.1 beta 4
Assignee:
Reporter: Edina Pimp
Created: Wed, 15 Oct 2003 11:36 AM
Updated: Wed, 15 Oct 2003 12:08 PM
Environment: oracle, jdk1.3.1_08
Description:
When the optional where clause supplied in a collection mapping is parsed, dialect specific keywords are ignored, resulting in invalid SQL being generated.
<example code>
Template.renderWhereStringTemplate(
"x < sysdate",
new Oracle9Dialect());
produces:
$PlaceHolder.x < $PlaceHolder.sysdate
</example code>
Possible fix may be to add additional code to logic beginning on line 59 of Template that starts
boolean isIdentifier = ...
New logic would check the current dialect's function map, etc.
-dc
---------------------------------------------------------------------
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
|