allow SESSION_READ_ONLY open a DBI book without write privileges

[John Ralls]

> On Jul 13, 2026, at 18:54, array_hourly_0u at icloud.com wrote:
> 
> - Wrap a logical edit (a transaction and its splits) in one
> transaction, so the multi-object write commits atomically instead of
> the current behavior of per-instance commits.
> 
> I want to work through the details before proposing anything concrete.
> I see friction points around rollback across a multi-instance edit,
> and how the retry/reconnect path interacts with a longer-lived
> transaction. I think I'll enjoy working on this; it seems like the
> right direction. I'll follow up on the list once I have a design worth
> reviewing.

Fortunately transactions and splits commit together and save a copy so that they can roll back. I don’t think any of the other QofInstances do that. But that might not be the right model to use except perhaps as a last resort after multiple retries (with feedback to the user if it’s going to be noticeable).

Remember to watch out for deadlock potential when trying to lock more than one record at a time.

Regards,
John Ralls

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gnucash.org/pipermail/gnucash-devel/attachments/20260713/a955d1b2/attachment-0001.htm>