Re: [sqlite] Does sqlite really support transaction?

[John LeSueur]

Thomas Briggs wrote:
  A transaction is a way to make a group of things that happens atomic,
but an SQL statement that generates an error doesn't really make
anything happen, so it has no impact on the transaction itself or any of
the other actions within it.  That kinda the whole point, in a way - one
statement failing doesn't make the other immediately invalid.  The
decision to roll back the entire transaction when any statement within
it fails is a user or developer decision, however, not a function of
transactions - you can roll it back, invalidating the other actions, or
you can fix it and re-execute it, leaving the other actions intact.
 

I don't disagree with this, but
  This isn't an SQLite thing either... All databases work this way, as
far as I'm aware.
 

Postgres refuses to process any further sql statements in a transaction 
after an error occurs with
one of the sql statements.

  -Tom
John