[
https://issues.apache.org/jira/browse/DERBY-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510581
]
Mamta A. Satoor commented on DERBY-2777:
----------------------------------------
Made a simple checkin for TernaryOperatorNode into main (checkin 553735) and
10.3.1.1 codeline(checkin 553736). Commit comments were as follows
DERBY-2777
TernaryOperatorNode was incorrectly setting up collation for non-character
string type. Collation only applies to character
string types. Also, fixed a comment to be more meaningful.
> 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
> Fix For: 10.3.1.1, 10.4.0.0
>
>
> 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.
