Hello, igniters. We previously discussed savepoints[1] for transactions in Ignite, but that discussion focused only on the KV‑API behavior. Now transactions are also available for SQL, with an API that looks like this:
INSERT INTO table1 VALUES (1); SAVEPOINT my_savepoint; INSERT INTO table1 VALUES (2); ROLLBACK TO SAVEPOINT my_savepoint; INSERT INTO table1 VALUES (3); COMMIT; Since the SQL API doesn’t have an additional parameter for overwriting a savepoint (unlike the KV‑API, which does have such a parameter), I propose that the default behavior should be to overwrite the old savepoint.| This behavior is adopted by most major databases (Oracle, PostgreSQL, SQL Server). Are there any concerns with this approach? [1]: http://apache-ignite-developers-legacy-mail-archive.111.s1.nabble.com/TX-savepoints-tt12041.html -- Vladislav Pyatkov
