db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From shabz <shahbaz.ty...@sphere.ae>
Subject Re: Derby crash (urgent)
Date Thu, 12 Jun 2008 07:41:11 GMT

Its old DB generated with 10.3


Knut Anders Hatlen wrote:
> 
> Bassel_kh <bkhashfeh@hotmail.com> writes:
> 
>> Actually, I removed C3P0 totally, and upgraded derby to 10.4, the new
>> Exception occured:
> 
> Hi,
> 
> Did you create a new database after upgrading to Derby 10.4, or did you
> continue with an old database created with an earlier version of Derby?
> I'm asking this to find out if this is a new bug or a know bug that was
> fixed in Derby 10.4. If the database has become corrupted (as we know
> could happen with some of the 10.2 and 10.3 releases), upgrading Derby
> won't help you accessing that database.
> 
>> I got tired of using Derby, It is not that professional, and still not
>> stable!!
> 
> If it is possible, it would be great if you could post some code to
> reproduce the problem. That would be very helpful for those who would
> like to track it down and make Derby more stable.
> 
>> Also new bug came today: Inconsistent index!!
> 
> My guess is that it is probably not a new bug, just a different
> manifestation of the same one. Since it seems like your database has
> become corrupted, all sorts of errors may happen, and the exact error
> message may vary depending on which operation is performed when the
> damaged data is accessed.
> 
> -- 
> Knut Anders
> 
> 

-- 
View this message in context: http://www.nabble.com/Derby-crash-%28urgent%29-tp16217446p17794274.html
Sent from the Apache Derby Developers mailing list archive at Nabble.com.


Mime
View raw message