Wait, wait, wait... you mean I can't just drop the user and expect the event to vanish into thin air? Option B it is, my friends. Looks like the database gods have a sense of humor today.
Ah, the classic 'drop the user and see what happens' approach. I'm going to have to go with option B on this one. Gotta love it when the database gets a little bit of an attitude adjustment.
Option C seems a bit too convenient, don't you think? I doubt the system would just drop the event without any notification. I'm leaning towards option B.
Well, this is an interesting scenario. I'm gonna go with option D. If the user is dropped, the event won't be scheduled in the first place, so it won't execute.
Hmm, this is a tricky one. I think option B is the correct answer. Dropping the user will prevent the event from executing, but the system should log an error.
Sue
2 months agoHarley
2 days agoNettie
3 days agoAlex
6 days agoOdette
2 months agoMarcos
2 months agoRuby
1 months agoFredric
1 months agoRolande
1 months agoShaunna
2 months agoGilberto
2 months agoVon
2 days agoCarolynn
3 days agoJamey
12 days agoAlecia
15 days agoTammy
19 days agoJustine
1 months agoIluminada
2 months agoValene
2 months agoEarleen
2 months agoColetta
2 months agoEarleen
3 months ago