My understanding is that a SQL database server that supports stored procedures will behave that way in a stored procedure (same is true for triggers). But there is nothing to stop a command from executing just because the previous command failed. If one is 'faking' stored procedures by executing commands with the command isqlite program, the commands can just keep executing.
> -----Original Message----- > From: John Buck [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 12, 2005 12:33 PM > To: sqlite-users@sqlite.org > Subject: RE: [sqlite] Does sqlite really support transaction? > > MySql works like you described.. Frankly im surprised > Postgres doesn't . > Id imagine there must be a "continue trnasaction" command or > something. > > -- > JB > > -----Original Message----- > From: Thomas Briggs [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 12, 2005 12:25 PM > To: sqlite-users@sqlite.org > Subject: RE: [sqlite] Does sqlite really support transaction? > > > > > 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. > > Heh. I should have said that "all databases with which I > am familiar work this way". Postgres is obviously not one of > the databases with which I'm familiar. :) I did try MS SQL > Server, Oracle and DB2 and they all function this way. > Didn't try MySQL though... Hrm. > > -Tom > >
