Re: [sqlite] Testing the 'I' in ACID

2014-11-25 Thread Igor Tandetnik
On 11/25/2014 5:41 PM, Simon Slavin wrote: Fair point. I should have written 'writing concurrency'. I would be interested in anything you have to say about the article I referred to. I don't see much in the way of reasoning in that article, and I'm too lazy to look at the code. Insofar as

Re: [sqlite] Testing the 'I' in ACID

2014-11-25 Thread Simon Slavin
On 25 Nov 2014, at 10:39pm, Igor Tandetnik wrote: > On 11/25/2014 5:32 PM, Simon Slavin wrote: >> SQLite doesn't support massive concurrency because it locks the entire >> database during changes. > > Not entirely true. WAL mode allows one writer working concurrently with

Re: [sqlite] Testing the 'I' in ACID

2014-11-25 Thread Igor Tandetnik
On 11/25/2014 5:32 PM, Simon Slavin wrote: SQLite doesn't support massive concurrency because it locks the entire database during changes. Not entirely true. WAL mode allows one writer working concurrently with multiple readers. -- Igor Tandetnik

[sqlite] Testing the 'I' in ACID

2014-11-25 Thread Simon Slavin
The 'I' in ACID stands for 'isolation'. In SQLite terms it means that a change made in one transaction doesn't affect another until the transaction is committed, at which point it does affect the database and transactions made afterwards. SQLite doesn't support massive concurrency because it