2260
Points
Questions
0
Answers
170
-
- 1932 views
- 3 answers
- 0 votes
-
- 1253 views
- 1 answers
- 0 votes
-
- 1481 views
- 3 answers
- 0 votes
-
- 1295 views
- 1 answers
- 0 votes
-
- 2891 views
- 4 answers
- 0 votes
-
- 1752 views
- 2 answers
- 0 votes
-
- 3433 views
- 2 answers
- 0 votes
-
This answer accepted by CoteC1. on May 7, 2024 Earned 15 points.
- 1465 views
- 1 answers
- 0 votes
-
Typically, you want to do your updates in a post event. All sorts of things can go wrong when modifying in a pre-event, including an error that the object has been modified. Validate in pre-event but update in post-event.
That you are updating the table that you are triggering on means you need to be sure you dont get into an infinite loop.. there is a configurable thread limit to keep that from happening but you dont want to count on it.
- 1459 views
- 1 answers
- 0 votes
-
Doesn’t really matter. The scheduler is background task anyway.
Where synchronous vs asynchronous matters are events that the user triggers. Synchronous holds the user up while processing and can show the user a message afterwards.
This answer accepted by Matt Paulhus. on May 7, 2024 Earned 15 points.
- 1610 views
- 2 answers
- 0 votes