I already sent an email to sqlabs about this, but I get an error when trying to issue a savepoint using CubeSQL. Its strange that ‘savepoint’ does not appear in the CubeSQL commands manual.
SO… I may have to replace the savepoint statement… If this is the case, how do you guys suggest dealing with this ? I want to avoid the regular rollback…this is a very specific situation which at the end of a long process the user may cancel and a rollback may be needed but I don’t want to keep a transaction open for such long time… Ideas ?
@Roman Varas
SAVEPOINTS are disabled inside cubeSQL because it needs to guarantee data integrity in a multi-threading environment.
SAVEPOINTS work like a stack under the hood so if two or more clients uses SAVEPOINT/ROLLBACK when it could happen that transaction for another client be rollback too.