db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <de...@segel.com>
Subject RE: Concurrent access problems?
Date Wed, 30 Aug 2006 23:24:26 GMT
Define "large amounts of data".

While its great that you're abstracting the database, you still have the
issue that not all databases are the same and that some require more tuning
than others.


> -----Original Message-----
> From: news [mailto:news@sea.gmane.org] On Behalf Of Mark Hellkamp
> Sent: Wednesday, August 30, 2006 5:39 PM
> To: derby-user@db.apache.org
> Subject: Re: Concurrent access problems?
> 
> Here is a quick follow-up to this issue. The problem appears to get worse
> as the
> number of rows increases in the tables used in the queries, even though
> the
> additional data should not be a factor in the queries. I did find a paper
> that
> discusses Derby
> (https://twiki.informatik.tu-
> chemnitz.de/pub/DVS/SeminarDBMSImplementation/
> Ressourcenverwaltung_Derby.pdf)that implies that Derby does not handle
> large
> amounts of data too well.
> 




Mime
View raw message