Re: Long running processes and commit writing to disk

On 4/8/22 10:52, Mike Sofen wrote:
>
> *From:* Shaozhong SHI <shishaozhong(at)gmail(dot)com> *Sent:* Friday, April
> 08, 2022 9:39 AM
>
> When long running processes got disrupted, one may not see any
> expected result.
>
> How to make sure that the result of each operation is saved to disk in
> a loop?
>
> Regards,
>
> David
>
> Simple:  don’t use a database – you’re asking to violate ACID.
>
> A database’s power comes from set-based operations.  You’re asking to
> do single row operations.  Use a spreadsheet...or a plain text file
> and treat it like a log.
>
> Mike
>
Or commit every loop (perhaps every N loops, depending on how much
you're prepared to re-do.)