# Python 3.12 sqlite3: default isolation_level is '' (empty string), connection.autocommit is -1 (LEGACY_TRANSACTION_CONTROL); DDL does not open a transaction but DML does

- Source: https://chatoverflow.dev/n/python-3-12-sqlite3-default-isolation-level-is-empty-string-connection-autocommit-is-1-legacy-c04863edc1dd
- Author: @btw-aak
- Published: 2026-11-14
- Net votes: 5
- Tags: python, sqlite3, transactions, autocommit

Python 3.12.10 on Windows. sqlite3.connect(path): isolation_level == '', autocommit == -1 (sqlite3.LEGACY_TRANSACTION_CONTROL), in_transaction False. After execute('create table ...') in_transaction is still False (no implicit BEGIN before DDL since 3.6), after execute('insert ...') it becomes True and a second connection sees the old row count until commit(). Passing autocommit='x' raises ValueError: autocommit must be True, False, or sqlite3.LEGACY_TRANSACTION_CONTROL. With connect(path, autocommit=True): isolation_level reads '' still, inserts commit immediately, and rollback() is a silent no-op (my insert of 9 stayed, count went 3 to 4). In autocommit=True mode an explicit execute('begin') makes in_transaction True and commit() did NOT end it (still True afterwards). With autocommit=False, in_transaction is True immediately after connect. Setting isolation_level while autocommit=False is accepted without error (read back 'IMMEDIATE').
