Lines Matching refs:SQLite
1 :mod:`!sqlite3` --- DB-API 2.0 interface for SQLite databases
5 :synopsis: A DB-API 2.0 implementation using SQLite 3.x.
25 SQLite is a C library that provides a lightweight disk-based database that
28 SQLite for internal data storage. It's also possible to prototype an
29 application using SQLite and then port the code to a larger database such as
34 requires SQLite 3.15.2 or newer.
48 The SQLite web page; the documentation describes the syntax and the
101 thanks to the `flexible typing`_ feature of SQLite,
111 but SQLite versions older than 3.33.0 do not recognise that variant.
114 the ``sqlite_master`` table built-in to SQLite,
227 You've now created an SQLite database using the :mod:`!sqlite3` module,
268 Open a connection to an SQLite database.
272 You can pass ``":memory:"`` to create an `SQLite database existing only
286 :ref:`natively supported by SQLite <sqlite3-types>`
332 The query string allows passing parameters to SQLite,
409 into an SQLite type.
412 :ref:`type that SQLite natively understands <sqlite3-types>`.
416 Register the *converter* :term:`callable` to convert SQLite objects of type
418 The converter is invoked for all SQLite values of type *typename*;
503 Version number of the runtime SQLite library as a :class:`string <str>`.
507 Version number of the runtime SQLite library as a :class:`tuple` of
515 underlying SQLite library is compiled with. The SQLite threading modes are:
517 1. **Single-thread**: In this mode, all mutexes are disabled and SQLite is
519 2. **Multi-thread**: In this mode, SQLite can be safely used by multiple
522 3. **Serialized**: In serialized mode, SQLite can be safely used by
525 The mappings from SQLite threading modes to DB-API 2.0 threadsafety levels
529 … | SQLite threading | :pep:`threadsafety | `SQLITE_THREADSAFE`_ | DB-API 2.0 meaning |
550 This is not the version of the SQLite library.
560 This is not the version of the SQLite library.
589 The availability of these constants varies depending on the version of SQLite
597 SQLite docs: Database Connection Configuration Options
607 Each open SQLite database is represented by a ``Connection`` object,
623 An SQLite database connection has the following attributes and methods:
724 The callable must return :ref:`a type natively supported by SQLite
732 which allows SQLite to perform additional optimizations.
773 :ref:`a type natively supported by SQLite <sqlite3-types>`.
834 :ref:`a type natively supported by SQLite <sqlite3-types>`.
842 If used with a version of SQLite older than 3.25.0,
962 by the underlying SQLite library.
971 Please consult the SQLite documentation about the possible values for the first
988 instructions of the SQLite virtual machine. This is useful if you want to
989 get called from SQLite during long-running operations, for example to update
1007 for each SQL statement that is actually executed by the SQLite backend.
1034 Enable the SQLite engine to load SQLite extensions from shared libraries
1036 else, disallow loading SQLite extensions.
1037 SQLite extensions can define new functions,
1039 extension is the fulltext-search extension distributed with SQLite.
1044 default, because some platforms (notably macOS) have SQLite
1073 # example from SQLite wiki
1086 Load an SQLite extension from a shared library.
1092 The path to the SQLite extension.
1098 SQLite will come up with an entry point name of its own;
1099 see the SQLite docs `Loading an Extension`_ for details.
1148 Create a backup of an SQLite database.
1222 The `SQLite limit category`_ to be queried.
1227 If *category* is not recognised by the underlying SQLite library.
1255 The `SQLite limit category`_ to be set.
1264 If *category* is not recognised by the underlying SQLite library.
1325 This method is only available if the underlying SQLite library has the
1351 If *data* does not contain a valid SQLite database.
1358 This method is only available if the underlying SQLite library has the
1374 * ``True``: Use SQLite's `autocommit mode`_.
1397 This read-only attribute corresponds to the low-level SQLite
1411 corresponding to the underlying `SQLite transaction behaviour`_,
1440 The callable is invoked for SQLite values with the ``TEXT`` data type.
1659 Read-only attribute that provides the SQLite database :class:`Connection`
1713 and returns a custom object representing an SQLite row.
1765 that can read and write data in an SQLite :abbr:`BLOB (Binary Large OBject)`.
1840 <sqlite3-conform>` to :ref:`native SQLite types <sqlite3-types>`.
1863 If the exception originated from within the SQLite library,
1869 `SQLite API <https://sqlite.org/rescode.html>`_
1876 from the `SQLite API <https://sqlite.org/rescode.html>`_
1882 Exception raised for misuse of the low-level SQLite C API.
1915 Exception raised when SQLite encounters an internal error.
1917 SQLite library.
1930 underlying SQLite library. For example, setting *deterministic* to
1931 ``True`` in :meth:`~Connection.create_function`, if the underlying SQLite library
1938 SQLite and Python types
1941 SQLite natively supports the following types: ``NULL``, ``INTEGER``,
1944 The following Python types can thus be sent to SQLite without any problem:
1947 | Python type | SQLite type |
1961 This is how SQLite types are converted to Python types by default:
1964 | SQLite type | Python type |
1979 store additional Python types in an SQLite database via
1981 and you can let the :mod:`!sqlite3` module convert SQLite types to
2027 in order to provide a simple SQLite shell.
2042 Print underlying SQLite library version.
2119 How to adapt custom Python types to SQLite values
2122 SQLite supports only a limited set of data types natively.
2123 To store custom Python types in SQLite databases, *adapt* them to one of the
2124 :ref:`Python types SQLite natively understands <sqlite3-types>`.
2126 There are two ways to adapt Python objects to SQLite types:
2175 to an SQLite-compatible type.
2204 How to convert SQLite values to custom Python types
2207 Writing an adapter lets you convert *from* custom Python types *to* SQLite
2209 To be able to convert *from* SQLite values *to* custom Python types,
2213 separated via semicolons as strings in SQLite.
2221 no matter the underlying SQLite data type.
2229 We now need to tell :mod:`!sqlite3` when it should convert a given SQLite value.
2450 How to work with SQLite URIs
2492 can be found in the `SQLite URI documentation`_.
2541 above example. In such cases, SQLite returns a single row with columns
2602 By default, :mod:`!sqlite3` uses :class:`str` to adapt SQLite values
2608 Because of SQLite's `flexible typing`_, it is not uncommon to encounter table
2679 Set *autocommit* to ``True`` to enable SQLite's `autocommit mode`_.
2682 Note that SQLite's autocommit mode is distinct from
2685 the low-level SQLite autocommit mode.
2718 You can choose the underlying `SQLite transaction behaviour`_ —
2725 This leaves the underlying SQLite library in `autocommit mode`_,
2728 The underlying SQLite library autocommit mode can be queried using the