Re: Queuing DBI transactions

I'm surprised no one's suggested this yet -- once the change has been submitted to the database without error, try to get the new or updated data back out. If you manage that OK, you can consider that query or command successful, and shift it off the stack.

Alex / talexb / Toronto

"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

Comment on Re: Queuing DBI transactions

Replies are listed 'Best First'.
Re^2: Queuing DBI transactions by oha (Friar) on Oct 05, 2007 at 14:55 UTC
I expect that if the query has been submitted without error, all went fine. Checking again should be not only a waste, but also risky: if someone is fast enough (think like a race condition) the data could have been changed again unless highly isolated (TX_SERIALIZABLE). Also, it's not always possible to know what is the correct data: `update counters set ct=ct+1` Oha	[reply] [d/l]
Re^3: Queuing DBI transactions by talexb (Chancellor) on Oct 05, 2007 at 14:57 UTC
Very good points. Well, it was just a suggestion. Alex / talexb / Toronto "Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds	[reply]