Long running processes and commit writing to disk

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

From: Shaozhong SHI <shishaozhong@gmail.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

On 4/8/22 10:52, Mike Sofen wrote:

*From:* Shaozhong SHI <shishaozhong@gmail.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.)

On 4/8/22 11:39, Shaozhong SHI wrote:

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?

That would of course depend on how often you begin and commit transactions.

--
Angular momentum makes the world go 'round.