[
https://issues.apache.org/jira/browse/DERBY-5370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-5370:
---------------------------------
Attachment: derby-5370-01-aa-withTest.diff
Attaching derby-5370-01-aa-withTest.diff. This adds a regression test to
Brett's patch. I am running tests now.
Touches the following files:
-----------
M java/engine/org/apache/derby/vti/Restriction.java
Brett's change.
-----------
A
java/testing/org/apache/derbyTesting/functionTests/tests/lang/RestrictedTableVTI.java
M
java/testing/org/apache/derbyTesting/functionTests/tests/lang/RestrictedVTITest.java
Test case for the improved Restriction.toSQL() method.
> The toSQL method of the org.apache.derby.vti.Restriction class does not
> output correct constants for VARCHAR, Timestamp, Date, Time, or CHAR FOR BIT
> DATA types
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5370
> URL: https://issues.apache.org/jira/browse/DERBY-5370
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.8.1.2
> Reporter: Brett Bergquist
> Attachments: derby-5370-01-aa-withTest.diff, derby-5370.diff
>
>
> The toSQL method of the org.apache.derby.vti.Restriction class does not
> output correct constants for VARCHAR, Timestamp, Date, Time, or CHAR FOR BIT
> DATA types. This method is useful for building the WHERE clause when
> implementing a Restricted Table Function. The result of calling the toSQL
> method with restrictions on columns of these types does not produce valid SQL
> constants. For example with a VARCHAR column being restricted the single
> quote characters are not placed round the string constant.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
