In response to "Phoenix Kiula" <phoenix.kiula@xxxxxxxxx>: > > If you issue a BEGIN then nothing gets committed until you issue a COMMIT. If > > anything happens in the meantime then everything you've done since the BEGIN > > disappears. > > There are some cases where I would like to bunch queries into a > transaction purely for speed purposes, but they're not interdependent > for integrity. E.g., > > BEGIN TRANSACTION; > UPDATE1; > UPDATE2; > UPDATE3; > COMMIT; > > If UPDATE2 fails because it, say, violates a foreign key constraint, > then so be it. I want UPDATE3 to go ahead. Is this not possible, or is > there an option I can use to do these kind of independent-query > transactions? That's not possible, by design. However, your application could keep track of which queries have run, and if one fails, start the transaction over without the failing query. But the rule is, if any query within the transaction errors, then all queries within the transaction are rolled back. -- Bill Moran http://www.potentialtech.com ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
