At 04:53 PM 1/9/2003, you wrote:
Yeah, that's actually what I am doing, if the first fails, no need to
do the second one at all. The problem lies in that when the second query
fails, I need to roll back the first.
--
jon
mailto:[EMAIL PROTECTED]
There are a couple of ways to do this, but you
Yeah, that's actually what I am doing, if the first fails, no need to
do the second one at all. The problem lies in that when the second query
fails, I need to roll back the first.
--
jon
mailto:[EMAIL PROTECTED]
Thursday, January 9, 2003, 3:27:33 PM, you wrote:
MA According to Mastering
I have a set of db inserts involving two datasources
and if there is a failure in the 2nd datasource, I
need to roll back the transaction on the first datasource.
In a perfect world I could somehow hold up the first
transaction commit until the transaction on the second
datasource has
Samuel R. Neff wrote:
1. Use DB level transactions. Haven't done it with CF, but you should be
able to just put begin trans; commit; rollback inside a cfquery.
Isn't a connection returned to the pool after a closing cfquery tag when
not using transactions?
Jochem
4 matches
Mail list logo