-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Miguel Angel Latorre D�az wrote:
|Kenneth: |Thanks, I see your point, but that was just an example, put an "insert" or |"delete" command instead of the "create table", and that row would be |"inserted" or "deleted" without executing a rollback due to the SQL error. |I haven't tested though. But perhaps, as you said, the create table makes |its own transaction, but that shouldn't bother the rest of statements |included in the explicit "outer transaction". Should it? | |I might be missing something but any number of statements surrounded by a |begin/commit should all be done or undone. | | | I don't know if it should be considered a bug or a feature, but what happens is that it works as expected if you issued the all the commands in a sentence (that is all in the same line). When they are separate, sqlite considers it is your responsibility to check the error returned, as the rollback has occurred already. That case also baffled me the first time I noticed it.
Regards, ~Nuno Lucas
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFA3LKo24S9OitwspoRAiPcAJ4l0dvzT3JDLw+p08rTbxWijRbbVwCfSdUJ dnd7Z9K+0C/iQ64Ph5RZovU= =3Nwf -----END PGP SIGNATURE-----
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
