News for hackers. Stuff that matters.
Re:SQLite – The “server-process-edition” branch by deepakprakash on Wednesday August 15, 2018 @01:53PM (#17768134)
Can someone explain a bit more?

(a) Does this mean that there will be an sqlite version that can be deployed as a process accessible over network in servers?

(b) Does this mean that sqlite will now have the capability to do concurrent reads/writes, but that it is upto users to implement a process that can take advantage of this and create something like (a)?

Re:SQLite – The “server-process-edition” branch by X-Istence on Wednesday August 15, 2018 @01:56PM (#17768188)
> (a) Does this mean that there will be an sqlite version that can be deployed as a process accessible over network in servers?

No.

> (b) Does this mean that sqlite will now have the capability to do concurrent reads/writes, but that it is upto users to implement a process that can take advantage of this and create something like (a)?

Yes... this allows a multi-threaded application for example to have multiple readers/writers without blocking each other.

Re:SQLite – The “server-process-edition” branch by nbevans on Wednesday August 15, 2018 @04:44PM (#17769595)
... as long as those threads don't touch the same page as each other. Page locks <> row locks.
Re:SQLite – The “server-process-edition” branch by blattimwind on Wednesday August 15, 2018 @06:53PM (#17770453)
Depends on the width of your rows and the relation of access patterns to physical row allocation.
Re:SQLite – The “server-process-edition” branch by hd4 on Wednesday August 15, 2018 @02:02PM (#17768256)
For some reason, I had the idea that this was always the case with SQLite, at least for the last 10 years or so.
Re:SQLite – The “server-process-edition” branch by blattimwind on Wednesday August 15, 2018 @02:03PM (#17768267)
In WAL mode, readers don't block writers and vice versa, but there can still only be one writer active at any given time.
Re:SQLite – The “server-process-edition” branch by dragonwriter on Wednesday August 15, 2018 @01:56PM (#17768179)
This provides (b), not (a).