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] Updated: (DERBY-4654) Restriction.toSQL() doesn't escape special characters
Date Fri, 14 May 2010 08:41:43 GMT

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

Knut Anders Hatlen updated DERBY-4654:

    Attachment: derby-4654-2.diff

The new test for DERBY-4651 conflicted with the test in the patch for this issue. Uploading
a new patch with an updated test.

Committed revision 944152.

> 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:
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>         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.

View raw message