[
http://issues.apache.org/jira/browse/DERBY-1433?page=comments#action_12447739 ]
Bernt M. Johnsen commented on DERBY-1433:
-----------------------------------------
There's more to it. There are several instance of ad-hoc pasing in
java/client/org/apache/derby/client/am/Statement.java. E.g. when figuring out
what kind of statement it is (QUERY, UPDATE, INSERT, DELETE, CALL etc), when
{?=CALL(.....)} is unescaped (Why is that necassry for CALL when it's not
needed for other escapes).
The proper solution would be one lightweight parser for all these needs (The
even more proper solution would have been a network protocol on a semantic
layer where such client parsing were unecessary).
> Client driver does not handle string literals containing "where current of"
> correctly
> -------------------------------------------------------------------------------------
>
> Key: DERBY-1433
> URL: http://issues.apache.org/jira/browse/DERBY-1433
> Project: Derby
> Issue Type: Bug
> Components: SQL, Network Client
> Affects Versions: 10.2.1.6
> Reporter: Knut Anders Hatlen
> Assigned To: Bernt M. Johnsen
> Fix For: 10.2.2.0
>
> Attachments: cursor.java
>
>
> If a string literal contains 'where current of something', the client driver
> tries to substitute 'something' with the corresponding cursor name on the
> server. This can lead to an exception being raised (no such cursor) or the
> string literal being modified. See attached repro.
> The bug is also present in JCC.
--
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
