Timeline for DB transactions necessity
Current License: CC BY-SA 4.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 11, 2021 at 6:00 | history | tweeted | twitter.com/StackSoftEng/status/1369890838461943808 | ||
| Mar 9, 2021 at 22:33 | answer | added | sakisk | timeline score: 1 | |
| Mar 7, 2021 at 19:58 | comment | added | Filip Milovanović | Also, transactions are, how shall I put it, extremely highly recommended if you're ever messing around with a production database :) - see: this and this | |
| Mar 7, 2021 at 9:18 | answer | added | gnasher729 | timeline score: 2 | |
| S Mar 7, 2021 at 6:35 | history | suggested | mentallurg | CC BY-SA 4.0 |
"consistent" better reflects one of the transaction aspects than "coherent"
|
| Mar 7, 2021 at 6:35 | vote | accept | Petro Ivanenko | ||
| Mar 7, 2021 at 1:42 | review | Suggested edits | |||
| S Mar 7, 2021 at 6:35 | |||||
| Mar 7, 2021 at 0:33 | comment | added | Zach Lipton | Do you use a particular ORM or application framework? Many modern frameworks will automatically use transactions (often with default behavior around rolling things back if there are errors), so it's worth knowing how the frameworks you use work and how to use them to control transactions where necessary. If you mention what you use, someone can help identify resources on that. | |
| Mar 6, 2021 at 23:14 | history | became hot network question | |||
| Mar 6, 2021 at 18:56 | review | Close votes | |||
| Mar 11, 2021 at 3:05 | |||||
| Mar 6, 2021 at 15:49 | answer | added | Andrew Henle | timeline score: 8 | |
| Mar 6, 2021 at 15:46 | answer | added | FrustratedWithFormsDesigner | timeline score: 11 | |
| Mar 6, 2021 at 15:45 | comment | added | Andrew Henle | As @Steve said, transactions are used in systems designed for reliability in all cases. As for why you don't see them in use more often? I refer you to Sturgeon's Law. | |
| Mar 6, 2021 at 15:42 | comment | added | Steve | Transactions are necessary whenever there is concurrent access to the database - so in multi-user or multi-thread contexts. In SQL, each 'statement' is supposed to be transactionally consistent by default. Where there are multiple statements, it is possible to explicitly declare that these should occur as a single transaction. If you know nothing about transactions, then the best place to start would be to read some information online about transactions, such as: docs.oracle.com/cd/B19306_01/server.102/b14220/transact.htm | |
| Mar 6, 2021 at 15:18 | review | First posts | |||
| Mar 6, 2021 at 16:35 | |||||
| Mar 6, 2021 at 15:14 | history | asked | Petro Ivanenko | CC BY-SA 4.0 |