[
https://issues.apache.org/jira/browse/DERBY-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502936
]
Mamta A. Satoor commented on DERBY-2777:
----------------------------------------
Fixed the parameters collation type in LENGTH operator with revision 545621.
Commit comments are as follows
DERBY-2777
Fixed the combination of LENGTH operator and parameters so that the parameters
take their collation from the context and not from the current compilation
schema. In fact, it appears that LENGTH operator is not allowed to take a
parameter and user would get sql exception 42X36 if LENGTH was used with a
parameter. I have added a test case for that.
> Parameters should take their collation from the context in which they are
> getting used rather than the current compilation schema
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2777
> URL: https://issues.apache.org/jira/browse/DERBY-2777
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.3.0.0
> Reporter: Mamta A. Satoor
> Assignee: Mamta A. Satoor
>
> With revision 542646, changes were made so that parameters will take their
> collation from current compilation schema. But based on the following thread
> http://www.nabble.com/Collation-and-parameter-markers-(-)-tf3866040.html ,
> using the collation from the context would be the correct thing to do for the
> parameters.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
