Thread: Long running processes and commit writing to disk
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.)@font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face {font-family:Consolas; panose-1:2 11 6 9 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; font-size:11.0pt; font-family:"Calibri",sans-serif;}span.EmailStyle24 {mso-style-type:personal-reply; font-family:"Calibri",sans-serif; color:windowtext;}.MsoChpDefault {mso-style-type:export-only; font-family:"Calibri",sans-serif;}div.WordSection1 {page:WordSection1;} 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