mirror of
https://code.briarproject.org/briar/briar.git
synced 2026-02-12 18:59:06 +01:00
7ed85c62c3e3f3ab62f37268de697860c1ca5115
Previously, when table A had a foreign key pointing to table B, we got read locks on A and B to read A, a write lock on A and a read lock on B to update A, and a write lock on B to update B (but this wasn't applied consistently). Now we get a read lock on A to read A, a write lock on A to update A, and write locks on A and B to update B. The difference is small in practice, but clarifying the rules has helped to catch some bugs.
Description
Secure messaging, anywhere.
Languages
Java
97.9%
Kotlin
1.9%