27 May
2016
27 May
'16
6:11 a.m.
This works as intended. Each transaction is atomic, and shall see neither DBIs nor data which were committed after the transaction began. Cross-txn mdb_dbi_open() is in any case hairy to get right, we screwed it up several times before arriving at the now-obvious semantics.
An application can open and cache its DBIs in a separate startup transaction, then commit it and start new transactions.
--
Hallvard