Suggestions on mechanism or existing code - maintain persistence of file download history
On Thu, Jan 30, 2020 at 7:41 PM R.Wieser <address at not.available> wrote:
> A database /sounds/ good, but what happens when you ctrl-c outof a
> non-atomic operation ? How do you fix that ? IOW: Databases can be
> corrupted for pretty-much the same reason as for a simple datafile (but with
> much worse consequences).
Proper databases don't HAVE non-atomic operations. That's kinda their job.
Unless you mean that there's a non-atomic operation that consists of
placing some kind of "claim" on a URL and then going and downloading
it, and finally reporting completion, but that's easily enough handled
by simply ensuring that there are no downloader processes running, and
then clear any incomplete claims. But that's still not corrupting the
Maybe you've only ever worked with half-baked apologies for database systems?