Skip to content
Merged
Changes from 21 commits
Commits
Show all changes
34 commits
Select commit Hold shift + click to select a range
974022c
gh-95271: Improve sqlite3 tutorial wording
erlend-aasland Aug 6, 2022
f21d777
Fix rest syntax
erlend-aasland Aug 6, 2022
4231b75
Improve count query comment
erlend-aasland Aug 6, 2022
e08ca43
SQL commands => SQL queries
erlend-aasland Aug 6, 2022
f9a5664
Improve transaction control paragraph
erlend-aasland Aug 6, 2022
484f341
Be more to the point
erlend-aasland Aug 6, 2022
ae0969f
Fix ref
erlend-aasland Aug 6, 2022
d1d11f4
Missing 'the'; even more to the point
erlend-aasland Aug 6, 2022
9870036
Be more accurate
erlend-aasland Aug 6, 2022
431dcb5
Remove unneeded comments; the instructions don't need to be reiterated
erlend-aasland Aug 6, 2022
ac7d870
Merge branch 'main' into sqlite-tutorial/improve-wording
erlend-aasland Aug 8, 2022
f4b66ac
Address Ezio's initial review
erlend-aasland Aug 8, 2022
09ac89d
Address second round of reviews from both Ezio and CAM
erlend-aasland Aug 9, 2022
cbfb325
Use Python version history as example database
erlend-aasland Aug 9, 2022
deb199c
move sphinx comment; it creates havoc
erlend-aasland Aug 9, 2022
d54ff8d
Address a new round of reviews from CAM
erlend-aasland Aug 9, 2022
e778012
Update the example, be more explicit
erlend-aasland Aug 10, 2022
e9e1ffa
Address review comments
erlend-aasland Aug 11, 2022
f60e3a2
Missing blank line below Sphinx comment
erlend-aasland Aug 11, 2022
5d03a4e
Address reviews from 2022-08-11
erlend-aasland Aug 12, 2022
3ec75d1
Tone: use second person singular more often
erlend-aasland Aug 12, 2022
84d798f
Adressing the last rounds of comments from CAM, Daniele, and Ezio
erlend-aasland Aug 14, 2022
d09d9f6
you will need to => you need to
erlend-aasland Aug 14, 2022
d6f4775
Address more review comments
erlend-aasland Aug 14, 2022
b46942b
Address CAM's last round of comments; use first person plural
erlend-aasland Aug 15, 2022
4a51e1e
Typos
erlend-aasland Aug 15, 2022
92fa693
Nits and a link
erlend-aasland Aug 15, 2022
d40c2a7
Adjust 'non-existent' example; adjust final query; sort links
erlend-aasland Aug 16, 2022
d2c3968
Rewrite an 'as expected'
erlend-aasland Aug 16, 2022
32a19e9
Fix string format anti-pattern
erlend-aasland Aug 17, 2022
dd38587
Clarify how we verify that the table has been created
Aug 18, 2022
f41be9b
Update Doc/library/sqlite3.rst
Aug 18, 2022
0e0398d
Update Doc/library/sqlite3.rst
Aug 18, 2022
cb41c49
Revert "Update Doc/library/sqlite3.rst"
erlend-aasland Aug 18, 2022
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
185 changes: 135 additions & 50 deletions Doc/library/sqlite3.rst
Original file line number Diff line number Diff line change
Expand Up @@ -47,85 +47,170 @@ This document includes four main sections:
PEP written by Marc-André Lemburg.


.. We use the following practises for SQL code:
- UPPERCASE for keywords
- snake_case for schema
- single quotes for string literals
- singular for table names
- if needed, use double quotes for table and column names

.. _sqlite3-tutorial:

Tutorial
--------

To use the module, start by creating a :class:`Connection` object that
represents the database. Here the data will be stored in the
:file:`example.db` file::
In this tutorial, you will learn the basics of the :mod:`!sqlite3` API
by creating a database of Monty Python movies.
It assumes a fundamental understanding of database concepts,
including `cursors`_ and `transactions`_.

