Timeline for Separating Business logic from DB-logic with transactions
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 19, 2020 at 9:49 | history | edited | Laiv | CC BY-SA 4.0 | added 1 character in body |
| May 19, 2020 at 9:25 | history | edited | Laiv | CC BY-SA 4.0 | added 1 character in body |
| May 19, 2020 at 9:22 | comment | added | Laiv | The simplest implementation is, as u say, aborting the transaction. For example, you could rise a business exception. Within the UoW, you might decide not to begin the transaction until all the policies (file size constraint) are checked so that in case of aborting the unit of work, there's no need change to rollback in the data source. | |
| May 19, 2020 at 9:05 | history | edited | Laiv | CC BY-SA 4.0 | deleted 98 characters in body |
| May 9, 2020 at 16:55 | comment | added | brainoverflow98 | What can I do if I have to check a business rule inside the transaction? Like if file size greater than 15mb abort transaction. | |
| Apr 22, 2017 at 8:56 | history | edited | Laiv | CC BY-SA 3.0 | deleted 1 character in body |
| Apr 21, 2017 at 10:19 | history | edited | Laiv | CC BY-SA 3.0 | added 2 characters in body; added 3 characters in body |
| Nov 12, 2016 at 15:09 | history | edited | Laiv | CC BY-SA 3.0 | added 1 character in body |
| Oct 7, 2016 at 5:04 | history | edited | Laiv | CC BY-SA 3.0 | deleted 50 characters in body |
| Oct 6, 2016 at 10:34 | history | edited | Doc Brown | CC BY-SA 3.0 | added 4 characters in body |
| Oct 5, 2016 at 18:13 | history | edited | Laiv | CC BY-SA 3.0 | added 10 characters in body |
| Oct 5, 2016 at 13:05 | history | answered | Laiv | CC BY-SA 3.0 |