Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <563594302.1233221759696.JavaMail.jira@brutus>
Date: Thu, 29 Jan 2009 01:35:59 -0800 (PST)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4032) Record not found in some SQL
In-Reply-To: <504041643.1233158521920.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668383#action_12668383 ] 

Knut Anders Hatlen commented on DERBY-4032:
-------------------------------------------

Thanks for testing the queries. If the two queries had returned different results, it would have meant that the row only in the base table and not in the index (or vice versa), which would have explained why the row sometimes shows up and sometimes doesn't. But that's not the case, apparently.

I downloaded the database and tried to boot it, but it appears to be encrypted, and I don't have the boot password. Booting the database failed with this error message:

ERROR XBM06: Startup failed. An encrypted database cannot be accessed without the correct boot password.

> Record not found in some SQL
> ----------------------------
>
>                 Key: DERBY-4032
>                 URL: https://issues.apache.org/jira/browse/DERBY-4032
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.3.2.1
>         Environment: Windows XP
>            Reporter: Chip Hartney
>         Attachments: OrderEntryDB-base.zip, OrderEntryDB-seg0-part1.zip, OrderEntryDB-seg0-part2.zip, OrderEntryDB-seg0-part3.zip, OrderEntryDB-seg0-part4.zip, OrderEntryDB-seg0-part5.zip, OrderEntryDB-seg0-part6.zip, OrderEntryDB-seg0-part7.zip
>
>
> Per discussion at http://www.nabble.com/Record-not-found-in-some-SQL---Bug--td21700110.html...
> I have a "Product" table with a "Num" column that contains a record that is only accessible by some SQL and not others.  I have tested this by JDBC access from my Java app as well was from IJ directly.
> ij> select "Num", length("Num") as "Len" from app."Product" where "Num" like 'HG1549%';
> Num            |Len
> ----------------------------
> HG15490        |7
> HG15493        |7
> HG15497        |7   <== Found as expected
> HG15499        |7
> 4 rows selected
> ij> select "Num" from app."Product" where "Num" = 'HG15490';
> Num
> ----------------
> HG15490  <== Found as expected
> 1 row selected
> ij> select "Num" from app."Product" where "Num" = 'HG15493';
> Num
> ----------------
> HG15493  <== Found as expected
> 1 row selected
> ij> select "Num" from app."Product" where "Num" = 'HG15499';
> Num
> ----------------
> HG15499  <== Found as expected
> 1 row selected
> ij> select "Num" from app."Product" where "Num" = 'HG15497';
> Num
> ----------------
> 0 rows selected  <== Not found!!!
> What could possibly hide the 'HG15497' record from the last SELECT?
> And it's not just a matter of equality versus inequality...as the following SQL does return the record:
>     SELECT I."STYLE" FROM TEMP."ZJVINV2" AS I INNER JOIN APP."Product" AS P ON I."STYLE" = P."Num" WHERE I."STYLE" = 'HG15497'; 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.