kero on Nostr: npub1y0emt…smm9n What do you think about making mdb_txn_begin accept the write txn ...

npub1y0emt2wlpsezcnmxtyrpf33qe7gwy5u8yzssvv6uw53em0k32t7q7smm9n (npub1y0e…mm9n) What do you think about making mdb_txn_begin accept the write txn as the parent parameter and accept the MDB_RDONLY flag simultaneously? The same restrictions apply to the write txn (only abort and commit allowed). It is possible to call this function multiple times, to use the read transactions in parallel and only from the write txn program.