Michael Ströder michael@stroeder.com schrieb am 02.08.2021 um 11:22 in
Nachricht 41eb0de3-d648-6ecb-6a2d-e03decb6bf03@stroeder.com:
On 8/2/21 11:00 AM, Ulrich Windl wrote:
Michael Ströder michael@stroeder.com schrieb am 02.08.2021 um 09:57
in
Nachricht 59abdf98-65a4-5bb4-fffb-f1384969772a@stroeder.com:
On 8/2/21 8:06 AM, Ulrich Windl wrote:
> Michael Ströder michael@stroeder.com schrieb am 31.07.2021 um 18:05
in
Nachricht 60ec1d1e-a2be-95a2-c9c4-24ecd9b4f58c@stroeder.com:
As far as I understood the MDB disk format changed. So the MDB files have to be re-created (either by simply removing/replicating or slapcat/slapadd). Right?
AFAIK; Sleepycat DB could do that conversion on the fly.
AFAICS the DB layout is application-specific. So there was also no way to let Berkeley-DB do this "on the fly".
Of course Berkely DB cannot upgrade the MDB database; I was talking about the layout versions of Berkeley DB.
I did not misunderstand you. I meant that Berkeley-DB could not do automagic upgrades of its files in case the application-specific format changes.
IIRC in former times with back-bdb and back-hdb there was also sometimes the need to reload BDB files because the slapd-specific layout changed.
Admittedly I never had or needed those. I only noticed changes of hash functions, and those did not need manual intervention.
Ciao, Michael.