/opt/cloudlinux/venv/lib/python3.11/site-packages/sqlalchemy/sql/__pycache__
Edit: /opt/cloudlinux/venv/lib/python3.11/site-packages/sqlalchemy/sql/__pycache__/dml.cpython-311.pyc (40192B)
<3R j d Z ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddl m
Z
ddl m Z dd l m Z dd
l m
Z
dd l mZ dd l mZ dd
lmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ G d deeeee Z G d de Z G d de Z G d de Z G d d e Zd S ) zd
Provide :class:`_expression.Insert`, :class:`_expression.Update` and
:class:`_expression.Delete`.
)util)
_from_objects) _generative)
DialectKWArgs)
Executable)_clone)_column_as_key)_literal_as_text)and_)
ClauseElement)Null)_interpret_as_from)_interpret_as_select)HasCTE) HasPrefixes )excc e Zd ZdZdZej ddi Z ej Z
dZ dZ dZ
dZd Zd Zd
Zd Z eee Zed Zedd ZdS )
UpdateBasezDForm the base for ``INSERT``, ``UPDATE``, and ``DELETE`` statements. update_base
autocommitTN Fc fd j re|ct |t r |r*t |d t st d d |D _ t
| dfS t |t t f rU|rSt |d t t t f r+ j st j d fd|D dfS | dfS ) Nc t | t t f r1t d t j j | D S | S )Nc 3 . K | ]\ }}|j |fV d S N)key).0cpvals f/builddir/build/BUILD/cloudlinux-venv-1.0.12/venv/lib64/python3.11/site-packages/sqlalchemy/sql/dml.py
zHUpdateBase._process_colparams..process_single..2 s, NNgaQUDMNNNNNN )
isinstancelisttupledictziptabler )pselfs r! process_singlez5UpdateBase._process_colparams..process_single0 sI !dE]++
NNTZ\19M9MNNNNNNr# zOWhen preserve_parameter_order is True, values() only accepts a list of 2-tuplesc g | ]\ }}|S r r )r r values r!
z1UpdateBase._process_colparams..> s 'I'I'I
U'I'I'Ir# Fz8This construct does not support multiple parameter sets.c & g | ]
} | S r r )r r* r, s r! r0 z1UpdateBase._process_colparams..N s# :::!NN1%%:::r# T)
_preserve_parameter_orderr$ r% r&
ValueError_parameter_orderingr' _supports_multi_parametersr InvalidRequestError)r+
parametersr, s ` @r! _process_colparamsz UpdateBase._process_colparams/ s@ )
+j.D j$//
#-jmU#C#C
!? (J'Ij'I'I'ID $
##U* *
zD%= 1 1 5 5 :a=4*=>> 5 2
-/
;:::z:::D@ @!>*--u4 4r# c t d )zSet the parameters for the statement.
This method raises ``NotImplementedError`` on the base class,
and is overridden by :class:`.ValuesBase` to provide the
SET/VALUES clause of UPDATE and INSERT.
zparams() is not supported for INSERT/UPDATE/DELETE statements. To set the values for an INSERT or UPDATE statement, use stmt.values(**parameters).)NotImplementedError)r+ argkws r! paramszUpdateBase.paramsR s "
*
r# c ( | j p | j j S )zuReturn a 'bind' linked to this :class:`.UpdateBase`
or a :class:`_schema.Table` associated with it.
)_bindr) bind)r+ s r! r@ zUpdateBase.bind` s
z,TZ_,r# c || _ d S r )r? )r+ r@ s r! _set_bindzUpdateBase._set_bindg s
r# c | j rt j d | j rt j d || _ dS )a Add a :term:`RETURNING` or equivalent clause to this statement.
e.g.::
stmt = table.update().\
where(table.c.data == 'value').\
values(status='X').\
returning(table.c.server_flag,
table.c.updated_timestamp)
for server_flag, updated_timestamp in connection.execute(stmt):
print(server_flag, updated_timestamp)
The given collection of column expressions should be derived from the
table that is the target of the INSERT, UPDATE, or DELETE. While
:class:`_schema.Column` objects are typical, the elements can also be
expressions::
stmt = table.insert().returning(
(table.c.first_name + " " + table.c.last_name).
label('fullname'))
Upon compilation, a RETURNING clause, or database equivalent,
will be rendered within the statement. For INSERT and UPDATE,
the values are the newly inserted/updated values. For DELETE,
the values are those of the rows which were deleted.
Upon execution, the values of the columns to be returned are made
available via the result set and can be iterated using
:meth:`_engine.ResultProxy.fetchone` and similar.
For DBAPIs which do not
natively support returning values (i.e. cx_oracle), SQLAlchemy will
approximate this behavior at the result level so that a reasonable
amount of behavioral neutrality is provided.
Note that not all databases/DBAPIs
support RETURNING. For those backends with no support,
an exception is raised upon compilation and/or execution.
For those who do support it, the functionality across backends
varies greatly, including restrictions on executemany()
and other statements which return multiple rows. Please
read the documentation notes for the database in use in
order to determine the availability of RETURNING.
.. seealso::
:meth:`.ValuesBase.return_defaults` - an alternative method tailored
towards efficient fetching of server-side defaults and triggers
for single-row INSERTs or UPDATEs.
z9return_defaults() is already configured on this statementzThe returning() method does not currently support multiple additive calls. The existing RETURNING clause being replaced by new columns.N)_return_defaultsr r6
_returningr warnr+ colss r! returningzUpdateBase.returningl sZ l )K
? I+
r# *c ^ || j }| j ||f|i | _ dS )a Add a table hint for a single table to this
INSERT/UPDATE/DELETE statement.
.. note::
:meth:`.UpdateBase.with_hint` currently applies only to
Microsoft SQL Server. For MySQL INSERT/UPDATE/DELETE hints, use
:meth:`.UpdateBase.prefix_with`.
The text of the hint is rendered in the appropriate
location for the database backend in use, relative
to the :class:`_schema.Table` that is the subject of this
statement, or optionally to that of the given
:class:`_schema.Table` passed as the ``selectable`` argument.
The ``dialect_name`` option will limit the rendering of a particular
hint to a particular backend. Such as, to add a hint
that only takes effect for SQL Server::
mytable.insert().with_hint("WITH (PAGLOCK)", dialect_name="mssql")
:param text: Text of the hint.
:param selectable: optional :class:`_schema.Table` that specifies
an element of the FROM clause within an UPDATE or DELETE
to be the subject of the hint - applies only to certain backends.
:param dialect_name: defaults to ``*``, if specified as the name
of a particular dialect, will apply these hints only when
that dialect is in use.
N)r) _hintsunion)r+ text
selectable dialect_names r! with_hintzUpdateBase.with_hint s7 @ Jk''*l)CT(JKK r# )NrJ )__name__
__module__ __qualname____doc____visit_name__r _execution_optionsrM r
immutabledictrL r4 _prefixesnamed_with_columnrD r8 r= r@ rB propertyr rI rQ r r# r! r r s ON"N#6<< t T
!
!F I !5 !5 !5F
- - - 8D) $ $D? ? [? B "L "L "L ["L "L "Lr# r c \ e Zd ZdZdZdZdZdZdZdZ d Z
e d Z e d Z
dS )
ValuesBasezTSupplies support for :meth:`.ValuesBase.values` to
INSERT and UPDATE constructs. values_baseFNc t | | _ | | \ | _ | _ |r| | d S d S r )r r) r8 r7 _has_multi_parameters_setup_prefixes)r+ r) valuesprefixess r! __init__zValuesBase.__init__ sa '..
6:6M6M 7
7
33 + * * * * * + +r# c j | j t j d | j r|rt j d |r0t | dk rt j d |d }ni }| j #| | \ | _ | _ n| j rlt | j | _ | | \ }| _ | j st j d | j | np| j
| _ | | \ }| _ | j rt j d | j | |r7| j rt j d | j | dS dS ) a& Specify a fixed VALUES clause for an INSERT statement, or the SET
clause for an UPDATE.
Note that the :class:`_expression.Insert` and
:class:`_expression.Update` constructs support
per-execution time formatting of the VALUES and/or SET clauses,
based on the arguments passed to :meth:`_engine.Connection.execute`.
However, the :meth:`.ValuesBase.values` method can be used to "fix" a
particular set of parameters into the statement.
Multiple calls to :meth:`.ValuesBase.values` will produce a new
construct, each one with the parameter list modified to include
the new parameters sent. In the typical case of a single
dictionary of parameters, the newly passed keys will replace
the same keys in the previous construct. In the case of a list-based
"multiple values" construct, each new list of values is extended
onto the existing list of values.
:param \**kwargs: key value pairs representing the string key
of a :class:`_schema.Column`
mapped to the value to be rendered into the
VALUES or SET clause::
users.insert().values(name="some name")
users.update().where(users.c.id==5).values(name="some name")
:param \*args: As an alternative to passing key/value parameters,
a dictionary, tuple, or list of dictionaries or tuples can be passed
as a single positional argument in order to form the VALUES or
SET clause of the statement. The forms that are accepted vary
based on whether this is an :class:`_expression.Insert` or an
:class:`_expression.Update` construct.
For either an :class:`_expression.Insert` or
:class:`_expression.Update`
construct, a single dictionary can be passed, which works the same as
that of the kwargs form::
users.insert().values({"name": "some name"})
users.update().values({"name": "some new name"})
Also for either form but more typically for the
:class:`_expression.Insert` construct, a tuple that contains an
entry for every column in the table is also accepted::
users.insert().values((5, "some name"))
The :class:`_expression.Insert` construct also supports being
passed a list of dictionaries or full-table-tuples, which on the
server will render the less common SQL syntax of "multiple values" -
this syntax is supported on backends such as SQLite, PostgreSQL,
MySQL, but not necessarily others::
users.insert().values([
{"name": "some name"},
{"name": "some other name"},
{"name": "yet another name"},
])
The above form would render a multiple VALUES statement similar to::
INSERT INTO users (name) VALUES
(:name_1),
(:name_2),
(:name_3)
It is essential to note that **passing multiple values is
NOT the same as using traditional executemany() form**. The above
syntax is a **special** syntax not typically used. To emit an
INSERT statement against multiple rows, the normal method is
to pass a multiple values list to the
:meth:`_engine.Connection.execute`
method, which is supported by all database backends and is generally
more efficient for a very large number of parameters.
.. seealso::
:ref:`execute_multiple` - an introduction to
the traditional Core method of multiple parameter set
invocation for INSERTs and other statements.
.. versionchanged:: 1.0.0 an INSERT that uses a multiple-VALUES
clause, even a list of length one,
implies that the :paramref:`_expression.Insert.inline`
flag is set to
True, indicating that the statement will not attempt to fetch
the "last inserted primary key" or other defaults. The
statement deals with an arbitrary number of rows, so the
:attr:`_engine.ResultProxy.inserted_primary_key`
accessor does not
apply.
.. versionchanged:: 1.0.0 A multiple-VALUES INSERT now supports
columns with Python side default values and callables in the
same way as that of an "executemany" style of invocation; the
callable is invoked for each row. See :ref:`bug_3288`
for other details.
The :class:`_expression.Update`
construct supports a special form which is a
list of 2-tuples, which when provided must be passed in conjunction
with the
:paramref:`_expression.update.preserve_parameter_order`
parameter.
This form causes the UPDATE statement to render the SET clauses
using the order of parameters given to
:meth:`_expression.Update.values`, rather
than the ordering of columns given in the :class:`_schema.Table`.
.. versionadded:: 1.0.10 - added support for parameter-ordered
UPDATE statements via the
:paramref:`_expression.update.preserve_parameter_order`
flag.
.. seealso::
:ref:`updates_order_parameters` - full example of the
:paramref:`_expression.update.preserve_parameter_order`
flag
.. seealso::
:ref:`inserts_and_updates` - SQL Expression
Language Tutorial
:func:`_expression.insert` - produce an ``INSERT`` statement
:func:`_expression.update` - produce an ``UPDATE`` statement
Nz,This construct already inserts from a SELECTz3This construct already has multiple parameter sets.r zWOnly a single dictionary/tuple or list of dictionaries/tuples is accepted positionally.r- zDCan't mix single-values and multiple values formats in one statementz
% & )E
4yy1}}'D QAAA ? " ''**
** )
*"&t"7"7040G0G0J0J-4-1 +3
&&q))))"&/"6"6"8"8040G0G0J0J-4-- +3 &&q))) /)
/'%
&&v..... / /r# c N | j rt j d |pd| _ dS )a Make use of a :term:`RETURNING` clause for the purpose
of fetching server-side expressions and defaults.
E.g.::
stmt = table.insert().values(data='newdata').return_defaults()
result = connection.execute(stmt)
server_created_at = result.returned_defaults['created_at']
When used against a backend that supports RETURNING, all column
values generated by SQL expression or server-side-default will be
added to any existing RETURNING clause, provided that
:meth:`.UpdateBase.returning` is not used simultaneously. The column
values will then be available on the result using the
:attr:`_engine.ResultProxy.returned_defaults` accessor as
a dictionary,
referring to values keyed to the :class:`_schema.Column`
object as well as
its ``.key``.
This method differs from :meth:`.UpdateBase.returning` in these ways:
1. :meth:`.ValuesBase.return_defaults` is only intended for use with
an INSERT or an UPDATE statement that matches exactly one row.
While the RETURNING construct in the general sense supports
multiple rows for a multi-row UPDATE or DELETE statement, or for
special cases of INSERT that return multiple rows (e.g. INSERT from
SELECT, multi-valued VALUES clause),
:meth:`.ValuesBase.return_defaults` is intended only for an
"ORM-style" single-row INSERT/UPDATE statement. The row returned
by the statement is also consumed implicitly when
:meth:`.ValuesBase.return_defaults` is used. By contrast,
:meth:`.UpdateBase.returning` leaves the RETURNING result-set
intact with a collection of any number of rows.
2. It is compatible with the existing logic to fetch auto-generated
primary key values, also known as "implicit returning". Backends
that support RETURNING will automatically make use of RETURNING in
order to fetch the value of newly generated primary keys; while the
:meth:`.UpdateBase.returning` method circumvents this behavior,
:meth:`.ValuesBase.return_defaults` leaves it intact.
3. It can be called against any backend. Backends that don't support
RETURNING will skip the usage of the feature, rather than raising
an exception. The return value of
:attr:`_engine.ResultProxy.returned_defaults` will be ``None``
:meth:`.ValuesBase.return_defaults` is used by the ORM to provide
an efficient implementation for the ``eager_defaults`` feature of
:func:`.mapper`.
:param cols: optional list of column key names or
:class:`_schema.Column`
objects. If omitted, all column expressions evaluated on the server
are added to the returning list.
.. versionadded:: 0.9.0
.. seealso::
:meth:`.UpdateBase.returning`
:attr:`_engine.ResultProxy.returned_defaults`
z1RETURNING is already configured on this statementTN)rE r r6 rD rG s r! return_defaultszValuesBase.return_defaults s; J ? )C
!% r# )rR rS rT rU rV r5 r` r2 rf _post_values_clauserd r rb rp r r# r! r] r] s % % #N!& ! %
F + + + y/ y/ [y/v H- H- [H- H- H-r# r] c V e Zd ZdZdZdZ d
dZd Zed d Z e
fd Z dS ) InsertzRepresent an INSERT construct.
The :class:`_expression.Insert` object is created using the
:func:`_expression.insert()` function.
.. seealso::
:ref:`coretutorial_insert_expressions`
insertTNFc t | ||| || _ dx| _ | _ d| _ || _ || _ | | || _ dS )a Construct an :class:`_expression.Insert` object.
Similar functionality is available via the
:meth:`_expression.TableClause.insert` method on
:class:`_schema.Table`.
:param table: :class:`_expression.TableClause`
which is the subject of the
insert.
:param values: collection of values to be inserted; see
:meth:`_expression.Insert.values`
for a description of allowed formats here.
Can be omitted entirely; a :class:`_expression.Insert` construct
will also dynamically render the VALUES clause at execution time
based on the parameters passed to :meth:`_engine.Connection.execute`.
:param inline: if True, no attempt will be made to retrieve the
SQL-generated default values to be provided within the statement;
in particular,
this allows SQL expressions to be rendered 'inline' within the
statement without the need to pre-execute them beforehand; for
backends that support "returning", this turns off the "implicit
returning" feature for the statement.
If both `values` and compile-time bind parameters are present, the
compile-time bind parameters override the information specified
within `values` on a per-key basis.
The keys within `values` can be either
:class:`~sqlalchemy.schema.Column` objects or their string
identifiers. Each key may reference one of:
* a literal data value (i.e. string, number, etc.);
* a Column object;
* a SELECT statement.
If a ``SELECT`` statement is specified which references this
``INSERT`` statement's table, the statement will be correlated
against the ``INSERT`` statement.
.. seealso::
:ref:`coretutorial_insert_expressions` - SQL Expression Tutorial
:ref:`inserts_and_updates` - SQL Expression Tutorial
NF)
r] rd r? rf select_names#include_insert_from_select_defaultsinlinerE _validate_dialect_kwargsrD ) r+ r) rb rx r@ rc rI rp
dialect_kws r! rd zInsert.__init__ sm v D%:::
*.. d'380 # %%j111 / r# c $ | j | j fS dS Nr )rf r+ rm s r! get_childrenzInsert.get_childrenD s ; "K> !2r# c | j rt j d | d |D \ | _ | _ || _ d| _ || _ t | | _ dS )a Return a new :class:`_expression.Insert` construct which represents
an ``INSERT...FROM SELECT`` statement.
e.g.::
sel = select([table1.c.a, table1.c.b]).where(table1.c.c > 5)
ins = table2.insert().from_select(['a', 'b'], sel)
:param names: a sequence of string column names or
:class:`_schema.Column`
objects representing the target columns.
:param select: a :func:`_expression.select` construct,
:class:`_expression.FromClause`
or other construct which resolves into a
:class:`_expression.FromClause`,
such as an ORM :class:`_query.Query` object, etc. The order of
columns returned from this FROM clause should correspond to the
order of columns sent as the ``names`` parameter; while this
is not checked before passing along to the database, the database
would normally raise an exception if these column lists don't
correspond.
:param include_defaults: if True, non-server default values and
SQL expressions as specified on :class:`_schema.Column` objects
(as documented in :ref:`metadata_defaults_toplevel`) not
otherwise specified in the list of names will be rendered
into the INSERT and SELECT statements, so that these values are also
included in the data to be inserted.
.. note:: A Python-side default that uses a Python callable function
will only be invoked **once** for the whole statement, and **not
per row**.
.. versionadded:: 1.0.0 - :meth:`_expression.Insert.from_select`
now renders
Python-side and SQL expression column defaults into the
SELECT statement for columns otherwise not included in the
list of column names.
.. versionchanged:: 1.0.0 an INSERT that uses FROM SELECT
implies that the :paramref:`_expression.insert.inline`
flag is set to
True, indicating that the statement will not attempt to fetch
the "last inserted primary key" or other defaults. The statement
deals with an arbitrary number of rows, so the
:attr:`_engine.ResultProxy.inserted_primary_key`
accessor does not apply.
z0This construct already inserts value expressionsc F i | ] }t | t S r )r r
)r ns r!
z&Insert.from_select.. s& 6 6 61^A
6 6 6r# TN)
r7 r r6 r8 r` rv rx rw r rf )r+ namesrf include_defaultss r! from_selectzInsert.from_selectJ s d ? )B
7;6M6M 6 6 6 6 67
7
33 " 3C0*622 r# c | j | _ | j t | j | _ d S d S r )r7 rj rf r r+ cloner< s r! _copy_internalszInsert._copy_internals s< /..00 ; " --DKKK # "r# )NFNNNF)T) rR rS rT rU rV r5 rd r~ r r r r r r# r! rs rs s N!%
B0 B0 B0 B0H =3 =3 =3 [=3~ %+ . . . . . .r# rs c j e Zd ZdZdZ d
dZd ZefdZe d Z
e d Z dS ) UpdatezRepresent an Update construct.
The :class:`_expression.Update`
object is created using the :func:`update()`
function.
rk NFc
| | _ t | ||| || _ || _ |t | | _ nd| _ || _ | |
|| _ dS )a; Construct an :class:`_expression.Update` object.
E.g.::
from sqlalchemy import update
stmt = update(users).where(users.c.id==5).\
values(name='user #5')
Similar functionality is available via the
:meth:`_expression.TableClause.update` method on
:class:`_schema.Table`::
stmt = users.update().\
where(users.c.id==5).\
values(name='user #5')
:param table: A :class:`_schema.Table`
object representing the database
table to be updated.
:param whereclause: Optional SQL expression describing the ``WHERE``
condition of the ``UPDATE`` statement; is equivalent to using the
more modern :meth:`~Update.where()` method to specify the ``WHERE``
clause.
:param values:
Optional dictionary which specifies the ``SET`` conditions of the
``UPDATE``. If left as ``None``, the ``SET``
conditions are determined from those parameters passed to the
statement during the execution and/or compilation of the
statement. When compiled standalone without any parameters,
the ``SET`` clause generates for all columns.
Modern applications may prefer to use the generative
:meth:`_expression.Update.values` method to set the values of the
UPDATE statement.
:param inline:
if True, SQL defaults present on :class:`_schema.Column` objects via
the ``default`` keyword will be compiled 'inline' into the statement
and not pre-executed. This means that their values will not
be available in the dictionary returned from
:meth:`_engine.ResultProxy.last_updated_params`.
:param preserve_parameter_order: if True, the update statement is
expected to receive parameters **only** via the
:meth:`_expression.Update.values` method,
and they must be passed as a Python
``list`` of 2-tuples. The rendered UPDATE statement will emit the SET
clause for each referenced column maintaining this order.
.. versionadded:: 1.0.10
.. seealso::
:ref:`updates_order_parameters` - full example of the
:paramref:`_expression.update.preserve_parameter_order` flag
If both ``values`` and compile-time bind parameters are present, the
compile-time bind parameters override the information specified
within ``values`` on a per-key basis.
The keys within ``values`` can be either :class:`_schema.Column`
objects or their string identifiers (specifically the "key" of the
:class:`_schema.Column`, normally but not necessarily equivalent to
its "name"). Normally, the
:class:`_schema.Column` objects used here are expected to be
part of the target :class:`_schema.Table` that is the table
to be updated. However when using MySQL, a multiple-table
UPDATE statement can refer to columns from any of
the tables referred to in the WHERE clause.
The values referred to in ``values`` are typically:
* a literal data value (i.e. string, number, etc.)
* a SQL expression, such as a related :class:`_schema.Column`,
a scalar-returning :func:`_expression.select` construct,
etc.
When combining :func:`_expression.select` constructs within the values
clause of an :func:`_expression.update` construct,
the subquery represented by the :func:`_expression.select` should be
*correlated* to the parent table, that is, providing criterion
which links the table inside the subquery to the outer table
being updated::
users.update().values(
name=select([addresses.c.email_address]).\
where(addresses.c.user_id==users.c.id).\
as_scalar()
)
.. seealso::
:ref:`inserts_and_updates` - SQL Expression
Language Tutorial
N)
r2 r] rd r? rE r
_whereclauserx ry rD ) r+ r) whereclauserb rx r@ rc rI rp preserve_parameter_orderrz s r! rd zUpdate.__init__ s b *B&D%:::
# " 0 = =D $D %%j111 / r# c $ | j | j fS dS r| r r} s r! r~ zUpdate.get_children (%' '2r# c h || j fi || _ | j | _ d S r )r r7 rj r s r! r zUpdate._copy_internals s8 !E$"3 : :r : : /..00r# c | j )t | j t | | _ dS t | | _ dS )a Return a new update() construct with the given expression added to
its WHERE clause, joined to the existing clause via AND, if any.
Both :meth:`_dml.Update.where` and :meth:`_dml.Delete.where`
support multiple-table forms, including database-specific
``UPDATE...FROM`` as well as ``DELETE..USING``. For backends that
don't have multiple-table support, a backend agnostic approach
to using multiple tables is to make use of correlated subqueries.
See the linked tutorial sections below for examples.
.. seealso::
:ref:`tutorial_1x_correlated_updates`
:ref:`multi_table_updates`
:ref:`multi_table_deletes`
Nr r r
r+ r s r! wherez Update.where$ N , ( $!#3K#@#@! !D !1 = =D r# c p g }t t j | j }|d h}| j `t | j D ]K}| |j s| | | |j L|
|dd |S )Nr- r ) r% sql_utiltables_from_leftmostr) r r intersection _cloned_setappendrk ri )r+ froms
all_tablesseenitems r! _extra_fromszUpdate._extra_fromsA s (7
CCDD
1
(%d&788
.
.(()9:: 'LL&&& D ,----
Z^$$$ r# )NNFNNNFF)
rR rS rT rU rV rd r~ r r r r r[ r r r# r! r r s N
!&{0 {0 {0 {0z %+ 1 1 1 1
> > [>8
X
r# r c b e Zd ZdZdZ d dZd Zed Ze d Z
e fdZ dS )
DeletezRepresent a DELETE construct.
The :class:`_expression.Delete`
object is created using the :func:`delete()`
function.
deleteNc || _ t | | _ || _ |r| | |t | | _ nd| _ | | dS )a= Construct :class:`_expression.Delete` object.
Similar functionality is available via the
:meth:`_expression.TableClause.delete` method on
:class:`_schema.Table`.
:param table: The table to delete rows from.
:param whereclause: Optional SQL expression describing the ``WHERE``
condition of the ``DELETE`` statement; is equivalent to using the
more modern :meth:`~Delete.where()` method to specify the ``WHERE``
clause.
.. seealso::
:ref:`deletes` - SQL Expression Tutorial
N)r? r r) rE ra r
r ry )r+ r) r r@ rI rc rz s r! rd zDelete.__init__] sx 6
'..
# + * * * " 0 = =D $D %%j11111r# c $ | j | j fS dS r| r r} s r! r~ zDelete.get_children r r# c | j )t | j t | | _ dS t | | _ dS )a Add the given WHERE clause to a newly returned delete construct.
Both :meth:`_dml.Update.where` and :meth:`_dml.Delete.where`
support multiple-table forms, including database-specific
``UPDATE...FROM`` as well as ``DELETE..USING``. For backends that
don't have multiple-table support, a backend agnostic approach
to using multiple tables is to make use of correlated subqueries.
See the linked tutorial sections below for examples.
.. seealso::
:ref:`tutorial_1x_correlated_updates`
:ref:`multi_table_updates`
:ref:`multi_table_deletes`
Nr r s r! r z Delete.where r r# c g }| j h}| j `t | j D ]K}| |j s| | | |j L|S r )r) r r r r r rk )r+ r r r s r! r zDelete._extra_froms s{
| (%d&788
.
.(()9:: 'LL&&& D ,---- r# c , || j fi || _ d S r r r s r! r zDelete._copy_internals s% !E$"3 : :r : :r# )NNNN)
rR rS rT rU rV rd r~ r r r[ r r r r r# r! r r R s N
'2 '2 '2 '2R > > [>8
X
%+ ; ; ; ; ; ;r# r N)rU r r baser r r r elementsr r r
r r r
rO r r r r r r r] rs r r r r# r! r s^
$ $ $ $ $ $ & & & & & & # # # # # # * * * * * * , , , , , , # # # # # # rL rL rL rL rL
M;
MrL rL rLjY- Y- Y- Y- Y- Y- Y- Y-x^. ^. ^. ^. ^.Z ^. ^. ^.B~ ~ ~ ~ ~Z ~ ~ ~Bf; f; f; f; f;Z f; f; f; f; f;r#