After discussion with Victor by using DM, I decided to provide
high-level API instead of low-level APIs.
- gdbm.open(filename, snapshots=(foo, bar))
will do everything at once.
Regards,
Dong-hee
2022년 1월 21일 (금) 오후 12:52, Dong-hee Na 님이 작성:
> For more readable code:
>
For more readable code:
https://gist.github.com/corona10/d4fe0b6367ea6865e37b4369a7d60912
2022년 1월 21일 (금) 오후 12:50, Dong-hee Na 님이 작성:
> I exchanged a mail for investigating details.
>
> Before getting started, please remind the following fact.
> - The latest snapshot is always valid, even if
I exchanged a mail for investigating details.
Before getting started, please remind the following fact.
- The latest snapshot is always valid, even if corruption has not occurred.
> Why is a separated script needed? / A single script cannot automatically
detect a corrupted database and load the
How does someone know if a database is corrupted? Why is a separated
script needed?
A single script cannot automatically detect a corrupted database and
load the latest snapshot?
How is different from simply copying the whole database file?
Victor
--
Night gathers, and now my watch begins. It
Hello Victor :)
> Do you ask us our opinion on the Python API that you propose? Or if
the whole feature is worth it?
Latter must be done first :)
> Can you please show me a short full example opening a database with
automatic snapshot recovery (with your proposed API)?
The following codes are
Hi Dong-hee,
Can you please show me a short full example opening a database with
automatic snapshop recovery (with your proposed API)?
Do you ask us our opinion on the Python API that you propose? Or if
the whole feature is worth it?
Victor
On Tue, Jan 18, 2022 at 2:41 AM Dong-hee Na wrote:
>
