> SAVEPOINTs is the way PostgreSQL and MySQL do it, as well as many > other SQL database engines. We want to maximize compatibility. > > We have discussed letting you used named transactions using BEGIN. We > might add that in the future. But for now, SAVEPOINT seems to be the > safest way to do things - and the least likely to cause compatibility > problems. >
Makes perfect sense. I'm still hoping for nested transactions sometime soon, hope the savepoint code makes it easier ;) ..pretty please?.. - Sherief _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
