Visitar URL original
bpo-29121: Remove outdated documentation about transactions by berkerpeksag · Pull Request #313 · python/cpython · GitHub
Skip to content

bpo-29121: Remove outdated documentation about transactions #313

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
berkerpeksag merged 2 commits into from
Feb 26, 2017
Merged

bpo-29121: Remove outdated documentation about transactions #313

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d8d865d
bpo-29121: Remove outdated documentation about transactions
berkerpeksag Feb 26, 2017
0968cf5
Keep in_transaction documentation around
berkerpeksag Feb 26, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
bpo-29121: Remove outdated documentation about transactions 
Patch by Aviv Palivoda.
  • Loading branch information
@berkerpeksag
berkerpeksag committed Feb 26, 2017
commit d8d865da89990272ee784b2e04f1596baba65583
8 changes: 0 additions & 8 deletions Doc/library/sqlite3.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -927,14 +927,6 @@ By default, the :mod:`sqlite3` module opens transactions implicitly before a
Data Modification Language (DML) statement (i.e.
``INSERT``/``UPDATE``/``DELETE``/``REPLACE``).

So if you are within a transaction and issue a command like ``CREATE TABLE
...``, ``VACUUM``, ``PRAGMA``, the :mod:`sqlite3` module will commit implicitly
before executing that command. There are two reasons for doing that. The first
is that some of these commands don't work within transactions. The other reason
is that sqlite3 needs to keep track of the transaction state (if a transaction
is active or not). The current transaction state is exposed through the
:attr:`Connection.in_transaction` attribute of the connection object.

You can control which kind of ``BEGIN`` statements sqlite3 implicitly executes
(or none at all) via the *isolation_level* parameter to the :func:`connect`
call, or via the :attr:`isolation_level` property of connections.
Expand Down