First, you'll need to create a new database to hold the movie data
and open a database connection to allow :mod:`!sqlite3` to work with it.
Call the :func:`sqlite3.connect` function to
to create a connection to a database :file:`tutorial.db`
in the current working directory,
implicitly creating it if it does not exist::

import sqlite3
con = sqlite3.connect('example.db')
con = sqlite3.connect("tutorial.db")

The special path name ``:memory:`` can be provided to create a temporary
database in RAM.
The returned :class:`Connection` object ``con``
represents the connection to the database.

Once a :class:`Connection` has been established, create a :class:`Cursor` object
and call its :meth:`~Cursor.execute` method to perform SQL commands::
In order to execute SQL statements and fetch results from SQL queries,
you'll use a database cursor.
Call :meth:`con.cursor() <Connection.cursor>` to create the :class:`Cursor`::

cur = con.cursor()

# Create table
cur.execute('''CREATE TABLE stocks
(date text, trans text, symbol text, qty real, price real)''')

# Insert a row of data
cur.execute("INSERT INTO stocks VALUES ('2006-01-05','BUY','RHAT',100,35.14)")
Now you'll create a database table ``movie`` with columns for title,
release year, and review score.
For simplicitly, just use column names in the table declaration:
thanks to the `flexible typing`_ feature of SQLite,
specifying the data types is optional.
Execute the ``CREATE TABLE`` statement
by calling :meth:`con.execute() <Cursor.execute>`::

cur.execute("CREATE TABLE movie(title, year, score)")

.. Ideally, we'd use sqlite_schema instead of sqlite_master below,
but earlier versions of SQLite do not recognise that variant.

You can verify that the new table has been created by querying
the ``sqlite_master`` table built-in to SQLite.
It should contain an entry for the ``movie`` table definition.
Execute that query by calling :meth:`cur.execute(...) <Cursor.execute>`,
store the result in a variable ``res``,
and call :meth:`res.fetchone() <Cursor.fetchone>` to fetch the first
(and only) row that was returned::

>>> res = cur.execute("SELECT name FROM sqlite_master")
>>> res.fetchone()
('movie',)

As expected, the query shows the table is now created
by returning a single :class:`tuple`: with the name of the table.
As an exercise, try querying ``sqlite_master``
for a non-existent table ``"abc"``::

>>> res = cur.execute("SELECT name FROM sqlite_master WHERE name='abc'")
>>> res.fetchone()
>>>

As expected, the query returns an empty result.

Now, you'll add two rows of data supplied as SQL literals
by executing an ``INSERT`` statement,
once again by calling :meth:`cur.execute(...) <Cursor.execute>`::

cur.execute("""
INSERT INTO movie VALUES
('Monty Python and the Holy Grail', 1975, 8.2),
('And Now for Something Completely Different', 1971, 7.5)
""")

The ``INSERT`` statement implicitly opens a transaction,
which needs to be committed before changes are saved in the database
(see :ref:`sqlite3-controlling-transactions` for details).
Call :meth:`con.commit() <Connection.commit>` on the connection object
to commit the transaction::

# Save (commit) the changes
con.commit()

# We can also close the connection if we are done with it.
# Just be sure any changes have been committed or they will be lost.
con.close()
You can verify that the data was inserted correctly
by executing a ``SELECT`` query.
Use the now-familiar :meth:`con.execute(...) <Cursor.execute>` to
store the result in ``res``,
and call :meth:`res.fetchall() <Cursor.fetchall>` to fetch all rows::

The saved data is persistent: it can be reloaded in a subsequent session even
after restarting the Python interpreter::

import sqlite3
con = sqlite3.connect('example.db')
cur = con.cursor()
>>> res = cur.execute("SELECT score FROM movie")
>>> res.fetchall()
[(8.2,), (7.5,)]

At this point, our database only contains one row::
The result is a :class:`list` of two :class:`!tuple`\s, one per row,
each containing a the ``score`` from the query.

