Transactions tests failing about monetdbe-python HOT 5 CLOSED

which functions do you expect?

from monetdbe-python.

What are the options? the usual commit, rollback, start transaction?

from monetdbe-python.

from monetdbe-python.

Recap from the documentation.
The Python/SQLite semantics are : auto-commit, deferred, immediate, exclusive.
The underlying SQLite library is based on auto-commit.autocommit mode means that statements that modify the database take effect immediately. A BEGIN or SAVEPOINT statement disables auto-commit mode, and a COMMIT, a ROLLBACK, or a RELEASE that ends the outermost transaction, turns auto-commit mode back on.
The Python sqlite3 module by default issues a BEGIN statement implicitly before a Data Modification Language (DML) statement (i.e. INSERT/UPDATE/DELETE/REPLACE).

You can control which kind of BEGIN statements sqlite3 implicitly executes via the isolation_level parameter to the connect() call, or via the isolation_level property of connections. If you specify no isolation_level, a plain BEGIN is used, which is equivalent to specifying DEFERRED. Other possible values are IMMEDIATE and EXCLUSIVE.

You can disable the sqlite3 module’s implicit transaction management by setting isolation_level to None. This will leave the underlying sqlite3 library operating in autocommit mode. You can then completely control the transaction state by explicitly issuing BEGIN, ROLLBACK, SAVEPOINT, and RELEASE statements in your code.

Proposed MonetDBe rules

• all statements passed through execute() follow the auto-commit semantics
• all statements passed executescript(), and executemany() are considered compound transactions, automatically wrapped with a BEGIN TRANSACTION and finalized with a COMMIT. We don;t check on mis-use (nested BEGIN) within the sequence.

from monetdbe-python.

The SQLite transactions test suite passes now

from monetdbe-python.