Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 21949 invoked from network); 4 Sep 2007 21:39:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Sep 2007 21:39:09 -0000 Received: (qmail 95983 invoked by uid 500); 4 Sep 2007 21:39:03 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 95940 invoked by uid 500); 4 Sep 2007 21:39:03 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 95931 invoked by uid 99); 4 Sep 2007 21:39:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2007 14:39:03 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2007 21:40:21 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id C3A3A714035 for ; Tue, 4 Sep 2007 14:38:44 -0700 (PDT) Message-ID: <3478277.1188941924791.JavaMail.jira@brutus> Date: Tue, 4 Sep 2007 14:38:44 -0700 (PDT) From: "Daniel John Debrunner (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-2972) Update or select with function in the where clause causes with TERRITORY_BASED collation fails with ERROR 42818: Comparisons between 'VARCHAR' and 'VARCHAR' are not supported. In-Reply-To: <857349.1185293311103.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524882 ] Daniel John Debrunner commented on DERBY-2972: ---------------------------------------------- Rule 3 on the wiki page is only about situations where a data type definition is explicitly used, like CHAR(10), VARCHAR(10) etc. So String literal is not a specific instance of rule 3. >From the list in the last comment, the only additional one is XMLSERIALIZE, leading to Routine definition XMLSERIALIZE CAST being the only implementation defined instances of rule 3. > Update or select with function in the where clause causes with TERRITORY_BASED collation fails with ERROR 42818: Comparisons between 'VARCHAR' and 'VARCHAR' are not supported. > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-2972 > URL: https://issues.apache.org/jira/browse/DERBY-2972 > Project: Derby > Issue Type: Bug > Components: SQL > Affects Versions: 10.4.0.0 > Reporter: Kathey Marsden > Assignee: Kathey Marsden > Attachments: derby-2972_diff.txt, derby-2972_stat.txt > > > The following update fails with ERROR 42818 > ij> update testing set a = PADSTRING('aa',2024) where a = PADSTRING('a',2024); > ERROR 42818: Comparisons between 'VARCHAR' and 'VARCHAR' are not supported. > See full script below > onnect 'jdbc:derby:nordb;territory=no_NO;collation=TERRITORY_BASED'; > CREATE FUNCTION PADSTRING (DATA VARCHAR(32000), LENGTH INTEGER) RETURNS VARCHAR(32000) EXTERNAL NAME 'org.apache.derbyTesting.functionTests.util.Formatters.padString' LANGUAGE JAVA PARAMETER STYLE JAVA; > create table testing > (a varchar(2024), b varchar(1024), c varchar(1024), d varchar(2048), e varchar(300)) ; > -- insert 9 rows into the table > insert into testing values (PADSTRING('1',2024), PADSTRING('2',1024), > PADSTRING('3',1024), PADSTRING('4',2048), PADSTRING('5',300)); > insert into testing values (PADSTRING('10',2024), > PADSTRING('20',1024), PADSTRING('30',1024), > PADSTRING('40',2048), PADSTRING('50',300)); > insert into testing values (PADSTRING('100',2024), > PADSTRING('200',1024), PADSTRING('300',1024), > PADSTRING('400',2048), PADSTRING('500',300)); > insert into testing values (PADSTRING('1000',2024), > PADSTRING('2000',1024), PADSTRING('3000',1024), > PADSTRING('4000',2048), PADSTRING('5000',300)); > insert into testing values (PADSTRING('10000',2024), > PADSTRING('20000',1024), PADSTRING('30000',1024), > PADSTRING('40000',2048), PADSTRING('50000',300)); > insert into testing values (PADSTRING('100000',2024), > PADSTRING('200000',1024), PADSTRING('300000',1024), > PADSTRING('400000',2048), PADSTRING('500000',300)); > insert into testing values (PADSTRING('1000000',2024), > PADSTRING('2000000',1024), PADSTRING('3000000',1024), > PADSTRING('4000000',2048), PADSTRING('5000000',300)); > insert into testing values (PADSTRING('10000000',2024), > PADSTRING('20000000',1024), PADSTRING('30000000',1024), > PADSTRING('40000000',2048), PADSTRING('50000000',300)); > insert into testing values (PADSTRING('100000000',2024), > PADSTRING('200000000',1024), PADSTRING('300000000',1024), > PADSTRING('400000000',2048), PADSTRING('500000000',300)); > update testing set a = PADSTRING('aa',2024) where a = PADSTRING('a',2024); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.