+Yw>X{ d Z ddlZddlZddlZddlmZ ddlmZ ddlmZ ddlm Z dd lm
Z
dd
lm Z dd lm
Z
dd lmZ dd
lmZ ddlmZ ddlmZ ddl
mZ ddl
mZ dd
l
m Z ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlm Z ddlm Z ddlm Z ddlm Z dd lm Z dd lm!Z! G d d e Z" G d d!e# Z$ G d" d#e$ej% Z& G d$ d%e$ej' Z( G d& d'e$ej) Z*ej' e(ej% e&ej e"ej j eej j eej) e*iZ+i d(ej, d)ej d*ej d+ej d,ej d%ej( d-ej( d#ej& d.ej& d/ej d0ej d1ej d2ej d3ej d4ed5ej d6ej ej ej ej* ej* ej ej! ej- ej. d7Z/ G d8 d9ej0 Z1 G d: d;ej2 Z3 G d< d=ej4 Z5 G d> d?ej6 Z7 G d@ dAej8 Z9 G dB dCej: Z;dS )DacU
.. dialect:: sqlite
:name: SQLite
.. _sqlite_datetime:
Date and Time Types
-------------------
SQLite does not have built-in DATE, TIME, or DATETIME types, and pysqlite does
not provide out of the box functionality for translating values between Python
`datetime` objects and a SQLite-supported format. SQLAlchemy's own
:class:`~sqlalchemy.types.DateTime` and related types provide date formatting
and parsing functionality when SQLite is used. The implementation classes are
:class:`_sqlite.DATETIME`, :class:`_sqlite.DATE` and :class:`_sqlite.TIME`.
These types represent dates and times as ISO formatted strings, which also
nicely support ordering. There's no reliance on typical "libc" internals for
these functions so historical dates are fully supported.
Ensuring Text affinity
^^^^^^^^^^^^^^^^^^^^^^
The DDL rendered for these types is the standard ``DATE``, ``TIME``
and ``DATETIME`` indicators. However, custom storage formats can also be
applied to these types. When the
storage format is detected as containing no alpha characters, the DDL for
these types is rendered as ``DATE_CHAR``, ``TIME_CHAR``, and ``DATETIME_CHAR``,
so that the column continues to have textual affinity.
.. seealso::
`Type Affinity `_ -
in the SQLite documentation
.. _sqlite_autoincrement:
SQLite Auto Incrementing Behavior
----------------------------------
Background on SQLite's autoincrement is at: http://sqlite.org/autoinc.html
Key concepts:
* SQLite has an implicit "auto increment" feature that takes place for any
non-composite primary-key column that is specifically created using
"INTEGER PRIMARY KEY" for the type + primary key.
* SQLite also has an explicit "AUTOINCREMENT" keyword, that is **not**
equivalent to the implicit autoincrement feature; this keyword is not
recommended for general use. SQLAlchemy does not render this keyword
unless a special SQLite-specific directive is used (see below). However,
it still requires that the column's type is named "INTEGER".
Using the AUTOINCREMENT Keyword
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
To specifically render the AUTOINCREMENT keyword on the primary key column
when rendering DDL, add the flag ``sqlite_autoincrement=True`` to the Table
construct::
Table('sometable', metadata,
Column('id', Integer, primary_key=True),
sqlite_autoincrement=True)
Allowing autoincrement behavior SQLAlchemy types other than Integer/INTEGER
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SQLite's typing model is based on naming conventions. Among other things, this
means that any type name which contains the substring ``"INT"`` will be
determined to be of "integer affinity". A type named ``"BIGINT"``,
``"SPECIAL_INT"`` or even ``"XYZINTQPR"``, will be considered by SQLite to be
of "integer" affinity. However, **the SQLite autoincrement feature, whether
implicitly or explicitly enabled, requires that the name of the column's type
is exactly the string "INTEGER"**. Therefore, if an application uses a type
like :class:`.BigInteger` for a primary key, on SQLite this type will need to
be rendered as the name ``"INTEGER"`` when emitting the initial ``CREATE
TABLE`` statement in order for the autoincrement behavior to be available.
One approach to achieve this is to use :class:`.Integer` on SQLite
only using :meth:`.TypeEngine.with_variant`::
table = Table(
"my_table", metadata,
Column("id", BigInteger().with_variant(Integer, "sqlite"), primary_key=True)
)
Another is to use a subclass of :class:`.BigInteger` that overrides its DDL
name to be ``INTEGER`` when compiled against SQLite::
from sqlalchemy import BigInteger
from sqlalchemy.ext.compiler import compiles
class SLBigInteger(BigInteger):
pass
@compiles(SLBigInteger, 'sqlite')
def bi_c(element, compiler, **kw):
return "INTEGER"
@compiles(SLBigInteger)
def bi_c(element, compiler, **kw):
return compiler.visit_BIGINT(element, **kw)
table = Table(
"my_table", metadata,
Column("id", SLBigInteger(), primary_key=True)
)
.. seealso::
:meth:`.TypeEngine.with_variant`
:ref:`sqlalchemy.ext.compiler_toplevel`
`Datatypes In SQLite Version 3 `_
.. _sqlite_concurrency:
Database Locking Behavior / Concurrency
---------------------------------------
SQLite is not designed for a high level of write concurrency. The database
itself, being a file, is locked completely during write operations within
transactions, meaning exactly one "connection" (in reality a file handle)
has exclusive access to the database during this period - all other
"connections" will be blocked during this time.
The Python DBAPI specification also calls for a connection model that is
always in a transaction; there is no ``connection.begin()`` method,
only ``connection.commit()`` and ``connection.rollback()``, upon which a
new transaction is to be begun immediately. This may seem to imply
that the SQLite driver would in theory allow only a single filehandle on a
particular database file at any time; however, there are several
factors both within SQLite itself as well as within the pysqlite driver
which loosen this restriction significantly.
However, no matter what locking modes are used, SQLite will still always
lock the database file once a transaction is started and DML (e.g. INSERT,
UPDATE, DELETE) has at least been emitted, and this will block
other transactions at least at the point that they also attempt to emit DML.
By default, the length of time on this block is very short before it times out
with an error.
This behavior becomes more critical when used in conjunction with the
SQLAlchemy ORM. SQLAlchemy's :class:`.Session` object by default runs
within a transaction, and with its autoflush model, may emit DML preceding
any SELECT statement. This may lead to a SQLite database that locks
more quickly than is expected. The locking mode of SQLite and the pysqlite
driver can be manipulated to some degree, however it should be noted that
achieving a high degree of write-concurrency with SQLite is a losing battle.
For more information on SQLite's lack of write concurrency by design, please
see
`Situations Where Another RDBMS May Work Better - High Concurrency
`_ near the bottom of the page.
The following subsections introduce areas that are impacted by SQLite's
file-based architecture and additionally will usually require workarounds to
work when using the pysqlite driver.
.. _sqlite_isolation_level:
Transaction Isolation Level / Autocommit
----------------------------------------
SQLite supports "transaction isolation" in a non-standard way, along two
axes. One is that of the
`PRAGMA read_uncommitted `_
instruction. This setting can essentially switch SQLite between its
default mode of ``SERIALIZABLE`` isolation, and a "dirty read" isolation
mode normally referred to as ``READ UNCOMMITTED``.
SQLAlchemy ties into this PRAGMA statement using the
:paramref:`_sa.create_engine.isolation_level` parameter of
:func:`_sa.create_engine`.
Valid values for this parameter when used with SQLite are ``"SERIALIZABLE"``
and ``"READ UNCOMMITTED"`` corresponding to a value of 0 and 1, respectively.
SQLite defaults to ``SERIALIZABLE``, however its behavior is impacted by
the pysqlite driver's default behavior.
When using the pysqlite driver, the ``"AUTOCOMMIT"`` isolation level is also
available, which will alter the pysqlite connection using the ``.isolation_level``
attribute on the DBAPI connection and set it to None for the duration
of the setting.
.. versionadded:: 1.3.16 added support for SQLite AUTOCOMMIT isolation level
when using the pysqlite / sqlite3 SQLite driver.
The other axis along which SQLite's transactional locking is impacted is
via the nature of the ``BEGIN`` statement used. The three varieties
are "deferred", "immediate", and "exclusive", as described at
`BEGIN TRANSACTION `_. A straight
``BEGIN`` statement uses the "deferred" mode, where the database file is
not locked until the first read or write operation, and read access remains
open to other transactions until the first write operation. But again,
it is critical to note that the pysqlite driver interferes with this behavior
by *not even emitting BEGIN* until the first write operation.
.. warning::
SQLite's transactional scope is impacted by unresolved
issues in the pysqlite driver, which defers BEGIN statements to a greater
degree than is often feasible. See the section :ref:`pysqlite_serializable`
for techniques to work around this behavior.
.. seealso::
:ref:`dbapi_autocommit`
SAVEPOINT Support
----------------------------
SQLite supports SAVEPOINTs, which only function once a transaction is
begun. SQLAlchemy's SAVEPOINT support is available using the
:meth:`_engine.Connection.begin_nested` method at the Core level, and
:meth:`.Session.begin_nested` at the ORM level. However, SAVEPOINTs
won't work at all with pysqlite unless workarounds are taken.
.. warning::
SQLite's SAVEPOINT feature is impacted by unresolved
issues in the pysqlite driver, which defers BEGIN statements to a greater
degree than is often feasible. See the section :ref:`pysqlite_serializable`
for techniques to work around this behavior.
Transactional DDL
----------------------------
The SQLite database supports transactional :term:`DDL` as well.
In this case, the pysqlite driver is not only failing to start transactions,
it also is ending any existing transaction when DDL is detected, so again,
workarounds are required.
.. warning::
SQLite's transactional DDL is impacted by unresolved issues
in the pysqlite driver, which fails to emit BEGIN and additionally
forces a COMMIT to cancel any transaction when DDL is encountered.
See the section :ref:`pysqlite_serializable`
for techniques to work around this behavior.
.. _sqlite_foreign_keys:
Foreign Key Support
-------------------
SQLite supports FOREIGN KEY syntax when emitting CREATE statements for tables,
however by default these constraints have no effect on the operation of the
table.
Constraint checking on SQLite has three prerequisites:
* At least version 3.6.19 of SQLite must be in use
* The SQLite library must be compiled *without* the SQLITE_OMIT_FOREIGN_KEY
or SQLITE_OMIT_TRIGGER symbols enabled.
* The ``PRAGMA foreign_keys = ON`` statement must be emitted on all
connections before use.
SQLAlchemy allows for the ``PRAGMA`` statement to be emitted automatically for
new connections through the usage of events::
from sqlalchemy.engine import Engine
from sqlalchemy import event
@event.listens_for(Engine, "connect")
def set_sqlite_pragma(dbapi_connection, connection_record):
cursor = dbapi_connection.cursor()
cursor.execute("PRAGMA foreign_keys=ON")
cursor.close()
.. warning::
When SQLite foreign keys are enabled, it is **not possible**
to emit CREATE or DROP statements for tables that contain
mutually-dependent foreign key constraints;
to emit the DDL for these tables requires that ALTER TABLE be used to
create or drop these constraints separately, for which SQLite has
no support.
.. seealso::
`SQLite Foreign Key Support `_
- on the SQLite web site.
:ref:`event_toplevel` - SQLAlchemy event API.
:ref:`use_alter` - more information on SQLAlchemy's facilities for handling
mutually-dependent foreign key constraints.
.. _sqlite_on_conflict_ddl:
ON CONFLICT support for constraints
-----------------------------------
SQLite supports a non-standard clause known as ON CONFLICT which can be applied
to primary key, unique, check, and not null constraints. In DDL, it is
rendered either within the "CONSTRAINT" clause or within the column definition
itself depending on the location of the target constraint. To render this
clause within DDL, the extension parameter ``sqlite_on_conflict`` can be
specified with a string conflict resolution algorithm within the
:class:`.PrimaryKeyConstraint`, :class:`.UniqueConstraint`,
:class:`.CheckConstraint` objects. Within the :class:`_schema.Column` object,
there
are individual parameters ``sqlite_on_conflict_not_null``,
``sqlite_on_conflict_primary_key``, ``sqlite_on_conflict_unique`` which each
correspond to the three types of relevant constraint types that can be
indicated from a :class:`_schema.Column` object.
.. seealso::
`ON CONFLICT `_ - in the SQLite
documentation
.. versionadded:: 1.3
The ``sqlite_on_conflict`` parameters accept a string argument which is just
the resolution name to be chosen, which on SQLite can be one of ROLLBACK,
ABORT, FAIL, IGNORE, and REPLACE. For example, to add a UNIQUE constraint
that specifies the IGNORE algorithm::
some_table = Table(
'some_table', metadata,
Column('id', Integer, primary_key=True),
Column('data', Integer),
UniqueConstraint('id', 'data', sqlite_on_conflict='IGNORE')
)
The above renders CREATE TABLE DDL as::
CREATE TABLE some_table (
id INTEGER NOT NULL,
data INTEGER,
PRIMARY KEY (id),
UNIQUE (id, data) ON CONFLICT IGNORE
)
When using the :paramref:`_schema.Column.unique`
flag to add a UNIQUE constraint
to a single column, the ``sqlite_on_conflict_unique`` parameter can
be added to the :class:`_schema.Column` as well, which will be added to the
UNIQUE constraint in the DDL::
some_table = Table(
'some_table', metadata,
Column('id', Integer, primary_key=True),
Column('data', Integer, unique=True,
sqlite_on_conflict_unique='IGNORE')
)
rendering::
CREATE TABLE some_table (
id INTEGER NOT NULL,
data INTEGER,
PRIMARY KEY (id),
UNIQUE (data) ON CONFLICT IGNORE
)
To apply the FAIL algorithm for a NOT NULL constraint,
``sqlite_on_conflict_not_null`` is used::
some_table = Table(
'some_table', metadata,
Column('id', Integer, primary_key=True),
Column('data', Integer, nullable=False,
sqlite_on_conflict_not_null='FAIL')
)
this renders the column inline ON CONFLICT phrase::
CREATE TABLE some_table (
id INTEGER NOT NULL,
data INTEGER NOT NULL ON CONFLICT FAIL,
PRIMARY KEY (id)
)
Similarly, for an inline primary key, use ``sqlite_on_conflict_primary_key``::
some_table = Table(
'some_table', metadata,
Column('id', Integer, primary_key=True,
sqlite_on_conflict_primary_key='FAIL')
)
SQLAlchemy renders the PRIMARY KEY constraint separately, so the conflict
resolution algorithm is applied to the constraint itself::
CREATE TABLE some_table (
id INTEGER NOT NULL,
PRIMARY KEY (id) ON CONFLICT FAIL
)
.. _sqlite_type_reflection:
Type Reflection
---------------
SQLite types are unlike those of most other database backends, in that
the string name of the type usually does not correspond to a "type" in a
one-to-one fashion. Instead, SQLite links per-column typing behavior
to one of five so-called "type affinities" based on a string matching
pattern for the type.
SQLAlchemy's reflection process, when inspecting types, uses a simple
lookup table to link the keywords returned to provided SQLAlchemy types.
This lookup table is present within the SQLite dialect as it is for all
other dialects. However, the SQLite dialect has a different "fallback"
routine for when a particular type name is not located in the lookup map;
it instead implements the SQLite "type affinity" scheme located at
http://www.sqlite.org/datatype3.html section 2.1.
The provided typemap will make direct associations from an exact string
name match for the following types:
:class:`_types.BIGINT`, :class:`_types.BLOB`,
:class:`_types.BOOLEAN`, :class:`_types.BOOLEAN`,
:class:`_types.CHAR`, :class:`_types.DATE`,
:class:`_types.DATETIME`, :class:`_types.FLOAT`,
:class:`_types.DECIMAL`, :class:`_types.FLOAT`,
:class:`_types.INTEGER`, :class:`_types.INTEGER`,
:class:`_types.NUMERIC`, :class:`_types.REAL`,
:class:`_types.SMALLINT`, :class:`_types.TEXT`,
:class:`_types.TIME`, :class:`_types.TIMESTAMP`,
:class:`_types.VARCHAR`, :class:`_types.NVARCHAR`,
:class:`_types.NCHAR`
When a type name does not match one of the above types, the "type affinity"
lookup is used instead:
* :class:`_types.INTEGER` is returned if the type name includes the
string ``INT``
* :class:`_types.TEXT` is returned if the type name includes the
string ``CHAR``, ``CLOB`` or ``TEXT``
* :class:`_types.NullType` is returned if the type name includes the
string ``BLOB``
* :class:`_types.REAL` is returned if the type name includes the string
``REAL``, ``FLOA`` or ``DOUB``.
* Otherwise, the :class:`_types.NUMERIC` type is used.
.. versionadded:: 0.9.3 Support for SQLite type affinity rules when reflecting
columns.
.. _sqlite_partial_index:
Partial Indexes
---------------
A partial index, e.g. one which uses a WHERE clause, can be specified
with the DDL system using the argument ``sqlite_where``::
tbl = Table('testtbl', m, Column('data', Integer))
idx = Index('test_idx1', tbl.c.data,
sqlite_where=and_(tbl.c.data > 5, tbl.c.data < 10))
The index will be rendered at create time as::
CREATE INDEX test_idx1 ON testtbl (data)
WHERE data > 5 AND data < 10
.. versionadded:: 0.9.9
.. _sqlite_dotted_column_names:
Dotted Column Names
-------------------
Using table or column names that explicitly have periods in them is
**not recommended**. While this is generally a bad idea for relational
databases in general, as the dot is a syntactically significant character,
the SQLite driver up until version **3.10.0** of SQLite has a bug which
requires that SQLAlchemy filter out these dots in result sets.
.. versionchanged:: 1.1
The following SQLite issue has been resolved as of version 3.10.0
of SQLite. SQLAlchemy as of **1.1** automatically disables its internal
workarounds based on detection of this version.
The bug, entirely outside of SQLAlchemy, can be illustrated thusly::
import sqlite3
assert sqlite3.sqlite_version_info < (3, 10, 0), "bug is fixed in this version"
conn = sqlite3.connect(":memory:")
cursor = conn.cursor()
cursor.execute("create table x (a integer, b integer)")
cursor.execute("insert into x (a, b) values (1, 1)")
cursor.execute("insert into x (a, b) values (2, 2)")
cursor.execute("select x.a, x.b from x")
assert [c[0] for c in cursor.description] == ['a', 'b']
cursor.execute('''
select x.a, x.b from x where a=1
union
select x.a, x.b from x where a=2
''')
assert [c[0] for c in cursor.description] == ['a', 'b'], \
[c[0] for c in cursor.description]
The second assertion fails::
Traceback (most recent call last):
File "test.py", line 19, in
[c[0] for c in cursor.description]
AssertionError: ['x.a', 'x.b']
Where above, the driver incorrectly reports the names of the columns
including the name of the table, which is entirely inconsistent vs.
when the UNION is not present.
SQLAlchemy relies upon column names being predictable in how they match
to the original statement, so the SQLAlchemy dialect has no choice but
to filter these out::
from sqlalchemy import create_engine
eng = create_engine("sqlite://")
conn = eng.connect()
conn.execute("create table x (a integer, b integer)")
conn.execute("insert into x (a, b) values (1, 1)")
conn.execute("insert into x (a, b) values (2, 2)")
result = conn.execute("select x.a, x.b from x")
assert result.keys() == ["a", "b"]
result = conn.execute('''
select x.a, x.b from x where a=1
union
select x.a, x.b from x where a=2
''')
assert result.keys() == ["a", "b"]
Note that above, even though SQLAlchemy filters out the dots, *both
names are still addressable*::
>>> row = result.first()
>>> row["a"]
1
>>> row["x.a"]
1
>>> row["b"]
1
>>> row["x.b"]
1
Therefore, the workaround applied by SQLAlchemy only impacts
:meth:`_engine.ResultProxy.keys` and :meth:`.RowProxy.keys()`
in the public API. In
the very specific case where an application is forced to use column names that
contain dots, and the functionality of :meth:`_engine.ResultProxy.keys` and
:meth:`.RowProxy.keys()` is required to return these dotted names unmodified,
the ``sqlite_raw_colnames`` execution option may be provided, either on a
per-:class:`_engine.Connection` basis::
result = conn.execution_options(sqlite_raw_colnames=True).execute('''
select x.a, x.b from x where a=1
union
select x.a, x.b from x where a=2
''')
assert result.keys() == ["x.a", "x.b"]
or on a per-:class:`_engine.Engine` basis::
engine = create_engine("sqlite://", execution_options={"sqlite_raw_colnames": True})
When using the per-:class:`_engine.Engine` execution option, note that
**Core and ORM queries that use UNION may not function properly**.
SQLite-specific table options
-----------------------------
One option for CREATE TABLE is supported directly by the SQLite
dialect in conjunction with the :class:`_schema.Table` construct:
* ``WITHOUT ROWID``::
Table("some_table", metadata, ..., sqlite_with_rowid=False)
.. seealso::
`SQLite CREATE TABLE options
`_
N )JSON)
JSONIndexType) JSONPathType )exc)
processorsschema)sql)types)util)default)
reflection)
ColumnElement)compiler)BLOB)BOOLEAN)CHAR)DECIMAL)FLOAT)INTEGER)NUMERIC)REAL)SMALLINT)TEXT) TIMESTAMP)VARCHARc e Zd Z fdZ xZS ) _SQliteJsonc f t t | || fd}|S )Nc v | S # t $ r t | t j r| cY S w xY wN) TypeError
isinstancenumbersNumber)valuedefault_processors s/builddir/build/BUILD/cloudlinux-venv-1.0.10/venv/lib64/python3.11/site-packages/sqlalchemy/dialects/sqlite/base.pyprocessz-_SQliteJson.result_processor..process sT
((///
eW^44 LLL
s
&88)superr result_processor)selfdialectcoltyper+ r) __class__s @r* r- z _SQliteJson.result_processor} sI !+t 4 4 E E W
)__name__
__module__ __qualname__r-
__classcell__r1 s @r* r r | s8 r2 r c N e Zd ZdZdZd fd Zed Z fdZd Z xZ
S )_DateTimeMixinNc t t | j di | |t j | | _ | || _ d S d S )N )r, r9 __init__recompile_reg_storage_format)r. storage_formatregexpkwr1 s r* r< z_DateTimeMixin.__init__ sY ,nd##,22r222
6**DI %#1D & %r2 c j | j ddddddddz }t t j d| S )a` return True if the storage format will automatically imply
a TEXT affinity.
If the storage format contains no non-numeric characters,
it will imply a NUMERIC storage format on SQLite; in this case,
the type will generate its DDL as DATE_CHAR, DATETIME_CHAR,
TIME_CHAR.
.. versionadded:: 1.0.0
r yearmonthdayhourminutesecond microsecondz[^0-9])r@ boolr= search)r. specs r* format_is_text_affinityz&_DateTimeMixin.format_is_text_affinity sL # '
'
BIi..///r2 c t |t r"| j r
| j |d< | j r
| j |d< t t | j |fi |S )NrA rB )
issubclassr9 r@ r? r, adapt)r. clsrC r1 s r* rS z_DateTimeMixin.adapt sh c> * * )#
<'+';#$y
) #y8 0u^T**0;;;;;r2 c < | | fd}|S )Nc d | z S )Nz'%s'r; )r( bps r* r+ z1_DateTimeMixin.literal_processor..process s BBuII% %r2 )bind_processor)r. r/ r+ rW s @r* literal_processorz _DateTimeMixin.literal_processor s6
)
) & & & & & r2 )NN) r3 r4 r5 r? r@ r< propertyrP rS rY r6 r7 s @r* r9 r9 s DO2 2 2 2 2 2 0 0 X0.< < < < < r2 r9 c 2 e Zd ZdZdZ fdZd Zd Z xZS )DATETIMEa Represent a Python datetime object in SQLite using a string.
The default string storage format is::
"%(year)04d-%(month)02d-%(day)02d %(hour)02d:%(minute)02d:%(second)02d.%(microsecond)06d"
e.g.::
2011-03-15 12:05:57.10558
The storage format can be customized to some degree using the
``storage_format`` and ``regexp`` parameters, such as::
import re
from sqlalchemy.dialects.sqlite import DATETIME
dt = DATETIME(storage_format="%(year)04d/%(month)02d/%(day)02d "
"%(hour)02d:%(minute)02d:%(second)02d",
regexp=r"(\d+)/(\d+)/(\d+) (\d+)-(\d+)-(\d+)"
)
:param storage_format: format string which will be applied to the dict
with keys year, month, day, hour, minute, second, and microsecond.
:param regexp: regular expression which will be applied to incoming result
rows. If the regexp contains named groups, the resulting match dict is
applied to the Python datetime() constructor as keyword arguments.
Otherwise, if positional groups are used, the datetime() constructor
is called with positional arguments via
``*map(int, match_obj.groups(0))``.
zW%(year)04d-%(month)02d-%(day)02d %(hour)02d:%(minute)02d:%(second)02d.%(microsecond)06dc | dd } t t | j |i | |r%d|vs
J d d|vs
J d d| _ d S d S )Ntruncate_microsecondsFrA DYou can specify only one of truncate_microseconds or storage_format.rB .process s }tE#455
!J "[ 9 !J #l #l#(#4" " E=11
!J "[ 9 #$" " : r2 datetimedater@ )r. r/ r+ rg rh ri s @@@r* rX zDATETIME.bind_processor sG $ -
& : r2 c p | j r$t j | j t j S t j S r# )r? r !str_to_datetime_processor_factoryrk str_to_datetimer. r/ r0 s r* r- zDATETIME.result_processor s6 9 . ? 8,
- -r2 r3 r4 r5 __doc__r@ r< rX r- r6 r7 s @r* r\ r\ sm D A
"" " "H. . . . . . .r2 r\ c " e Zd ZdZdZd Zd ZdS )DATEa Represent a Python date object in SQLite using a string.
The default string storage format is::
"%(year)04d-%(month)02d-%(day)02d"
e.g.::
2011-03-15
The storage format can be customized to some degree using the
``storage_format`` and ``regexp`` parameters, such as::
import re
from sqlalchemy.dialects.sqlite import DATE
d = DATE(
storage_format="%(month)02d/%(day)02d/%(year)04d",
regexp=re.compile("(?P\d+)/(?P\d+)/(?P\d+)")
)
:param storage_format: format string which will be applied to the
dict with keys year, month, and day.
:param regexp: regular expression which will be applied to
incoming result rows. If the regexp contains named groups, the
resulting match dict is applied to the Python date() constructor
as keyword arguments. Otherwise, if positional groups are used, the
date() constructor is called with positional arguments via
``*map(int, match_obj.groups(0))``.
z %(year)04d-%(month)02d-%(day)02dc < t j | j fd}|S )Nc z | d S t | r| j | j | j dz S t d )N)rF rG rH z;SQLite Date type only accepts Python date objects as input.)r% rF rG rH r$ )r( rg ri s r* r+ z$DATE.bind_processor..processN s^ }tE=11
!J "[ 9" " - r2 rj )r. r/ r+ rg ri s @@r* rX zDATE.bind_processorJ s8
&
r2 c p | j r$t j | j t j S t j S r# )r? r rn rk rl str_to_daterp s r* r- zDATE.result_processor_ 5 9 * ? 8=
) )r2 N)r3 r4 r5 rr r@ rX r- r; r2 r* rt rt ' sD @ 9O ** * * * *r2 rt c 2 e Zd ZdZdZ fdZd Zd Z xZS )TIMEaZ Represent a Python time object in SQLite using a string.
The default string storage format is::
"%(hour)02d:%(minute)02d:%(second)02d.%(microsecond)06d"
e.g.::
12:05:57.10558
The storage format can be customized to some degree using the
``storage_format`` and ``regexp`` parameters, such as::
import re
from sqlalchemy.dialects.sqlite import TIME
t = TIME(storage_format="%(hour)02d-%(minute)02d-"
"%(second)02d-%(microsecond)06d",
regexp=re.compile("(\d+)-(\d+)-(\d+)-(?:-(\d+))?")
)
:param storage_format: format string which will be applied to the dict
with keys hour, minute, second, and microsecond.
:param regexp: regular expression which will be applied to incoming result
rows. If the regexp contains named groups, the resulting match dict is
applied to the Python time() constructor as keyword arguments. Otherwise,
if positional groups are used, the time() constructor is called with
positional arguments via ``*map(int, match_obj.groups(0))``.
z6%(hour)02d:%(minute)02d:%(second)02d.%(microsecond)06dc | dd } t t | j |i | |r%d|vs
J d d|vs
J d d| _ d S d S )Nr^ FrA r_ rB r` z$%(hour)02d:%(minute)02d:%(second)02d)ra r, r{ r< r@ rb s r* r< z
TIME.__init__ s &
+BE J J "dD"D3F333 J#6111B 211 6)))3 *)) $JD J Jr2 c < t j | j fd}|S )Nc | d S t | r | j | j | j | j dz S t d )N)rI rJ rK rL z;SQLite Time type only accepts Python time objects as input.)r% rI rJ rK rL r$ )r(
datetime_timeri s r* r+ z$TIME.bind_processor..process sd }tE=11
!J #l #l#(#4 " " - r2 )rk timer@ )r. r/ r+ r ri s @@r* rX zTIME.bind_processor s8
& r2 c p | j r$t j | j t j S t j S r# )r? r rn rk r str_to_timerp s r* r- zTIME.result_processor ry r2 rq r7 s @r* r{ r{ h sm > OO J J J J J ,* * * * * * *r2 r{ BIGINTr BOOLr r DATE_CHAR
DATETIME_CHARDOUBLEr r INTr r r r )r r r{ TIME_CHARr r NVARCHARNCHARc e Zd Z ej ej j ddddddddd d
d
Zd Zd
Z d Z
d Z d Z fdZ
d Zd Zd Zd Zd Zd Zd Zd Z xZS )SQLiteCompilerz%mz%dz%Yz%Sz%Hz%jz%Mz%sz%wz%W)
rG rH rF rK rI doyrJ epochdowweekc dS )NCURRENT_TIMESTAMPr; r. fnrC s r* visit_now_funcz SQLiteCompiler.visit_now_func s ""r2 c dS )Nz(DATETIME(CURRENT_TIMESTAMP, "localtime")r; )r. funcrC s r* visit_localtimestamp_funcz(SQLiteCompiler.visit_localtimestamp_func s 99r2 c dS )N1r; r. exprrC s r*
visit_truezSQLiteCompiler.visit_true sr2 c dS )N0r; r s r* visit_falsezSQLiteCompiler.visit_false r r2 c 2 d| | z S )Nzlength%s)function_argspecr s r* visit_char_length_funcz%SQLiteCompiler.visit_char_length_func s D 1 1" 5 555r2 c | j j r! t t | j |fi |S | j |j fi |S r# )r/
supports_castr, r
visit_castr+ clause)r. castrd r1 s r* r zSQLiteCompiler.visit_cast sQ < % 795 ..9$II&II I 4< 66v66 6r2 c d| j |j d | j |j fi |dS # t $ r;}t j t j d|j z | Y d }~d S d }~ww xY w)NzCAST(STRFTIME('z', z
) AS INTEGER)z#%s is not a valid extract argument.replace_context) extract_mapfieldr+ r KeyErrorr raise_r CompileError)r. extractrC errs r*
visit_extractz SQLiteCompiler.visit_extract s /// W\00R0000
K 9GMI !$
s )+
A00A++A0c @ d}|j |d | j |j fi |z z
}|j N|j -|d| t j d z z
}|d | j |j fi |z z
}n&|d | j t j d fi |z z
}|S )N z
LIMIT z OFFSET r )
_limit_clauser+ _offset_clauser literal)r. selectrC texts r* limit_clausezSQLiteCompiler.limit_clause s + K,$,v/C"J"Jr"J"JJ JD ,#+ dll3;r??&C&CCC J f.C!J!Jr!J!JJ JDD J ck!nn!C!C!C!CC CD r2 c dS )Nr r; )r. r rC s r* for_update_clausez SQLiteCompiler.for_update_clause s rr2 c p | |j d| |j S )Nz IS NOT r+ leftrightr. binaryoperatorrC s r* visit_is_distinct_from_binaryz,SQLiteCompiler.visit_is_distinct_from_binary! 7 LL % % % % LL & & &
r2 c p | |j d| |j S )Nz IS r r s r* visit_isnot_distinct_from_binaryz/SQLiteCompiler.visit_isnot_distinct_from_binary' r r2 c |j j t j u rd}nd}| | j |j fi | | j |j fi |fz S Nz JSON_QUOTE(JSON_EXTRACT(%s, %s))zJSON_EXTRACT(%s, %s)type_type_affinitysqltypesr r+ r r r. r r rC r s r* visit_json_getitem_op_binaryz+SQLiteCompiler.visit_json_getitem_op_binary- d ; % 6 65DD)D DL + + + + DL , , , ,
r2 c |j j t j u rd}nd}| | j |j fi | | j |j fi |fz S r r r s r* !visit_json_path_getitem_op_binaryz0SQLiteCompiler.visit_json_path_getitem_op_binary8 r r2 c dd d |pt gD dd d |pt gD dS )NzSELECT , c 3 K | ]}d V dS r Nr; .0type_s r* z6SQLiteCompiler.visit_empty_set_expr..E " DDecDDDDDDr2 z FROM (SELECT c 3 K | ]}d V dS r r; r s r* r z6SQLiteCompiler.visit_empty_set_expr..F r r2 z ) WHERE 1!=1)joinr )r.
element_typess r* visit_empty_set_exprz#SQLiteCompiler.visit_empty_set_exprC sl IIDD}'C DDD D D D D IIDD}'C DDD D D D D
r2 )r3 r4 r5 r update_copyr SQLCompilerr r r r r r r r r r r r r r r r6 r7 s @r* r r s@ "$" (
K # # #: : : 6 6 67 7 7 7 7
r2 r c b e Zd Zd Z fdZ fdZ fdZ fdZ fdZd Z d d
Z
d Z xZ S )
SQLiteDDLCompilerc b | j j |j | }| j | dz |z }| | }|/t |j j t rd|z dz }|d|z z
}|j s"|dz
}|j d d }||d |z z
}|j
r|j d
u r6t |j j
j d k rt% j d |j j d d
rtt |j j
j d k rRt) |j j t, j r.|j s'|dz
}|j d d }||d |z z
}|dz
}|j |d| |j z z
}|S )N)type_expression ()z DEFAULT z NOT NULLsqliteon_conflict_not_null
ON CONFLICT Tr z@SQLite does not support autoincrement for composite primary keys
autoincrementz PRIMARY KEYon_conflict_primary_keyz AUTOINCREMENT)r/
type_compilerr+ r preparer
format_columnget_column_default_stringr% server_defaultargr nullabledialect_options primary_keyr lentablecolumnsr r rR r r Integer foreign_keyscomputed)r. columnrd r0 colspecr on_conflict_clauses r* get_column_specificationz*SQLiteDDLCompiler.get_column_specificationK s ,,44 K 5
---f55;gE0088 &/3]CC
. -#- {W, ,G @ { "G!'!7!A&" "-?-??? ,$,, 0899Q>>&- ,X6G
, 0899Q>> v{ 98;KLL ? + ? >)%+%;H%E-&" &11C CCG++ ? & sT\\&/ : :: :Gr2 c t |j dk rat | d }|j rE|j j d d r-t
|j j t j
r |j sd S t t | | }|j d d }|>t |j dk r&t | d j d d }||d|z z
}|S )Nr r r r on_conflictr r )r r listr r r rR r r r r r r, r visit_primary_key_constraint)r.
constraintcr r r1 s r* r z.SQLiteDDLCompiler.visit_primary_key_constraint s z! " "a ' 'Z #A
G+H5oF
qv 4h6FGG
t&--JJ
( 7 A
%#j.@*A*AQ*F*F!%j!1!1!!4!DX!N)" ) O&88 8D r2 c p t t | | }|j d d }|mt |j dk rUt
| d }t |t j r&t
| d j d d }||d|z z
}|S )Nr r r r on_conflict_uniquer )
r, r visit_unique_constraintr r r r r% r
SchemaItem)r. r r r col1r1 s r* r
z)SQLiteDDLCompiler.visit_unique_constraint s &--EE
( 7 A
%#j.@*A*AQ*F*F
##A&D$ 122
(%)*%5%5a%8%H &&&(" ) O&88 8D r2 c t t | | }|j d d }||d|z z
}|S )Nr r r )r, r visit_check_constraintr )r. r r r r1 s r* r z(SQLiteDDLCompiler.visit_check_constraint s[ &--DD
( 7 A
) O&88 8D r2 c t t | | }|j d d t j d |S )Nr r zFSQLite does not support on conflict clause for column check constraint)r, r visit_column_check_constraintr r r )r. r r r1 s r* r z/SQLiteDDLCompiler.visit_column_check_constraint s\ &--KK
%h /
> J"*
r2 c |j d j j }|j d j j }|j |j k rd S t t | | S )Nr )elementsparentr r r r, r visit_foreign_key_constraint)r. r local_table remote_tabler1 s r* r z.SQLiteDDLCompiler.visit_foreign_key_constraint se )!,39 !*1-4: !4 4 44*D11NN
r2 c 0 | |d S )z=Format the remote table clause of a CREATE CONSTRAINT clause.F
use_schema) format_table)r. r r r s r* define_constraint_remote_tablez0SQLiteDDLCompiler.define_constraint_remote_table s $$Uu$===r2 FTc
|j } | j }d}|j r|dz
}|d |d d| |j d d d
fd |j D d z
}|j d
d }|% j
|dd }|d|z z
}|S )NzCREATE zUNIQUE zINDEX T)include_schemaz ON Fr z (r c 3 R K | ]!}j |d d V "dS )FT
include_table
literal_bindsN) sql_compilerr+ )r r r. s r* r z7SQLiteDDLCompiler.visit_create_index.. sX !))T * r2 r r wherer" z WHERE ) element_verify_index_tabler unique_prepared_index_namer r r expressionsr r% r+ ) r. creater include_table_schemaindexr r whereclausewhere_compileds ` r* visit_create_indexz$SQLiteDDLCompiler.visit_create_index s% '''= < I D % %eD % A A A A ! !%+% ! @ @ @ @ II " -
+H5g> " ! . 6 65 7 N
I. .D r2 c 4 |j d d du rdS dS )Nr
with_rowidFz
WITHOUT ROWIDr )r )r. r s r* post_create_tablez#SQLiteDDLCompiler.post_create_table s% *< 8E A A%%rr2 )FT)
r3 r4 r5 r r r
r r r r r1 r4 r6 r7 s @r* r r J s 2 2 2h > (
> > > BF : r2 r c > e Zd Zd Z fdZ fdZ fdZd Z xZS )SQLiteTypeCompilerc , | | S r# )
visit_BLOBr. r rC s r* visit_large_binaryz%SQLiteTypeCompiler.visit_large_binary s u%%%r2 c t |t r|j r(t t | | S dS )Nr )r% r9 rP r, r6 visit_DATETIMEr. r rC r1 s r* r< z!SQLiteTypeCompiler.visit_DATETIME sF 5.11 #, # +T22AA%HH H"?r2 c t |t r|j r(t t | | S dS )Nr )r% r9 rP r, r6
visit_DATEr= s r* r? z SQLiteTypeCompiler.visit_DATE F 5.11 , +T22==eDD D ;r2 c t |t r|j r(t t | | S dS )Nr )r% r9 rP r, r6
visit_TIMEr= s r* rB z SQLiteTypeCompiler.visit_TIME r@ r2 c dS )Nr r; r9 s r*
visit_JSONz SQLiteTypeCompiler.visit_JSON s vr2 ) r3 r4 r5 r: r< r? rB rD r6 r7 s @r* r6 r6 s & & &# # # # # r2 r6 c ( e Zd Z eg d ZdS )SQLiteIdentifierPreparer)uaddafterallalteranalyzeandasascattachr beforebeginbetweenbycascadecaser checkcollater commitconflictr r, cross current_date current_timecurrent_timestampdatabaser
deferrabledeferreddeletedescdetachdistinctdropeachelseendescapeexcept exclusiveexistsexplainfalsefailforforeignfromfullglobgrouphavingifignore immediateinr. indexed initiallyinnerinsertinstead intersectintoisisnullr keyr likelimitmatchnaturalnotnotnullnullofoffsetonororderouterplanpragmaprimaryqueryraise
referencesreindexrenamereplacerestrictr rollbackrowr setr temp temporarythento transactiontriggertrueunionr) updateusingvacuumvaluesviewvirtualwhenr& N)r3 r4 r5 r reserved_wordsr; r2 r* rF rF ' s3 Sv
v
v
x xNNNr2 rF c 4 e Zd Zej d Zd ZdS )SQLiteExecutionContextc R | j j p| j dd S )Nsqlite_raw_colnamesF)r/ _broken_dotted_colnamesexecution_optionsget)r. s r* _preserve_raw_colnamesz-SQLiteExecutionContext._preserve_raw_colnames s1 4 4
H%))*?GG
r2 c Z | j s!d|v r | d d |fS |d fS )N.r )r split)r. colnames r* _translate_colnamez)SQLiteExecutionContext._translate_colname s= * !sg~~==%%b)72 2D= r2 N)r3 r4 r5 r memoized_propertyr r r; r2 r* r r s@
! ! ! ! !r2 r c e Zd ZdZdZdZdZdZdZdZ dZ
dZ dZ e
ZeZeZeZeZeZeZdZej dddfej ddifej ddddfej d difgZ dZ dZ! e"j# d
d d&d
Z$dddZ%d Z&d Z'd Z(e)j* d Z+e)j* d'd Z,e)j* d Z-e)j* d Z.d'dZ/e)j* d'd Z0e)j* d'd Z1e)j* d'd Z2d Z3d Z4e)j* d'd Z5e)j* d'd Z6d Z7e)j* d'd! Z8e)j* d'd" Z9e)j* d'd# Z:e)j* d'd$ Z;d'd%Z
aZZ%% >6> > >5r2 c $ j fd}|S d S )Nc > | j d S r# )r r )connr. s r* connectz)SQLiteDialect.on_connect..connectT s" ((t/CDDDDDr2 )r )r. r s ` r*
on_connectzSQLiteDialect.on_connectQ s6 +
E
E
E
E
E N4r2 c H d}| | }d |D S )NzPRAGMA database_listc 6 g | ]}|d dk |d S )r r r; )r dbs r*
z2SQLiteDialect.get_schema_names..` s% 666"bevoo1ooor2 r )r. r rC sdls r* get_schema_namesz SQLiteDialect.get_schema_names[ s. "
"
"666666r2 c | | j | }d|z }nd}d|d}| | }d |D S )N%s.sqlite_master
sqlite_masterSELECT name FROM z! WHERE type='table' ORDER BY namec g | ]
}|d S r r; r r s r* r z1SQLiteDialect.get_table_names..m %%%3A%%%r2 identifier_preparerquote_identifierr r. r r rC qschemamasterr rss r* get_table_namesz SQLiteDialect.get_table_namesb sg .??GGG''1FF$F FF
"
"%%"%%%%r2 c H d}| | }d |D S )NzESELECT name FROM sqlite_temp_master WHERE type='table' ORDER BY name c g | ]
}|d S r r; r s r* r z6SQLiteDialect.get_temp_table_names..w r r2 r r. r rC r r s r* get_temp_table_namesz"SQLiteDialect.get_temp_table_nameso s5
0
"
"%%"%%%%r2 c H d}| | }d |D S )NzDSELECT name FROM sqlite_temp_master WHERE type='view' ORDER BY name c g | ]
}|d S r r; r s r* r z5SQLiteDialect.get_temp_view_names.. r r2 r r s r* get_temp_view_namesz!SQLiteDialect.get_temp_view_namesy s5
/
"
"%%"%%%%r2 c R | |d|| }t | S )N
table_infor
)_get_table_pragmarM )r. r
table_namer infos r* has_tablezSQLiteDialect.has_table s3 %% j &
Dzzr2 c | | j | }d|z }nd}d|d}| | }d |D S )Nr r r z WHERE type='view' ORDER BY namec g | ]
}|d S r r; r s r* r z0SQLiteDialect.get_view_names.. r r2 r r s r* get_view_namesz SQLiteDialect.get_view_names sg .??GGG''1FF$F FF
"
"%%"%%%%r2 c \ |=| j | }d|z }d|d}| ||f }nI d}| ||f }n.# t j $ r d}| ||f }Y nw xY w| } | r
| d j S d S )Nr zSELECT sql FROM z WHERE name = ? AND type='view'zzSELECT sql FROM (SELECT * FROM sqlite_master UNION ALL SELECT * FROM sqlite_temp_master) WHERE name = ? AND type='view'z