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
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 inf
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 inform
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 r
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?
> -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.
>
>
Kristian Waagan wrote:
Blair Zajac wrote:
Kristian Waagan wrote:
Blair Zajac wrote:
Hello Blair,
My only *guess* is that there might be a restructuring of a BTree
going on, which is not correctly reported - and you might be
experiencing a deadlock. To stop guessing and actually start
und
Knut Anders Hatlen wrote:
Blair Zajac writes:
I downloaded d2991-preview-1e.diff and applied it to r737572 of trunk.
I don't see the original problem now. Even going to 500 threads and
setting derby.locks.waitTimeout to -1 works.
Will or when will a patch for d2991 be applied to trunk?
Tha
I have reported the problem as
https://issues.apache.org/jira/browse/DERBY-4032.
The problem is reproducible given the current state of the DB. However, if
I reload the data, the problem goes away. So I conclude that use of the DB
has altered its state in some way as to cause this problem to ar
Is this reproducible on all tries?
The point of the question is to understand why you have only one row that is
not working.
What happens if you reload the data and run the test again?
Do you get the same results?
Are you loading from a file? Is there a corrupt character?
The length() function.
jrgchip 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 "Nu
11 matches
Mail list logo