[ http://issues.apache.org/jira/browse/JDO-370?page=all ]
Michael Bouschen updated JDO-370:
---------------------------------
Attachment: JDO-370.patch
Good catch! I agree, the second query is invalid. It is supposed to be testing
the replacement of the query filter, so it does not need to declare (and set)
any parameters.
Attached you find a patch (JDO-370.patch) for review. With this patch the
second and third query do not declare any parameters and do not pass any actual
parameter values to execute. I propose I fix this in the trunk and in the 2.0
branch.
> Valid query seems invalid in SetterReplacePreviousValues
> --------------------------------------------------------
>
> Key: JDO-370
> URL: http://issues.apache.org/jira/browse/JDO-370
> Project: JDO
> Type: Bug
> Components: tck20
> Reporter: Ilan Kirsh
> Attachments: JDO-370.patch
>
> Probably I am missing something, but as far as I can see the second valid
> query in org.apache.jdo.tck.query.api.SetterReplacePreviousValues, has a
> String parameter and receives a long argument, so it should throw an
> exception, isn't it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
