db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-4654) Restriction.toSQL() doesn't escape special characters
Date Fri, 14 May 2010 09:03:42 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen closed DERBY-4654.
-------------------------------------

    Issue & fix info:   (was: [Patch Available])
       Fix Version/s: 10.6.1.1
                      10.7.0.0
          Resolution: Fixed

Merged to 10.6 and committed revision 944159.

> Restriction.toSQL() doesn't escape special characters
> -----------------------------------------------------
>
>                 Key: DERBY-4654
>                 URL: https://issues.apache.org/jira/browse/DERBY-4654
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.6.1.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>             Fix For: 10.6.1.1, 10.7.0.0
>
>         Attachments: derby-4654-2.diff, derby-4654.diff
>
>
> org.apache.derby.vti.Restriction.toSQL() adds double quotes around column names, but
it does not escape the special characters (like double quotes) in the column names, so the
returned string may not be valid SQL. This could cause problems when using the restriction
to generate a query against an external database.
> Restriction.doubleQuote() should use IdUtil.normalToDelimited() to get proper quoting
of the names.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message