You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Brett Bergquist (JIRA)" <ji...@apache.org> on 2011/08/02 15:51:27 UTC
[jira] [Commented] (DERBY-5370) 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
[ https://issues.apache.org/jira/browse/DERBY-5370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13076206#comment-13076206 ]
Brett Bergquist commented on DERBY-5370:
----------------------------------------
Actually it is not the column types that matter, but rather constant types that are passed with the SELECT statement WHERE clause that uses a Restricted Table Function. These constant types are not correctly reproduced by the 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
>
> 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