1 :mod:`sqlite3` --- DB-API 2.0 interface for SQLite databases
2 ============================================================
5 :synopsis: A DB-API 2.0 implementation using SQLite 3.x.
6 .. sectionauthor:: Gerhard Häring <gh@ghaering.de>
11 SQLite is a C library that provides a lightweight disk-based database that
12 doesn't require a separate server process and allows accessing the database
13 using a nonstandard variant of the SQL query language. Some applications can use
14 SQLite for internal data storage. It's also possible to prototype an
15 application using SQLite and then port the code to a larger database such as
18 pysqlite was written by Gerhard Häring and provides a SQL interface compliant
19 with the DB-API 2.0 specification described by :pep:`249`.
21 To use the module, you must first create a :class:`Connection` object that
22 represents the database. Here the data will be stored in the
23 :file:`/tmp/example` file::
25 conn = sqlite3.connect('/tmp/example')
27 You can also supply the special name ``:memory:`` to create a database in RAM.
29 Once you have a :class:`Connection`, you can create a :class:`Cursor` object
30 and call its :meth:`execute` method to perform SQL commands::
35 c.execute('''create table stocks
36 (date text, trans text, symbol text,
37 qty real, price real)''')
39 # Insert a row of data
40 c.execute("""insert into stocks
41 values ('2006-01-05','BUY','RHAT',100,35.14)""")
43 # Save (commit) the changes
46 # We can also close the cursor if we are done with it
49 Usually your SQL operations will need to use values from Python variables. You
50 shouldn't assemble your query using Python's string operations because doing so
51 is insecure; it makes your program vulnerable to an SQL injection attack.
53 Instead, use the DB-API's parameter substitution. Put ``?`` as a placeholder
54 wherever you want to use a value, and then provide a tuple of values as the
55 second argument to the cursor's :meth:`execute` method. (Other database modules
56 may use a different placeholder, such as ``%s`` or ``:1``.) For example::
58 # Never do this -- insecure!
60 c.execute("... where symbol = '%s'" % symbol)
64 c.execute('select * from stocks where symbol=?', t)
67 for t in (('2006-03-28', 'BUY', 'IBM', 1000, 45.00),
68 ('2006-04-05', 'BUY', 'MSOFT', 1000, 72.00),
69 ('2006-04-06', 'SELL', 'IBM', 500, 53.00),
71 c.execute('insert into stocks values (?,?,?,?,?)', t)
73 To retrieve data after executing a SELECT statement, you can either treat the
74 cursor as an :term:`iterator`, call the cursor's :meth:`fetchone` method to
75 retrieve a single matching row, or call :meth:`fetchall` to get a list of the
78 This example uses the iterator form::
81 >>> c.execute('select * from stocks order by price')
85 (u'2006-01-05', u'BUY', u'RHAT', 100, 35.140000000000001)
86 (u'2006-03-28', u'BUY', u'IBM', 1000, 45.0)
87 (u'2006-04-06', u'SELL', u'IBM', 500, 53.0)
88 (u'2006-04-05', u'BUY', u'MSOFT', 1000, 72.0)
94 http://www.pysqlite.org
95 The pysqlite web page.
98 The SQLite web page; the documentation describes the syntax and the available
99 data types for the supported SQL dialect.
101 :pep:`249` - Database API Specification 2.0
102 PEP written by Marc-André Lemburg.
105 .. _sqlite3-module-contents:
107 Module functions and constants
108 ------------------------------
111 .. data:: PARSE_DECLTYPES
113 This constant is meant to be used with the *detect_types* parameter of the
114 :func:`connect` function.
116 Setting it makes the :mod:`sqlite3` module parse the declared type for each
117 column it returns. It will parse out the first word of the declared type,
118 i. e. for "integer primary key", it will parse out "integer", or for
119 "number(10)" it will parse out "number". Then for that column, it will look
120 into the converters dictionary and use the converter function registered for
124 .. data:: PARSE_COLNAMES
126 This constant is meant to be used with the *detect_types* parameter of the
127 :func:`connect` function.
129 Setting this makes the SQLite interface parse the column name for each column it
130 returns. It will look for a string formed [mytype] in there, and then decide
131 that 'mytype' is the type of the column. It will try to find an entry of
132 'mytype' in the converters dictionary and then use the converter function found
133 there to return the value. The column name found in :attr:`cursor.description`
134 is only the first word of the column name, i. e. if you use something like
135 ``'as "x [datetime]"'`` in your SQL, then we will parse out everything until the
136 first blank for the column name: the column name would simply be "x".
139 .. function:: connect(database[, timeout, isolation_level, detect_types, factory])
141 Opens a connection to the SQLite database file *database*. You can use
142 ``":memory:"`` to open a database connection to a database that resides in RAM
145 When a database is accessed by multiple connections, and one of the processes
146 modifies the database, the SQLite database is locked until that transaction is
147 committed. The *timeout* parameter specifies how long the connection should wait
148 for the lock to go away until raising an exception. The default for the timeout
149 parameter is 5.0 (five seconds).
151 For the *isolation_level* parameter, please see the
152 :attr:`Connection.isolation_level` property of :class:`Connection` objects.
154 SQLite natively supports only the types TEXT, INTEGER, FLOAT, BLOB and NULL. If
155 you want to use other types you must add support for them yourself. The
156 *detect_types* parameter and the using custom **converters** registered with the
157 module-level :func:`register_converter` function allow you to easily do that.
159 *detect_types* defaults to 0 (i. e. off, no type detection), you can set it to
160 any combination of :const:`PARSE_DECLTYPES` and :const:`PARSE_COLNAMES` to turn
163 By default, the :mod:`sqlite3` module uses its :class:`Connection` class for the
164 connect call. You can, however, subclass the :class:`Connection` class and make
165 :func:`connect` use your class instead by providing your class for the *factory*
168 Consult the section :ref:`sqlite3-types` of this manual for details.
170 The :mod:`sqlite3` module internally uses a statement cache to avoid SQL parsing
171 overhead. If you want to explicitly set the number of statements that are cached
172 for the connection, you can set the *cached_statements* parameter. The currently
173 implemented default is to cache 100 statements.
176 .. function:: register_converter(typename, callable)
178 Registers a callable to convert a bytestring from the database into a custom
179 Python type. The callable will be invoked for all database values that are of
180 the type *typename*. Confer the parameter *detect_types* of the :func:`connect`
181 function for how the type detection works. Note that the case of *typename* and
182 the name of the type in your query must match!
185 .. function:: register_adapter(type, callable)
187 Registers a callable to convert the custom Python type *type* into one of
188 SQLite's supported types. The callable *callable* accepts as single parameter
189 the Python value, and must return a value of the following types: int, long,
190 float, str (UTF-8 encoded), unicode or buffer.
193 .. function:: complete_statement(sql)
195 Returns :const:`True` if the string *sql* contains one or more complete SQL
196 statements terminated by semicolons. It does not verify that the SQL is
197 syntactically correct, only that there are no unclosed string literals and the
198 statement is terminated by a semicolon.
200 This can be used to build a shell for SQLite, as in the following example:
203 .. literalinclude:: ../includes/sqlite3/complete_statement.py
206 .. function:: enable_callback_tracebacks(flag)
208 By default you will not get any tracebacks in user-defined functions,
209 aggregates, converters, authorizer callbacks etc. If you want to debug them, you
210 can call this function with *flag* as True. Afterwards, you will get tracebacks
211 from callbacks on ``sys.stderr``. Use :const:`False` to disable the feature
215 .. _sqlite3-connection-objects:
220 A :class:`Connection` instance has the following attributes and methods:
222 .. attribute:: Connection.isolation_level
224 Get or set the current isolation level. None for autocommit mode or one of
225 "DEFERRED", "IMMEDIATE" or "EXLUSIVE". See section
226 :ref:`sqlite3-controlling-transactions` for a more detailed explanation.
229 .. method:: Connection.cursor([cursorClass])
231 The cursor method accepts a single optional parameter *cursorClass*. If
232 supplied, this must be a custom cursor class that extends
233 :class:`sqlite3.Cursor`.
236 .. method:: Connection.commit()
238 This method commits the current transaction. If you don't call this method,
239 anything you did since the last call to commit() is not visible from from
240 other database connections. If you wonder why you don't see the data you've
241 written to the database, please check you didn't forget to call this method.
243 .. method:: Connection.rollback()
245 This method rolls back any changes to the database since the last call to
248 .. method:: Connection.close()
250 This closes the database connection. Note that this does not automatically
251 call :meth:`commit`. If you just close your database connection without
252 calling :meth:`commit` first, your changes will be lost!
254 .. method:: Connection.execute(sql, [parameters])
256 This is a nonstandard shortcut that creates an intermediate cursor object by
257 calling the cursor method, then calls the cursor's :meth:`execute` method with
258 the parameters given.
261 .. method:: Connection.executemany(sql, [parameters])
263 This is a nonstandard shortcut that creates an intermediate cursor object by
264 calling the cursor method, then calls the cursor's :meth:`executemany` method
265 with the parameters given.
267 .. method:: Connection.executescript(sql_script)
269 This is a nonstandard shortcut that creates an intermediate cursor object by
270 calling the cursor method, then calls the cursor's :meth:`executescript` method
271 with the parameters given.
274 .. method:: Connection.create_function(name, num_params, func)
276 Creates a user-defined function that you can later use from within SQL
277 statements under the function name *name*. *num_params* is the number of
278 parameters the function accepts, and *func* is a Python callable that is called
281 The function can return any of the types supported by SQLite: unicode, str, int,
282 long, float, buffer and None.
286 .. literalinclude:: ../includes/sqlite3/md5func.py
289 .. method:: Connection.create_aggregate(name, num_params, aggregate_class)
291 Creates a user-defined aggregate function.
293 The aggregate class must implement a ``step`` method, which accepts the number
294 of parameters *num_params*, and a ``finalize`` method which will return the
295 final result of the aggregate.
297 The ``finalize`` method can return any of the types supported by SQLite:
298 unicode, str, int, long, float, buffer and None.
302 .. literalinclude:: ../includes/sqlite3/mysumaggr.py
305 .. method:: Connection.create_collation(name, callable)
307 Creates a collation with the specified *name* and *callable*. The callable will
308 be passed two string arguments. It should return -1 if the first is ordered
309 lower than the second, 0 if they are ordered equal and 1 if the first is ordered
310 higher than the second. Note that this controls sorting (ORDER BY in SQL) so
311 your comparisons don't affect other SQL operations.
313 Note that the callable will get its parameters as Python bytestrings, which will
314 normally be encoded in UTF-8.
316 The following example shows a custom collation that sorts "the wrong way":
318 .. literalinclude:: ../includes/sqlite3/collation_reverse.py
320 To remove a collation, call ``create_collation`` with None as callable::
322 con.create_collation("reverse", None)
325 .. method:: Connection.interrupt()
327 You can call this method from a different thread to abort any queries that might
328 be executing on the connection. The query will then abort and the caller will
332 .. method:: Connection.set_authorizer(authorizer_callback)
334 This routine registers a callback. The callback is invoked for each attempt to
335 access a column of a table in the database. The callback should return
336 :const:`SQLITE_OK` if access is allowed, :const:`SQLITE_DENY` if the entire SQL
337 statement should be aborted with an error and :const:`SQLITE_IGNORE` if the
338 column should be treated as a NULL value. These constants are available in the
339 :mod:`sqlite3` module.
341 The first argument to the callback signifies what kind of operation is to be
342 authorized. The second and third argument will be arguments or :const:`None`
343 depending on the first argument. The 4th argument is the name of the database
344 ("main", "temp", etc.) if applicable. The 5th argument is the name of the
345 inner-most trigger or view that is responsible for the access attempt or
346 :const:`None` if this access attempt is directly from input SQL code.
348 Please consult the SQLite documentation about the possible values for the first
349 argument and the meaning of the second and third argument depending on the first
350 one. All necessary constants are available in the :mod:`sqlite3` module.
353 .. method:: Connection.set_progress_handler(handler, n)
355 .. versionadded:: 2.6
357 This routine registers a callback. The callback is invoked for every *n*
358 instructions of the SQLite virtual machine. This is useful if you want to
359 get called from SQLite during long-running operations, for example to update
362 If you want to clear any previously installed progress handler, call the
363 method with :const:`None` for *handler*.
366 .. attribute:: Connection.row_factory
368 You can change this attribute to a callable that accepts the cursor and the
369 original row as a tuple and will return the real result row. This way, you can
370 implement more advanced ways of returning results, such as returning an object
371 that can also access columns by name.
375 .. literalinclude:: ../includes/sqlite3/row_factory.py
377 If returning a tuple doesn't suffice and you want name-based access to
378 columns, you should consider setting :attr:`row_factory` to the
379 highly-optimized :class:`sqlite3.Row` type. :class:`Row` provides both
380 index-based and case-insensitive name-based access to columns with almost no
381 memory overhead. It will probably be better than your own custom
382 dictionary-based approach or even a db_row based solution.
384 .. XXX what's a db_row-based solution?
387 .. attribute:: Connection.text_factory
389 Using this attribute you can control what objects are returned for the TEXT data
390 type. By default, this attribute is set to :class:`unicode` and the
391 :mod:`sqlite3` module will return Unicode objects for TEXT. If you want to
392 return bytestrings instead, you can set it to :class:`str`.
394 For efficiency reasons, there's also a way to return Unicode objects only for
395 non-ASCII data, and bytestrings otherwise. To activate it, set this attribute to
396 :const:`sqlite3.OptimizedUnicode`.
398 You can also set it to any other callable that accepts a single bytestring
399 parameter and returns the resulting object.
401 See the following example code for illustration:
403 .. literalinclude:: ../includes/sqlite3/text_factory.py
406 .. attribute:: Connection.total_changes
408 Returns the total number of database rows that have been modified, inserted, or
409 deleted since the database connection was opened.
412 .. attribute:: Connection.iterdump
414 Returns an iterator to dump the database in an SQL text format. Useful when
415 saving an in-memory database for later restoration. This function provides
416 the same capabilities as the :kbd:`.dump` command in the :program:`sqlite3`
419 .. versionadded:: 2.6
423 # Convert file existing_db.db to SQL dump file dump.sql
426 con = sqlite3.connect('existing_db.db')
427 full_dump = os.linesep.join([line for line in con.iterdump()])
428 f = open('dump.sql', 'w')
429 f.writelines(full_dump)
433 .. _sqlite3-cursor-objects:
438 A :class:`Cursor` instance has the following attributes and methods:
441 .. method:: Cursor.execute(sql, [parameters])
443 Executes an SQL statement. The SQL statement may be parametrized (i. e.
444 placeholders instead of SQL literals). The :mod:`sqlite3` module supports two
445 kinds of placeholders: question marks (qmark style) and named placeholders
448 This example shows how to use parameters with qmark style:
450 .. literalinclude:: ../includes/sqlite3/execute_1.py
452 This example shows how to use the named style:
454 .. literalinclude:: ../includes/sqlite3/execute_2.py
456 :meth:`execute` will only execute a single SQL statement. If you try to execute
457 more than one statement with it, it will raise a Warning. Use
458 :meth:`executescript` if you want to execute multiple SQL statements with one
462 .. method:: Cursor.executemany(sql, seq_of_parameters)
464 Executes an SQL command against all parameter sequences or mappings found in
465 the sequence *sql*. The :mod:`sqlite3` module also allows using an
466 :term:`iterator` yielding parameters instead of a sequence.
468 .. literalinclude:: ../includes/sqlite3/executemany_1.py
470 Here's a shorter example using a :term:`generator`:
472 .. literalinclude:: ../includes/sqlite3/executemany_2.py
475 .. method:: Cursor.executescript(sql_script)
477 This is a nonstandard convenience method for executing multiple SQL statements
478 at once. It issues a COMMIT statement first, then executes the SQL script it
481 *sql_script* can be a bytestring or a Unicode string.
485 .. literalinclude:: ../includes/sqlite3/executescript.py
488 .. method:: Cursor.fetchone()
490 Fetches the next row of a query result set, returning a single sequence,
491 or ``None`` when no more data is available.
494 .. method:: Cursor.fetchmany([size=cursor.arraysize])
496 Fetches the next set of rows of a query result, returning a list. An empty
497 list is returned when no more rows are available.
499 The number of rows to fetch per call is specified by the *size* parameter.
500 If it is not given, the cursor's arraysize determines the number of rows
501 to be fetched. The method should try to fetch as many rows as indicated by
502 the size parameter. If this is not possible due to the specified number of
503 rows not being available, fewer rows may be returned.
505 Note there are performance considerations involved with the *size* parameter.
506 For optimal performance, it is usually best to use the arraysize attribute.
507 If the *size* parameter is used, then it is best for it to retain the same
508 value from one :meth:`fetchmany` call to the next.
510 .. method:: Cursor.fetchall()
512 Fetches all (remaining) rows of a query result, returning a list. Note that
513 the cursor's arraysize attribute can affect the performance of this operation.
514 An empty list is returned when no rows are available.
517 .. attribute:: Cursor.rowcount
519 Although the :class:`Cursor` class of the :mod:`sqlite3` module implements this
520 attribute, the database engine's own support for the determination of "rows
521 affected"/"rows selected" is quirky.
523 For ``DELETE`` statements, SQLite reports :attr:`rowcount` as 0 if you make a
524 ``DELETE FROM table`` without any condition.
526 For :meth:`executemany` statements, the number of modifications are summed up
527 into :attr:`rowcount`.
529 As required by the Python DB API Spec, the :attr:`rowcount` attribute "is -1 in
530 case no executeXX() has been performed on the cursor or the rowcount of the last
531 operation is not determinable by the interface".
533 This includes ``SELECT`` statements because we cannot determine the number of
534 rows a query produced until all rows were fetched.
536 .. attribute:: Cursor.lastrowid
538 This read-only attribute provides the rowid of the last modified row. It is
539 only set if you issued a ``INSERT`` statement using the :meth:`execute`
540 method. For operations other than ``INSERT`` or when :meth:`executemany` is
541 called, :attr:`lastrowid` is set to :const:`None`.
545 SQLite and Python types
546 -----------------------
552 SQLite natively supports the following types: NULL, INTEGER, REAL, TEXT, BLOB.
554 The following Python types can thus be sent to SQLite without any problem:
556 +------------------------+-------------+
557 | Python type | SQLite type |
558 +========================+=============+
560 +------------------------+-------------+
561 | ``int`` | INTEGER |
562 +------------------------+-------------+
563 | ``long`` | INTEGER |
564 +------------------------+-------------+
566 +------------------------+-------------+
567 | ``str (UTF8-encoded)`` | TEXT |
568 +------------------------+-------------+
569 | ``unicode`` | TEXT |
570 +------------------------+-------------+
571 | ``buffer`` | BLOB |
572 +------------------------+-------------+
574 This is how SQLite types are converted to Python types by default:
576 +-------------+---------------------------------------------+
577 | SQLite type | Python type |
578 +=============+=============================================+
580 +-------------+---------------------------------------------+
581 | ``INTEGER`` | int or long, depending on size |
582 +-------------+---------------------------------------------+
584 +-------------+---------------------------------------------+
585 | ``TEXT`` | depends on text_factory, unicode by default |
586 +-------------+---------------------------------------------+
587 | ``BLOB`` | buffer |
588 +-------------+---------------------------------------------+
590 The type system of the :mod:`sqlite3` module is extensible in two ways: you can
591 store additional Python types in a SQLite database via object adaptation, and
592 you can let the :mod:`sqlite3` module convert SQLite types to different Python
593 types via converters.
596 Using adapters to store additional Python types in SQLite databases
597 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
599 As described before, SQLite supports only a limited set of types natively. To
600 use other Python types with SQLite, you must **adapt** them to one of the
601 sqlite3 module's supported types for SQLite: one of NoneType, int, long, float,
602 str, unicode, buffer.
604 The :mod:`sqlite3` module uses Python object adaptation, as described in
605 :pep:`246` for this. The protocol to use is :class:`PrepareProtocol`.
607 There are two ways to enable the :mod:`sqlite3` module to adapt a custom Python
608 type to one of the supported ones.
611 Letting your object adapt itself
612 """"""""""""""""""""""""""""""""
614 This is a good approach if you write the class yourself. Let's suppose you have
618 def __init__(self, x, y):
619 self.x, self.y = x, y
621 Now you want to store the point in a single SQLite column. First you'll have to
622 choose one of the supported types first to be used for representing the point.
623 Let's just use str and separate the coordinates using a semicolon. Then you need
624 to give your class a method ``__conform__(self, protocol)`` which must return
625 the converted value. The parameter *protocol* will be :class:`PrepareProtocol`.
627 .. literalinclude:: ../includes/sqlite3/adapter_point_1.py
630 Registering an adapter callable
631 """""""""""""""""""""""""""""""
633 The other possibility is to create a function that converts the type to the
634 string representation and register the function with :meth:`register_adapter`.
638 The type/class to adapt must be a :term:`new-style class`, i. e. it must have
639 :class:`object` as one of its bases.
641 .. literalinclude:: ../includes/sqlite3/adapter_point_2.py
643 The :mod:`sqlite3` module has two default adapters for Python's built-in
644 :class:`datetime.date` and :class:`datetime.datetime` types. Now let's suppose
645 we want to store :class:`datetime.datetime` objects not in ISO representation,
646 but as a Unix timestamp.
648 .. literalinclude:: ../includes/sqlite3/adapter_datetime.py
651 Converting SQLite values to custom Python types
652 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
654 Writing an adapter lets you send custom Python types to SQLite. But to make it
655 really useful we need to make the Python to SQLite to Python roundtrip work.
659 Let's go back to the :class:`Point` class. We stored the x and y coordinates
660 separated via semicolons as strings in SQLite.
662 First, we'll define a converter function that accepts the string as a parameter
663 and constructs a :class:`Point` object from it.
667 Converter functions **always** get called with a string, no matter under which
668 data type you sent the value to SQLite.
672 def convert_point(s):
673 x, y = map(float, s.split(";"))
676 Now you need to make the :mod:`sqlite3` module know that what you select from
677 the database is actually a point. There are two ways of doing this:
679 * Implicitly via the declared type
681 * Explicitly via the column name
683 Both ways are described in section :ref:`sqlite3-module-contents`, in the entries
684 for the constants :const:`PARSE_DECLTYPES` and :const:`PARSE_COLNAMES`.
686 The following example illustrates both approaches.
688 .. literalinclude:: ../includes/sqlite3/converter_point.py
691 Default adapters and converters
692 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
694 There are default adapters for the date and datetime types in the datetime
695 module. They will be sent as ISO dates/ISO timestamps to SQLite.
697 The default converters are registered under the name "date" for
698 :class:`datetime.date` and under the name "timestamp" for
699 :class:`datetime.datetime`.
701 This way, you can use date/timestamps from Python without any additional
702 fiddling in most cases. The format of the adapters is also compatible with the
703 experimental SQLite date/time functions.
705 The following example demonstrates this.
707 .. literalinclude:: ../includes/sqlite3/pysqlite_datetime.py
710 .. _sqlite3-controlling-transactions:
712 Controlling Transactions
713 ------------------------
715 By default, the :mod:`sqlite3` module opens transactions implicitly before a
716 Data Modification Language (DML) statement (i.e. INSERT/UPDATE/DELETE/REPLACE),
717 and commits transactions implicitly before a non-DML, non-query statement (i. e.
718 anything other than SELECT/INSERT/UPDATE/DELETE/REPLACE).
720 So if you are within a transaction and issue a command like ``CREATE TABLE
721 ...``, ``VACUUM``, ``PRAGMA``, the :mod:`sqlite3` module will commit implicitly
722 before executing that command. There are two reasons for doing that. The first
723 is that some of these commands don't work within transactions. The other reason
724 is that pysqlite needs to keep track of the transaction state (if a transaction
727 You can control which kind of "BEGIN" statements pysqlite implicitly executes
728 (or none at all) via the *isolation_level* parameter to the :func:`connect`
729 call, or via the :attr:`isolation_level` property of connections.
731 If you want **autocommit mode**, then set :attr:`isolation_level` to None.
733 Otherwise leave it at its default, which will result in a plain "BEGIN"
734 statement, or set it to one of SQLite's supported isolation levels: DEFERRED,
735 IMMEDIATE or EXCLUSIVE.
739 Using pysqlite efficiently
740 --------------------------
743 Using shortcut methods
744 ^^^^^^^^^^^^^^^^^^^^^^
746 Using the nonstandard :meth:`execute`, :meth:`executemany` and
747 :meth:`executescript` methods of the :class:`Connection` object, your code can
748 be written more concisely because you don't have to create the (often
749 superfluous) :class:`Cursor` objects explicitly. Instead, the :class:`Cursor`
750 objects are created implicitly and these shortcut methods return the cursor
751 objects. This way, you can execute a SELECT statement and iterate over it
752 directly using only a single call on the :class:`Connection` object.
754 .. literalinclude:: ../includes/sqlite3/shortcut_methods.py
757 Accessing columns by name instead of by index
758 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
760 One useful feature of the :mod:`sqlite3` module is the builtin
761 :class:`sqlite3.Row` class designed to be used as a row factory.
763 Rows wrapped with this class can be accessed both by index (like tuples) and
764 case-insensitively by name:
766 .. literalinclude:: ../includes/sqlite3/rowclass.py
769 Using the connection as a context manager
770 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
772 .. versionadded:: 2.6
774 Connection objects can be used as context managers
775 that automatically commit or rollback transactions. In the event of an
776 exception, the transaction is rolled back; otherwise, the transaction is
779 .. literalinclude:: ../includes/sqlite3/ctx_manager.py