Return-Path: 
 <derby-dev-return-6963-apmail-db-derby-dev-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-derby-dev-archive@www.apache.org
Received: (qmail 76841 invoked from network); 21 Jul 2005 20:18:15 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 21 Jul 2005 20:18:15 -0000
Received: (qmail 41263 invoked by uid 500); 21 Jul 2005 20:18:11 -0000
Delivered-To: apmail-db-derby-dev-archive@db.apache.org
Received: (qmail 41100 invoked by uid 500); 21 Jul 2005 20:18:10 -0000
Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:derby-dev-help@db.apache.org>
list-unsubscribe: <mailto:derby-dev-unsubscribe@db.apache.org>
List-Post: <mailto:derby-dev@db.apache.org>
List-Id: <derby-dev.db.apache.org>
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Delivered-To: mailing list derby-dev@db.apache.org
Received: (qmail 40996 invoked by uid 99); 21 Jul 2005 20:18:09 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=SPF_FAIL
X-Spam-Check-By: apache.org
Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jul 2005 13:17:57 -0700
Received: from ajax.apache.org (ajax.apache.org [127.0.0.1])
	by ajax.apache.org (Postfix) with ESMTP id 17A41D2
	for <derby-dev@db.apache.org>; Thu, 21 Jul 2005 22:17:54 +0200 (CEST)
Message-ID: <349572567.1121977074095.JavaMail.jira@ajax.apache.org>
Date: Thu, 21 Jul 2005 22:17:54 +0200 (CEST)
From: "David Van Couvering (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-20) LIKE handles strings with control
 characters incorrectly.
In-Reply-To: <1683177649.1096485110863.JavaMail.apache@nagoya>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

    [ http://issues.apache.org/jira/browse/DERBY-20?page=comments#action_12316408 ] 

David Van Couvering commented on DERBY-20:
------------------------------------------

This issue came up with EJBQL testing of the app server here at Sun.  I am including some comments from the folks doing the testing (Sailaja Rao).  Hopefully this will help us resolve this item

The below EJBQL query
> when run does not return any dataset.  When it is supposed to return the
> following as possible matches :
> 
> Ber%in
> Ber%lin
> 
> *SELECT OBJECT(le) FROM LIKEESCAPE le WHERE le.name LIKE 'Ber\%%' ESCAPE
> '\' *
> 
> where the dataset contains the values :
> 
> insert into LIKEESCAPE values('1', 'Berlin');
> insert into LIKEESCAPE values('2', 'Ber_in');
> insert into LIKEESCAPE values('3', 'Ber\in');
> insert into LIKEESCAPE values('4', 'Ber%in');
> insert into LIKEESCAPE values('5', 'Berin');
> insert into LIKEESCAPE values('6', 'Ber%lin');

Here is the SQL statement, when the test is executed. I am also attaching the server.log file.

[#|2005-07-20T17:43:13.031-0800|FINE|TestAbbrevProductName9.0|javax.enterprise.resource.jdo.sqlstore.sql|_ThreadID=15;|SQL statement<select t0."CUSTNO", t0."NAME" from "LIKEESCAPE" t0 where t0."NAME" LIKE ?  ESCAPE ? > with input values:java.lang.String:Ber\%%, java.lang.Character:\|#]

> LIKE handles strings with control characters incorrectly.
> ---------------------------------------------------------
>
>          Key: DERBY-20
>          URL: http://issues.apache.org/jira/browse/DERBY-20
>      Project: Derby
>         Type: Bug
>   Components: SQL
>     Versions: 10.0.2.0
>     Reporter: Tulika Agrawal
>     Priority: Minor
>  Attachments: server.log
>
> Reporting for Daniel John Debrunner.
> If a string contains control characters in the regions matched 
> by wild card characters then in some situations a LIKE will 
> return false instead of true and the row will not be returned.
> Caused by the dynamic like optimization using >= with a prefix 
> which is is equivalent to >= on the prefeix appended with 
> blanks and not null (\u0000) characters.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira