db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Whitt" <j.wh...@insightbb.com>
Subject Re: Weird
Date Wed, 15 Apr 2009 11:02:31 GMT
please remove me from this group
----- Original Message ----- 
From: "Knut Anders Hatlen" <Knut.Hatlen@Sun.COM>
To: "Derby Discussion" <derby-user@db.apache.org>
Sent: Wednesday, April 15, 2009 4:58 AM
Subject: Re: Weird

> ArtemGr <artemciy@gmail.com> writes:
>> Knut Anders Hatlen <Knut.Hatlen@...> writes:
>>> There should be another exception linked to the main exception. Look for
>>> the string "Caused by:". If you could post that exception too, it would
>>> be easier to see exactly where in the Derby code the error happens.
>> Oh, maybe this one?
>> http://gist.github.com/95679
> Thanks, that's it! It would be great if you could log a bug report at
> https://issues.apache.org/jira/browse/DERBY and post the stack trace
> there.
>> For some reason I can no longer reproduce the bug.
>> I don't think I have changed anything,
>> except switching to "db-derby-"
>> in order to produce a better stack trace.
>> (Then I've tried switching back to db-derby-
>> but still no bug).
>> Could it be I accidentally had a wrong version of Derby?
> It looks like it happens during the first compilation of a meta-data
> statement. The compiled query plan is stored in the database, so if you
> first get it compiled and stored, you'll probably not see the problem
> again. Maybe you need to start with a fresh database to reproduce it. Or
> perhaps it's related to database upgrade (I noticed that your code
> mentioned upgrade=true in one of the comments).
> -- 
> Knut Anders 

View raw message