Re: Default isolation_level for sqlite3.connect?
David Raymond <[email protected]>
| Newsgroups | gmane.comp.db.sqlite.general |
|---|---|
| Message-ID | <VI1PR07MB60291D19C6521ECBA202085987040@VI1PR07MB6029.eurprd07.prod.outlook.com> |
https://docs.python.org/3.8/library/sqlite3.html#sqlite3-controlling-transactions "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." https://www.sqlite.org/lang_transaction.html So basically if you explicitly specify one it will issue either a "begin deferred;", "begin immediate;", or "begin exclusive;", and if you don't specify one it issues a plain "begin;" -----Original Message----- From: sqlite-users <[email protected]> On Behalf Of Peng Yu Sent: Thursday, January 30, 2020 10:59 AM To: SQLite mailing list <[email protected]> Subject: [sqlite] Default isolation_level for sqlite3.connect? Hi, I don't see what is the default isolation_level here. Is it None? Thanks. https://docs.python.org/3/library/sqlite3.html#module-functions-and-constants sqlite3.connect(database[, timeout, detect_types, isolation_level, check_same_thread, factory, cached_statements, uri])¶ -- Regards, Peng _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users