My understanding is that SQLite suppprts only system locks. So multiple writers will need to be either blocking on system level or implement some other form of locking to ensure integrity.
A great deal of complexity of DBMS is in granularity of locks, its escalation/deescalation, and shared use performance.
I wonder if one day SQLite would support synchronization/replication protocol. In a way Fossil SCM is an attempt at SQLite replication, albeit a specialized one.
> A great deal of complexity of DBMS is in granularity of locks, its escalation/deescalation, and shared use performance.
Agreed.
> My understanding is that SQLite suppprts only system locks
Is this any different than a process blocking on a mutex while another writes to a shared resource? I understand DBMS do it better, but I don't see why it's viewed as a non-starter for SQLite.
A great deal of complexity of DBMS is in granularity of locks, its escalation/deescalation, and shared use performance.
I wonder if one day SQLite would support synchronization/replication protocol. In a way Fossil SCM is an attempt at SQLite replication, albeit a specialized one.