Re: savepoint API

Kouber Saparev wrote:

I think it's ok like that, since you can only move "backwards" to savepoints, i.e. rollbacking. Once you rollback to a savepoint, you cannot access a savepoint which was defined after the current savepoint - which is of course normal, every statement after the savepoint should be "rolled back". So, providing an optional string parameter to rollback(), just like you've implemented it, sounds reasonable to me.

Actually I gotten some feedback from people offlist as well and so I decided to remove setSavepoint() and releaseSavepoint() and moved the code into beginTransaction() and commit(). regards, Lukas