>>> res = cur.execute('SELECT count(rowid) FROM stocks')
>>> print(res.fetchone())
(1,)
Now, you'll insert three more rows by calling
:meth:`cur.executemany(...) <Cursor.executemany>`::

The result is a one-item :class:`tuple`:
one row, with one column.
Now, let us insert three more rows of data,
using :meth:`~Cursor.executemany`::
data = [
("Monty Python Live at the Hollywood Bowl", 1982, 7.9),
("Monty Python's The Meaning of Life", 1983, 7.5),
("Monty Python's Life of Brian", 1979, 8.0),
]
cur.executemany("INSERT INTO movie VALUES(?, ?, ?)", data)
con.commit() # Remember to commit the transaction after executing INSERT.

>>> data = [
... ('2006-03-28', 'BUY', 'IBM', 1000, 45.0),
... ('2006-04-05', 'BUY', 'MSFT', 1000, 72.0),
... ('2006-04-06', 'SELL', 'IBM', 500, 53.0),
... ]
>>> cur.executemany('INSERT INTO stocks VALUES(?, ?, ?, ?, ?)', data)

Notice that we used ``?`` placeholders to bind *data* to the query.
Notice that ``?`` placeholders are used to bind ``data`` to the query.
Always use placeholders instead of :ref:`string formatting <tut-formatting>`
to bind Python values to SQL statements,
to avoid `SQL injection attacks`_.
See the :ref:`placeholders how-to <sqlite3-placeholders>` for more details.
to avoid `SQL injection attacks`_
(see :ref:`sqlite3-placeholders` for more details).

Then, retrieve the data by iterating over the result of a ``SELECT`` statement::
You can verify that the new rows were inserted
by executing a ``SELECT`` query,
this time iterating over the results of the query::

>>> for row in cur.execute('SELECT * FROM stocks ORDER BY price'):
>>> for row in cur.execute("SELECT year, title FROM movie ORDER BY year"):
... print(row)
(1971, "And Now for Something Completely Different")
(1975, "Monty Python and the Holy Grail")
(1979, "Monty Python's Life of Brian")
(1982, "Monty Python Live at the Hollywood Bowl")
(1983, "Monty Python's The Meaning of Life")

Each row is now a two-item :class:`tuple` of ``(year, title)``.

At last, you'll verify that the database has been written to disk by
calling :meth:`con.close() <Connection.close>`
to close the existing connection,
opening a new one, creating a new cursor,
then reusing the query from above to read from the database::

>>> con.close()
>>> con2 = sqlite3.connect("tutorial.db")
>>> cur2 = con2.cursor()
>>> for row in cur.execute("SELECT year, title FROM movie ORDER BY year"):
... print(row)
(1971, "And Now for Something Completely Different")
(1975, "Monty Python and the Holy Grail")
(1979, "Monty Python's Life of Brian")
(1982, "Monty Python Live at the Hollywood Bowl")
(1983, "Monty Python's The Meaning of Life")

('2006-01-05', 'BUY', 'RHAT', 100, 35.14)
('2006-03-28', 'BUY', 'IBM', 1000, 45.0)
('2006-04-06', 'SELL', 'IBM', 500, 53.0)
('2006-04-05', 'BUY', 'MSFT', 1000, 72.0)

You've now created an SQLite database using the :mod:`!sqlite3` module.
You've now created an SQLite database using the :mod:`!sqlite3` module,
inserted data and ran several SQL queries against it.

.. _SQL injection attacks: https://en.wikipedia.org/wiki/SQL_injection
.. _cursors: https://en.wikipedia.org/wiki/Cursor_(databases)
.. _flexible typing: https://www.sqlite.org/flextypegood.html
.. _transactions: https://en.wikipedia.org/wiki/Database_transaction
.. _sqlite_master: https://www.sqlite.org/schematab.html

.. seealso::

* :ref:`sqlite3-howtos` for details how to handle specific tasks.
* :ref:`sqlite3-explanation` for in-depth background on transaction control.

.. _sqlite3-reference:

Expand Down