Jaime Casanova <systemguards@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
