On Jan 2, 2009, at 10:56 AM, Igor Tandetnik wrote: > "D. Richard Hipp" <[email protected]> wrote > in message news:[email protected] >> Preliminary documentation can be seen at >> http://www.sqlite.org/draft/lang_savepoint.html > > Describing the effects of RELEASE statement as committing a savepoint > may be somewhat misleading. How can one commit some changes in the > middle of a transaction? What happens to those committed changes if > the > entire transaction is rolled back later?
I have attempted to clarify the documentation. Please let me know if it makes better sense now. http://www.sqlite.org/draft/lang_savepoint.html > > > At least I, personally, was thoroughly confused by it, and got > un-confused only after reading Postgress' documentation which > describes > the effects of RELEASE statement as "destroys a savepoint, makes it > unavalilable for rollback, but has no other user visible behavior". > Basically, as I understand it, RELEASE simply makes it as if the > SAVEPOINT statement it names (and all subsequent ones) never > happened - > except when the SAVEPOINT in question initiated the transaction in the > first place (which, as I understand, is illegal in Postgress), in > which > case RELEASE is the same as COMMIT. > > Igor Tandetnik > > > > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
