Suggestions on mechanism or existing code - maintain persistence of file download history
On Fri, Jan 31, 2020 at 4:11 AM R.Wieser <address at not.available> wrote:
> But, do you remember what the OP said ?
> want to download these as a 'background task'. ... you can CTRL-C out,
> Why now do I think that, when such a backgroud process is forgotten and the
> 'puter switched off, the file, database or otherwise, could easily get
> damaged ? And that a ctrl-c at the wrong moment could cause the same if the
> cleanup (of the database, which could easily still be, in its own thread,
> busy housekeeping) isn't done correctly.
> Also, have you /never/ encountered a corrupted file, database or otherwise ?
> You must not have done much with 'puters at all ...
On the contrary, I grew up with IBM DB2 and then PostgreSQL, both of
which are actually resilient against power failures. I've also
recovered data from crashed hard drives. So, yeah, I think I know what
I'm talking about. Sorry.
Have a nice day. Enjoy dealing with corruption in places where
ordinary best-practices and basic tutorials can prevent it from ever