logic does not account for that possibility. So,
depending on the access path chosen and the logic used to satisfy the query,
the record might be found or not found.
--
View this message in context:
http://www.nabble.com/Record-not-found-in-some-SQL---Bug--tp21700110p21748874.html
Sent from
missing something?
-Mike
-Original Message-
From: jrgchip [mailto:c...@datamology.com]
Sent: Friday, January 30, 2009 9:10 AM
To: derby-user@db.apache.org
Subject: Re: Record not found in some SQL - Bug?
jrgchip wrote:
The failure still occurs.
Per investigation in DERBY
Rick Hillegas richard.hille...@sun.com writes:
jrgchip wrote:
Can you point me to information about that corruption bug?
Please see the release notes for 10.3.3.0 (
http://db.apache.org/derby/releases/release-10.3.3.0.cgi ) Detailed
information can be found on the associated bug report:
Rick Hillegas-2 wrote:
Upgrading to 10.3.3.0 will remove this theory from consideration.
I tested with v10.3.3.0 and v10.4.2.0...to no avail. The failure still
occurs.
--
View this message in context:
http://www.nabble.com/Record-not-found-in-some-SQL---Bug--tp21700110p21727785.html
jrgchip c...@datamology.com writes:
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
-Original Message-
From: jrgchip [mailto:c...@datamology.com]
Sent: Wednesday, January 28, 2009 10:10 AM
To: derby-user@db.apache.org
Subject: Re: Record not found in some SQL - Bug?
I have reported the problem as
https://issues.apache.org/jira/browse/DERBY-4032
de...@segel.com wrote:
-Original Message-
From: jrgchip [mailto:c...@datamology.com]
Sent: Wednesday, January 28, 2009 10:10 AM
To: derby-user@db.apache.org
Subject: Re: Record not found in some SQL - Bug?
[ snip ]
How did you load the data?
What character set(s) are you using
Have you tried to run the Derby consistency checker? (See
http://wiki.apache.org/db-derby/DatabaseConsistencyCheck).
Maybe that could give some clue about what is wrong.
--
Øystein
jrgchip wrote:
I have reported the problem as
https://issues.apache.org/jira/browse/DERBY-4032.
The problem is
this message in context:
http://www.nabble.com/Record-not-found-in-some-SQL---Bug--tp21700110p21714590.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
jrgchip wrote:
oysteing wrote:
Have you tried to run the Derby consistency checker?
Yes...it reports all 44 tables as OK per SYSCS_CHECK_TABLE.
Kristian Waagan-4 wrote:
Be aware that 10.3.1.4 and 10.3.2.1 had a corruption bug, mostly (or
only) seen on Windows.
Can you point me to
jrgchip wrote:
oysteing wrote:
Have you tried to run the Derby consistency checker?
Yes...it reports all 44 tables as OK per SYSCS_CHECK_TABLE.
Kristian Waagan-4 wrote:
Be aware that 10.3.1.4 and 10.3.2.1 had a corruption bug, mostly (or
only) seen on Windows.
Can you
';
I am using Java DB v10.3.2.1.
--
View this message in context:
http://www.nabble.com/Record-not-found-in-some-SQL---Bug--tp21700110p21700110.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
12 matches
Mail list logo