Is your feature request related to a problem? Please describe.
When comparing the APIs of RocksDB and FoundationDB for parity, I noticed that fjall only supports serialisable reads. Both RDB and FDB support making the distinction within the transaction (get vs get_for_update and snapshot: bool respectively), but fjall seems to always mark reads in the conflict manager.
Describe the solution you'd like
Some form of API exposing this functionality.
Describe alternatives you've considered
I could just fall back to serialised reads, at a potential performance penalty under load, so it's not a particulary high priority.
Is your feature request related to a problem? Please describe.
When comparing the APIs of RocksDB and FoundationDB for parity, I noticed that fjall only supports serialisable reads. Both RDB and FDB support making the distinction within the transaction (
getvsget_for_updateandsnapshot: boolrespectively), but fjall seems to always mark reads in the conflict manager.Describe the solution you'd like
Some form of API exposing this functionality.
Describe alternatives you've considered
I could just fall back to serialised reads, at a potential performance penalty under load, so it's not a particulary high priority.