I picked SQLite for its minuscule (by today's standards) footprint, simplicity, and ease of deployment.
Why do I get the feeling I've bought into a product like any model in the American car market. With each passing interation the vehicle gets bigger, fatter, and less efficient. This continues until the model bears absolutely no resemblance to the original. But, it does have electric fold down rear seats to the advantage of the totally clueless. If all these MySQL and PostgreSQL imitator "features" could be developed as "plug in" modules that leaves SQLite as it was for those who liked it the way it was when they picked the product, I would not really care who did what about complex locking situations. Guess I need to start "shopping" again :-( Fred >-----Original Message----- >From: b.bum [mailto:[EMAIL PROTECTED] >Sent: Friday, September 24, 2004 12:34 PM >To: [EMAIL PROTECTED] >Cc: Ara.T.Howard >Subject: Re: [sqlite] Lock files.... > > >On Sep 24, 2004, at 10:42 AM, Eddy Macnaghten wrote: >> I am getting some tests together now. As soon as I have got it ready >> enough I will put it on my site and inform the list... > >As a part of your tests, it would be helpful to have some abuse tests >that involve multiple processes reading/writing against the same >database file using the regular locking path. I don't believe this is >a case covered in the unit tests. > >b.bum
