Dustin J. Mitchell 25911b44a6 More explicit requirements regarding add_version ...

The core crate calls `get_client` and verifies the `latest_version_id`
before it invokes `add_version`. With the SQLite backend, transactions
lock the entire database, so these two queries cannot be interleaved
with any changes to the `latest_version_id` and there's no possibility
of incorrect updates. With Postgres (#129) the effect is similar: the
read performed by `get_client` locks that row and prevents other
transactions from writing to it.

However, the storage trait should not rely on this behavior --
`add_version` should verify that it is adding a new version on top of
the correct parent version.

2025-07-13 13:04:38 -04:00

..

error.rs

Reorganize the core API (#60)

2024-11-19 18:22:42 -05:00

inmemory.rs

Make Storage methods async

2025-07-11 17:37:14 -04:00

lib.rs

Reorganize the core API (#60)

2024-11-19 18:22:42 -05:00

server.rs

assert as suggested, remove outcommented code

2025-07-12 22:58:59 -04:00

storage.rs

More explicit requirements regarding add_version

2025-07-13 13:04:38 -04:00