@@ -292,7 +292,6 @@ Module functions
292
292
By default (``0 ``), type detection is disabled.
293
293
294
294
:param isolation_level:
295
- Control legacy transaction handling behaviour.
296
295
See :attr: `Connection.isolation_level ` and
297
296
:ref: `sqlite3-transaction-control-isolation-level ` for more information.
298
297
Can be ``"DEFERRED" `` (default), ``"EXCLUSIVE" `` or ``"IMMEDIATE" ``;
@@ -326,11 +325,8 @@ Module functions
326
325
enabling various :ref: `sqlite3-uri-tricks `.
327
326
328
327
:param autocommit:
329
- Control :pep: `249 ` transaction handling behaviour.
330
328
See :attr: `Connection.autocommit ` and
331
329
:ref: `sqlite3-transaction-control-autocommit ` for more information.
332
- If ``False ``, a new transaction is implicitly opened
333
- when the :class: `Connection ` is created.
334
330
*autocommit * currently defaults to
335
331
:data: `~sqlite3.LEGACY_TRANSACTION_CONTROL `.
336
332
The default will change to ``False `` in a future Python release.
@@ -2472,9 +2468,9 @@ which implies :pep:`249`-compliant transaction control.
2472
2468
This means:
2473
2469
2474
2470
* :mod: `!sqlite3 ` ensures that a transaction is always open,
2475
- so :meth: `Connection.commit ` and :meth: `Connection.rollback `
2476
- will implicitly open a new transaction immediately after closing
2477
- the pending one.
2471
+ so :func: ` connect `, : meth: `Connection.commit `, and :meth: `Connection.rollback `
2472
+ will implicitly open a new transaction
2473
+ (immediately after closing the pending one, for the latter two) .
2478
2474
:mod: `!sqlite3 ` uses ``BEGIN DEFERRED `` statements when opening transactions.
2479
2475
* Transactions should be committed explicitly using :meth: `!commit `.
2480
2476
* Transactions should be rolled back explicitly using :meth: `!rollback `.
0 commit comments