Timeline for Avoiding modification of multiple aggregate roots in one transaction
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 17, 2023 at 12:58 | history | edited | Doc Brown | CC BY-SA 4.0 |
added 136 characters in body
|
| Feb 16, 2023 at 20:45 | comment | added | Doc Brown | @deamon: yep, in case you have the resources to implement this, you could also determine the specific tasks causing a conflict, highlight them or display differnt kind of warning signs depending on the kind of conflict. | |
| Feb 16, 2023 at 15:15 | comment | added | deamon | I like your approach of modelling conflicts explicitly. I didn't want moving only some of the affected tasks, because it might be hard to see what has been moved and why, if the root cause might not have been performed due to a conflict. But if everything would be moved regardless of conflicts, everything would be fine, as long as conflicts are obvious to the user. | |
| Feb 16, 2023 at 14:52 | history | edited | Doc Brown | CC BY-SA 4.0 |
added 382 characters in body
|
| Feb 16, 2023 at 14:47 | history | edited | Doc Brown | CC BY-SA 4.0 |
added 382 characters in body
|
| Feb 16, 2023 at 14:32 | history | answered | Doc Brown | CC BY-SA 4.0 |