Jerome Gravel-Niquet

It might be possible to prevent multiple connections from writing by acquiring the singular permit in the "write semaphore" and using the [sqlite backup API](https://docs.rs/rusqlite/latest/rusqlite/backup/index.html) to get both progress report...

Buckets-based hashing for gentler resource utilization

1

Corrosion presently makes full table scans to hash the contents of everything to be able to compare consistency between actors. This is an expensive operation and it gets more and...

SQLite interruption seem to put Corrosion in a bad state

1

There's a 30s timeout for releasing a checked in *write* SQLite connection. This is to prevent any one write query from blocking every other. The way this is enforced is...

During synchronization, a peer starts sending fairly large buffers (64KB at the time of this writing) and that can create congestion. It might be faster to start w/ a buffer...

In SQLite, it's possible to return data as part of an INSERT or UPDATE. It could also make sense to use a transaction for reading data only (if you want...

Corrosion track bookkeeping in memory, as well as in SQLite. It uses more efficient data structures in memory. This makes accessing the state of Corrosion out-of-band very fast and easy....

Reproduction: ``` sqlite> create table foo (id int not null primary key, text text, text2 text, num int, num2 int); sqlite> select crsql_as_crr('foo'); OK sqlite> insert into foo values (1,...