A quick reply on one point:
From: Amirouche Boubekki <xxxxxx@gmail.com>
Date: Monday, June 24, 2019 11:57 AM
okvs and nstore operations require a transaction handle, but single stand alone database operations that are an implicit transaction, like:
(okvs-in-transaction db (lambda (txn) (okvs-ref txn (pack "hello"))))
[...]
This might also slow them down by requiring 3 round trip calls to the database when only 1 is required.
How 3 round trips? I don't understand the what is the problem if there is one....
I'm postulating KVS databases where you need one round trip to start the transaction and get its handle, one to do a single isolated operation, and one to commit the transaction. Vs. opening the connection in a default commit mode where operations are always committed unless a start transaction is first done for multiple following operations, followed by a commit (with possible nesting of transactions).
- Harold