db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2777) Parameters should take their collation from the context in which they are getting used rather than the current compilation schema
Date Fri, 06 Jul 2007 02:52:04 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510557
] 

Mamta A. Satoor commented on DERBY-2777:
----------------------------------------

Checked in a fix for the CollaitonTest2 failure. The changes went in main(revision 553703)
and 10.3.1.1(revision 553704) and commit comments are as follows

A trivial change to CollationTest2 test. Rather than relying on the number of rows in SYSCOLUMNS
for the test validity,
I am changing it so that no rows get selected from the LIKE test. This is so that over the
time, if we end up changing
the SYSCOLUMNS so that it will have more rows than what we have in the codeline today, we
won't have to go and fix the
test.


> 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.


Mime
View raw message