21 messages in com.mysql.lists.perlRe: [GENERAL] undefined behaviour for...
FromSent OnAttachments
Tyler MacDonald14 Nov 2005 23:00 
Jochen Wiedmann14 Nov 2005 23:16 
Tyler MacDonald14 Nov 2005 23:41 
Jochen Wiedmann14 Nov 2005 23:51 
Tyler MacDonald15 Nov 2005 00:22 
Jochen Wiedmann15 Nov 2005 00:32 
Tyler MacDonald15 Nov 2005 00:45 
Tyler MacDonald15 Nov 2005 00:57 
Jochen Wiedmann15 Nov 2005 00:59 
Tim Bunce15 Nov 2005 05:20 
Tyler MacDonald29 Nov 2005 10:49 
Tim Bunce29 Nov 2005 11:43 
Andrew Sullivan30 Nov 2005 13:18 
Tyler MacDonald30 Nov 2005 13:31 
Jaime Casanova30 Nov 2005 13:44 
Michael Fuhr30 Nov 2005 13:57 
Tyler MacDonald30 Nov 2005 14:33 
Tim Bunce30 Nov 2005 15:35 
Jochen Wiedmann30 Nov 2005 21:04 
Andrew Sullivan01 Dec 2005 04:45 
Michael Fuhr01 Dec 2005 10:21 
Subject:Re: [GENERAL] undefined behaviour for sub-transactions?
From:Tyler MacDonald (tyl@yi.org)
Date:11/30/2005 02:33:49 PM
List:com.mysql.lists.perl

Jaime Casanova <syst@gmail.com> wrote:

Either way the end result is that some database drivers poison a transaction if there's any error, others are selective about which errors are fatal and which are not, and still others just don't care at all.

that is a mis-conception... a transaction *must* be atomic (all or nothing)... the reason some databases act that bad is because they don't support savepoints, and because postgres does it doesn't need that awfulness...

OK, maybe I should have s/poison/behave properly with/. :-)

- Tyler