File: //usr/local/lib/python3.10/dist-packages/sqlalchemy/sql/__pycache__/dml.cpython-310.pyc
o
���gb � @ s> d Z ddlmZ ddlmZ ddlZddlmZ ddlm Z ddlm
Z
ddlm Z ddlm Z dd lm
Z
dd
lmZ dd lmZ dd lmZ dd
lmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddl m Z ddl m Z ddl m Z ddl m!Z! dd l"m#Z# dd l"m$Z$ dd l"m%Z% dd l"m&Z& dd l"m'Z' dd!l"m(Z( dd"l"m)Z) dd#l"m*Z* dd$l"m+Z+ dd%l"m,Z, dd&l"m-Z- dd'l"m.Z. dd(l/m0Z0 dd)l/m1Z1 dd*l/m2Z2 dd+l/m3Z3 dd,l/m4Z4 dd-l5m6Z6 dd.l5m7Z7 dd/l5m8Z8 dd0l5m9Z9 dd1l5m:Z: dd2l5m;Z; dd3l5m<Z< dd4l5m=Z= dd5l5m>Z> dd6l?m@Z@ dd7lAmBZB d8d9lmCZC d8dlmZ d8d:lDmEZE d8d;lDmFZF e�r�dd<l mGZG dd=l mHZH dd>l mIZI dd?l mJZJ dd@l mKZK ddAl mLZL ddBl mMZM ddCl mNZN ddDl mOZO ddEl mPZP ddFl mQZQ ddGl mRZR ddHl mSZS ddIl mTZU ddJl"mVZV ddKlWmXZX ddLl/mYZY ddMl5mZZZ ddNl5m[Z[ ddOl5m\Z\ ddPl5m]Z] d|dUdV�Z^d}dXdY�Z_d~d[d\�Z`ne�adV�Z^e�adY�Z_e�ad\�Z`ed]ed^�Zbeece2e f Zdee=e6e;f ZeG d_dR� dRe*�Zfe*�gd`da�G dbdc� dcef��Zhe*�gd`dd�G dedf� dfef��Zie*�gd`dg�G dhdi� dief��ZjG djdk� dkejke9e.e+e:e-e7e1�
ZlG dldm� dmel�ZmG dndo� doem�ZnG dpdq� dqene>e �ZoG drds� ds�ZpG dtdu� duepem�ZqG dvdw� dweqe>e �ZrG dxdy� dyepel�ZsG dzd{� d{eqe>e �ZtdS )zd
Provide :class:`_expression.Insert`, :class:`_expression.Update` and
:class:`_expression.Delete`.
� )� annotationsN)�Any)�cast)�Dict)�Iterable)�List)�MutableMapping)�NoReturn)�Optional)�overload)�Sequence)�Set)�Tuple)�Type)�
TYPE_CHECKING)�TypeVar)�Union� )� coercions)�roles)�util)�_TP)�_unexpected_kw)�is_column_element)�is_named_from_clause��_entity_namespace_key)�_exclusive_against)�
_from_objects)� _generative)�_select_iterables)�ColumnCollection)� ColumnSet)� CompileState)�
DialectKWArgs)�
Executable)�
Generative)�HasCompileState)�BooleanClauseList)�
ClauseElement)� ColumnClause)�
ColumnElement��Null)�Alias)�ExecutableReturnsRows)�
FromClause)�HasCTE)� HasPrefixes)�Join)�SelectLabelStyle)� TableClause)�TypedReturnsRows)�NullType)�InternalTraversal� )�exc)�Self)� TypeGuard)�_ColumnExpressionArgument)�_ColumnsClauseArgument)�_DMLColumnArgument)�_DMLColumnKeyMapping)�_DMLTableArgument)�_T0)�_T1)�_T2)�_T3)�_T4)�_T5)�_T6)�_T7)�_TypedColumnClauseArgument)�ReadOnlyColumnCollection)� SQLCompiler)�KeyedColumnElement)�_ColumnsClauseElement)�_SelectIterable)�Select)�
Selectable�dml�DMLState�return�TypeGuard[UpdateDMLState]c C � d S �N� �rR rX rX �=/usr/local/lib/python3.10/dist-packages/sqlalchemy/sql/dml.py�isupdate` � r[ �TypeGuard[DeleteDMLState]c C rV rW rX rY rX rX rZ �isdeleteb r\ r^ �TypeGuard[InsertDMLState]c C rV rW rX rY rX rX rZ �isinsertd r\ r` �_T)�boundc @ s� e Zd ZU dZdZded< dZded< dZded< dZd ed
< d ed < dZ d
Z
d
Z d
Z ded< d?dd�Z
ed@dd��ZedAdd ��ZedBd d ��ZerRedCd"d#��ZedDd'd(��ZedEd.d/��ZdFd2d3�ZdGd6d7�ZdGd8d9�ZdHd;d<�ZdId=d>�ZdS )JrS TNz0Optional[MutableMapping[_DMLColumnElement, Any]]�_dict_parametersz6Optional[List[MutableMapping[_DMLColumnElement, Any]]]�_multi_parameters�-Optional[List[Tuple[_DMLColumnElement, Any]]]�_ordered_valuesz!Optional[List[_DMLColumnElement]]�_parameter_orderingr0 �_primary_tableF�
UpdateBase� statement�compilerrL �kwr c K s t � �rW ��NotImplementedError)�selfrj rk rl rX rX rZ �__init__� s zDMLState.__init__rT �Dict[str, Any]c C s t |j�r |jjnd |jd�S )N)�name�table)r rs rr ��clsrj rX rX rZ �get_entity_description� s
��z DMLState.get_entity_description�List[Dict[str, Any]]c C s dd� |j D �S )Nc S s g | ]
}|j |j|d ��qS ))rr �type�expr)�keyrx ��.0�crX rX rZ �
<listcomp>� s ���z>DMLState.get_returning_column_descriptions.<locals>.<listcomp>)�_all_selected_columnsrt rX rX rZ �!get_returning_column_descriptions� s �z*DMLState.get_returning_column_descriptions�_DMLTableElementc C s | j jS rW )rj rs �ro rX rX rZ � dml_table� s zDMLState.dml_tabler% �Type[DMLState]c C rV rW rX rt rX rX rZ �get_plugin_class� s zDMLState.get_plugin_class�multi_kv_iterator�'Iterable[Dict[_DMLColumnArgument, Any]]�"List[Dict[_DMLColumnElement, Any]]c C s dd� |D �S )Nc S s g | ] }d d� |� � D ��qS )c S s i | ] \}}t �tj|�|�qS rX �r �expectr �
DMLColumnRole�r| �k�vrX rX rZ �
<dictcomp>� s ��z@DMLState._get_multi_crud_kv_pairs.<locals>.<listcomp>.<dictcomp>)�items)r| �mappingrX rX rZ r~ � s ���z5DMLState._get_multi_crud_kv_pairs.<locals>.<listcomp>rX )ru rj r� rX rX rZ �_get_multi_crud_kv_pairs� s �z!DMLState._get_multi_crud_kv_pairs� kv_iterator�(Iterable[Tuple[_DMLColumnArgument, Any]]�needs_to_be_cacheable�bool�#List[Tuple[_DMLColumnElement, Any]]c s � fdd�|D �S )Nc s< g | ]\}}t �tj|�� s|n
t jtj|t� d d�f�qS )T)�type_�is_crud)r r� r r� �ExpressionElementRoler7 r� �r� rX rZ r~ � s �����z/DMLState._get_crud_kv_pairs.<locals>.<listcomp>rX )ru rj r� r� rX r� rZ �_get_crud_kv_pairs� s
�zDMLState._get_crud_kv_pairs� DMLWhereBase�#Tuple[FromClause, List[FromClause]]c C s� g }t t�|j��}|d }|h}|j}| jr |t| j�� �7 }|D ]}t|�D ]}|� |j
�s5|� |� |� |j
� q(q"|�
|dd � � ||fS )Nr r )�list�sql_util�tables_from_leftmostrs �_where_criteriarc �tuple�valuesr � intersection� _cloned_set�append�update�extend) ro rj �froms�
all_tables�
primary_table�seen�consider�crit�itemrX rX rZ �_make_extra_froms� s
�zDMLState._make_extra_froms�
ValuesBase�Nonec C s | j r |j| _d| _ d S d S �NF)�_no_parameters�_valuesrc �ro rj rX rX rZ �_process_values� s
�zDMLState._process_valuesc C s< |j d usJ �dd� |j D �}| jrd| _|| _d S J d��)Nc S s i | ]}|t � �qS rX r, �r| rr rX rX rZ r� � s �z3DMLState._process_select_values.<locals>.<dictcomp>Fz%This statement already has parameters)�
_select_namesr� rc �ro rj �
parametersrX rX rZ �_process_select_values� s �
z DMLState._process_select_valuesr c C s t �d|j�� ��)Nz6%s construct does not support multiple parameter sets.)r: �InvalidRequestError�__visit_name__�upperr� rX rX rZ �_no_multi_values_supported� s
��z#DMLState._no_multi_values_supportedc C s
t �d��)Nz�Can't mix single and multiple VALUES formats in one INSERT statement; one style appends to a list while the other replaces values, so the intent is ambiguous.)r: r� r� rX rX rZ �_cant_mix_formats_error� s �z DMLState._cant_mix_formats_error)rj ri rk rL rl r )rj ri rT rq )rj ri rT rw �rT r� )rj r% rT r� )rj ri r� r� rT r� )rj ri r� r� r� r� rT r� )rj r� rT r� �rj r� rT r� )rj r� rT r )rT r ) �__name__�
__module__� __qualname__r� rc �__annotations__rd rf rg � _supports_implicit_returningr[ r^ r` rp � classmethodrv r� �propertyr� r r� r� r� r� r� r� r� r� rX rX rX rZ rS r s@
�
�default�insertc @ sJ e Zd ZdZdZdZ ddd d �Zejddd��Z ddd�Z
ddd�Z dS ) �InsertDMLStateTFrj �Insertrk rL �disable_implicit_returningr� rl r c K sZ || _ |j| _|r d| _d| _|jr| �|� |jd ur!| �|� |j r+| �
|� d S d S )NFT) rj rs rh r� r` r� r� r� r� �
_multi_values�_process_multi_values)ro rj rk r� rl rX rX rZ rp s
�zInsertDMLState.__init__rT � List[str]c C s dd� | j pdD �S )Nc S � g | ] }t jtj|d d��qS �T)�as_keyr� �r| �colrX rX rZ r~ ' � ��z3InsertDMLState._insert_col_keys.<locals>.<listcomp>rX )rc r� rX rX rZ �_insert_col_keys$ s �z InsertDMLState._insert_col_keysr� r� c C s4 | j rd| _|j| _d| _ d S | jr| �� d S d S r� )r� �_has_multi_parametersr� rc r� r� rX rX rZ r� , s
�z InsertDMLState._process_valuesc sn � j D ]1}� fdd�|D �}| jr!d| _d| _|| _| jd | _q| js)| �� q| js.J �| j�|� qd S )Nc s4 g | ]}t |tj�rd d� t� jj|�D �n|�qS )c S � i | ]\}}|j |�qS rX �rz �r| r} �valuerX rX rZ r� 8 s ��zCInsertDMLState._process_multi_values.<locals>.<listcomp>.<dictcomp>)�
isinstance�collections_abcr �ziprs r} )r| �
parameter_set�rj rX rZ r~ 6 s
�� ��z8InsertDMLState._process_multi_values.<locals>.<listcomp>FTr )r� r� r� rd rc r� r� )ro rj r� �multi_parametersrX r� rZ r� 4 s
�
�z$InsertDMLState._process_multi_valuesN�F)rj r� rk rL r� r� rl r )rT r� r� ) r� r� r� r` � include_table_with_column_exprsr� rp r �memoized_propertyr� r� r� rX rX rX rZ r� s �
r� r� c @ s( e Zd ZdZdZdd d
�Zddd�ZdS )�UpdateDMLStateTFrj �Updaterk rL rl r c K s� || _ d| _|jd ur| �|� n|jd ur | �|� n|jr$| �|� | �|�\}}|| _ || _
| | _ }t |o;|j
�| _d S �NT)rj r[ rf �_process_ordered_valuesr� r� r� r� r� rh � _extra_froms�
is_multitabler� �'render_table_with_column_in_update_fromr� )ro rj rk rl �t�ef�mtrX rX rZ rp T s
�zUpdateDMLState.__init__r� rT r� c C sL |j }| jr!d| _|d usJ �t|�| _|| _ dd� |D �| _d S t�d��)NFc S s g | ]\}}|�qS rX rX �r| rz r� rX rX rZ r~ o s z:UpdateDMLState._process_ordered_values.<locals>.<listcomp>zQCan only invoke ordered_values() once, and not mixed with any other values() call)rf r� �dictrc rg r: r� r� rX rX rZ r� g s
�z&UpdateDMLState._process_ordered_valuesN)rj r� rk rL rl r r� )r� r� r� r[ r� rp r� rX rX rX rZ r� N s
r� �deletec @ s e Zd ZdZd dd �Zd
S ) �DeleteDMLStateTrj �Deleterk rL rl r c K s0 || _ d| _| �|�\}}|| _|| _|| _d S r� )rj r^ r� rh r� r� )ro rj rk rl r� r� rX rX rZ rp { s
zDeleteDMLState.__init__N)rj r� rk rL rl r )r� r� r� r^ rp rX rX rX rZ r� w s r� c @ s e Zd ZU dZdZejZded< dZ e
j Z ded< ded < dZ
d
Zd ed < d
Zd ed
< dZded< dZdPd d �ZdQd"d#�ZedRd&d'��Zed
dd(�dSd/d0��Zedd1�dTd4d5��Z dUdVd:d;�ZejdWd=d>��ZejdXd@dA��Ze
BdYdZdHdI��Z e d[dKdL��Z e d\dNdO��Z d
S )]ri zDForm the base for ``INSERT``, ``UPDATE``, and ``DELETE`` statements.� update_basez5util.immutabledict[Tuple[_DMLTableElement, str], str]�_hintsFr4 � _label_styler� rs Nz+Optional[Tuple[_ColumnsClauseElement, ...]]�_return_defaults_columns�_supplemental_returningrX z!Tuple[_ColumnsClauseElement, ...]�
_returningT�
fromclauser0 �columns�.ColumnCollection[str, KeyedColumnElement[Any]]� primary_keyr" � foreign_keys� Set[KeyedColumnElement[Any]]rT r� c s" |� � ��fdd�| jD �� d S )Nc 3 s( � | ]}t |�r|j��� d �V qdS ))r r N)r � _make_proxyr� �r r� r rX rZ � <genexpr>� s � ��
�zAUpdateBase._generate_fromclause_column_proxies.<locals>.<genexpr>)�_populate_separate_keysr )ro r� r� r r rX r rZ �#_generate_fromclause_column_proxies� s �z.UpdateBase._generate_fromclause_column_proxies�argr rl r c O s t d��)z�Set 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.
z�params() is not supported for INSERT/UPDATE/DELETE statements. To set the values for an INSERT or UPDATE statement, use stmt.values(**parameters).rm )ro r rl rX rX rZ �params� s �zUpdateBase.params�optr; c K s | � |� | S )a Add dialect options to this INSERT/UPDATE/DELETE object.
e.g.::
upd = table.update().dialect_options(mysql_limit=10)
.. versionadded: 1.4 - this method supersedes the dialect options
associated with the constructor.
)�_validate_dialect_kwargs)ro r rX rX rZ �with_dialect_options� s
z UpdateBase.with_dialect_options)�supplemental_cols�sort_by_parameter_order�colsr? r �&Optional[Iterable[_DMLColumnArgument]]r r� c G s� | j r | jr|rtt�| j��dd� |D ���| _nd| _n
tdd� |D ��| _d| _ |r8| js5t�d��d| _ |r]dd� |D �}| j
du rPtt� |��| _
| S tt� | j
t|� ��| _
| S ) aA$ Make use of a :term:`RETURNING` clause for the purpose
of fetching server-side expressions and defaults, for supporting
backends only.
.. deepalchemy::
The :meth:`.UpdateBase.return_defaults` method is used by the ORM
for its internal work in fetching newly generated primary key
and server default values, in particular to provide the underyling
implementation of the :paramref:`_orm.Mapper.eager_defaults`
ORM feature as well as to allow RETURNING support with bulk
ORM inserts. Its behavior is fairly idiosyncratic
and is not really intended for general use. End users should
stick with using :meth:`.UpdateBase.returning` in order to
add RETURNING clauses to their INSERT, UPDATE and DELETE
statements.
Normally, a single row INSERT statement will automatically populate the
:attr:`.CursorResult.inserted_primary_key` attribute when executed,
which stores the primary key of the row that was just inserted in the
form of a :class:`.Row` object with column names as named tuple keys
(and the :attr:`.Row._mapping` view fully populated as well). The
dialect in use chooses the strategy to use in order to populate this
data; if it was generated using server-side defaults and / or SQL
expressions, dialect-specific approaches such as ``cursor.lastrowid``
or ``RETURNING`` are typically used to acquire the new primary key
value.
However, when the statement is modified by calling
:meth:`.UpdateBase.return_defaults` before executing the statement,
additional behaviors take place **only** for backends that support
RETURNING and for :class:`.Table` objects that maintain the
:paramref:`.Table.implicit_returning` parameter at its default value of
``True``. In these cases, when the :class:`.CursorResult` is returned
from the statement's execution, not only will
:attr:`.CursorResult.inserted_primary_key` be populated as always, the
:attr:`.CursorResult.returned_defaults` attribute will also be
populated with a :class:`.Row` named-tuple representing the full range
of server generated
values from that single row, including values for any columns that
specify :paramref:`_schema.Column.server_default` or which make use of
:paramref:`_schema.Column.default` using a SQL expression.
When invoking INSERT statements with multiple rows using
:ref:`insertmanyvalues <engine_insertmanyvalues>`, the
:meth:`.UpdateBase.return_defaults` modifier will have the effect of
the :attr:`_engine.CursorResult.inserted_primary_key_rows` and
:attr:`_engine.CursorResult.returned_defaults_rows` attributes being
fully populated with lists of :class:`.Row` objects representing newly
inserted primary key values as well as newly inserted server generated
values for each row inserted. The
:attr:`.CursorResult.inserted_primary_key` and
:attr:`.CursorResult.returned_defaults` attributes will also continue
to be populated with the first row of these two collections.
If the backend does not support RETURNING or the :class:`.Table` in use
has disabled :paramref:`.Table.implicit_returning`, then no RETURNING
clause is added and no additional data is fetched, however the
INSERT, UPDATE or DELETE statement proceeds normally.
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 an UPDATE statement
:meth:`.UpdateBase.return_defaults` instead looks for columns that
include :paramref:`_schema.Column.onupdate` or
:paramref:`_schema.Column.server_onupdate` parameters assigned, when
constructing the columns that will be included in the RETURNING clause
by default if explicit columns were not specified. When used against a
DELETE statement, no columns are included in RETURNING by default, they
instead must be specified explicitly as there are no columns that
normally change values when a DELETE statement proceeds.
.. versionadded:: 2.0 :meth:`.UpdateBase.return_defaults` is supported
for DELETE statements also and has been moved from
:class:`.ValuesBase` to :class:`.UpdateBase`.
The :meth:`.UpdateBase.return_defaults` method is mutually exclusive
against the :meth:`.UpdateBase.returning` method and errors will be
raised during the SQL compilation process if both are used at the same
time on one statement. The RETURNING clause of the INSERT, UPDATE or
DELETE statement is therefore controlled by only one of these methods
at a time.
The :meth:`.UpdateBase.return_defaults` method differs from
:meth:`.UpdateBase.returning` in these ways:
1. :meth:`.UpdateBase.return_defaults` method causes the
:attr:`.CursorResult.returned_defaults` collection to be populated
with the first row from the RETURNING result. This attribute is not
populated when using :meth:`.UpdateBase.returning`.
2. :meth:`.UpdateBase.return_defaults` is compatible with existing
logic used to fetch auto-generated primary key values that are then
populated into the :attr:`.CursorResult.inserted_primary_key`
attribute. By contrast, using :meth:`.UpdateBase.returning` will
have the effect of the :attr:`.CursorResult.inserted_primary_key`
attribute being left unpopulated.
3. :meth:`.UpdateBase.return_defaults` can be called against any
backend. Backends that don't support RETURNING will skip the usage
of the feature, rather than raising an exception, *unless*
``supplemental_cols`` is passed. The return value
of :attr:`_engine.CursorResult.returned_defaults` will be ``None``
for backends that don't support RETURNING or for which the target
:class:`.Table` sets :paramref:`.Table.implicit_returning` to
``False``.
4. An INSERT statement invoked with executemany() is supported if the
backend database driver supports the
:ref:`insertmanyvalues <engine_insertmanyvalues>`
feature which is now supported by most SQLAlchemy-included backends.
When executemany is used, the
:attr:`_engine.CursorResult.returned_defaults_rows` and
:attr:`_engine.CursorResult.inserted_primary_key_rows` accessors
will return the inserted defaults and primary keys.
.. versionadded:: 1.4 Added
:attr:`_engine.CursorResult.returned_defaults_rows` and
:attr:`_engine.CursorResult.inserted_primary_key_rows` accessors.
In version 2.0, the underlying implementation which fetches and
populates the data for these attributes was generalized to be
supported by most backends, whereas in 1.4 they were only
supported by the ``psycopg2`` driver.
:param cols: optional list of column key names or
:class:`_schema.Column` that acts as a filter for those columns that
will be fetched.
:param supplemental_cols: optional list of RETURNING expressions,
in the same form as one would pass to the
:meth:`.UpdateBase.returning` method. When present, the additional
columns will be included in the RETURNING clause, and the
:class:`.CursorResult` object will be "rewound" when returned, so
that methods like :meth:`.CursorResult.all` will return new rows
mostly as though the statement used :meth:`.UpdateBase.returning`
directly. However, unlike when using :meth:`.UpdateBase.returning`
directly, the **order of the columns is undefined**, so can only be
targeted using names or :attr:`.Row._mapping` keys; they cannot
reliably be targeted positionally.
.. versionadded:: 2.0
:param sort_by_parameter_order: for a batch INSERT that is being
executed against multiple parameter sets, organize the results of
RETURNING so that the returned rows correspond to the order of
parameter sets passed in. This applies only to an :term:`executemany`
execution for supporting dialects and typically makes use of the
:term:`insertmanyvalues` feature.
.. versionadded:: 2.0.10
.. seealso::
:ref:`engine_insertmanyvalues_returning_order` - background on
sorting of RETURNING rows for bulk INSERT
.. seealso::
:meth:`.UpdateBase.returning`
:attr:`_engine.CursorResult.returned_defaults`
:attr:`_engine.CursorResult.returned_defaults_rows`
:attr:`_engine.CursorResult.inserted_primary_key`
:attr:`_engine.CursorResult.inserted_primary_key_rows`
c s � � | ]
}t �tj|�V qd S rW �r r� r �ColumnsClauseRoler{ rX rX rZ r � �
� �
�z-UpdateBase.return_defaults.<locals>.<genexpr>rX c s r rW r r{ rX rX rZ r � � �
�Tz]The 'sort_by_parameter_order' argument to return_defaults() only applies to INSERT statementsc s r rW r r{ rX rX rZ r � r N) �_return_defaultsr� r� r �
OrderedSet�union� is_insertr: �
ArgumentError�_sort_by_parameter_orderr� � unique_list)ro r r r �supplemental_col_tuprX rX rZ �return_defaults� sH 8
��
���
� ����zUpdateBase.return_defaults�r �_ColumnsClauseArgument[Any]�_UpdateBase__kwc O sX |rt d|��| jrt�d��| jtdd� |D ��7 _|r*| js't�d��d| _| S )aR Add a :term:`RETURNING` or equivalent clause to this statement.
e.g.:
.. sourcecode:: pycon+sql
>>> stmt = (
... table.update()
... .where(table.c.data == "value")
... .values(status="X")
... .returning(table.c.server_flag, table.c.updated_timestamp)
... )
>>> print(stmt)
{printsql}UPDATE some_table SET status=:status
WHERE some_table.data = :data_1
RETURNING some_table.server_flag, some_table.updated_timestamp
The method may be invoked multiple times to add new entries to the
list of expressions to be returned.
.. versionadded:: 1.4.0b2 The method may be invoked multiple times to
add new entries to the list of expressions to be returned.
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:
.. sourcecode:: pycon+sql
>>> stmt = table.insert().returning(
... (table.c.first_name + " " + table.c.last_name).label("fullname")
... )
>>> print(stmt)
{printsql}INSERT INTO some_table (first_name, last_name)
VALUES (:first_name, :last_name)
RETURNING some_table.first_name || :first_name_1 || some_table.last_name AS 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.CursorResult.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.
:param \*cols: series of columns, SQL expressions, or whole tables
entities to be returned.
:param sort_by_parameter_order: for a batch INSERT that is being
executed against multiple parameter sets, organize the results of
RETURNING so that the returned rows correspond to the order of
parameter sets passed in. This applies only to an :term:`executemany`
execution for supporting dialects and typically makes use of the
:term:`insertmanyvalues` feature.
.. versionadded:: 2.0.10
.. seealso::
:ref:`engine_insertmanyvalues_returning_order` - background on
sorting of RETURNING rows for bulk INSERT (Core level discussion)
:ref:`orm_queryguide_bulk_insert_returning_ordered` - example of
use with :ref:`orm_queryguide_bulk_insert` (ORM level discussion)
.. seealso::
:meth:`.UpdateBase.return_defaults` - an alternative method tailored
towards efficient fetching of server-side defaults and triggers
for single-row INSERTs or UPDATEs.
:ref:`tutorial_insert_returning` - in the :ref:`unified_tutorial`
zUpdateBase.returning()z9return_defaults() is already configured on this statementc s r rW r r{ rX rX rZ r r z'UpdateBase.returning.<locals>.<genexpr>zWThe 'sort_by_parameter_order' argument to returning() only applies to INSERT statementsT) r r r: r� r� r� r r r )ro r r r" rX rX rZ � returning� s _
� ��zUpdateBase.returning�column�KeyedColumnElement[Any]�require_embedded� Optional[ColumnElement[Any]]c C s | j j||d�S )N)r& )�exported_columns�corresponding_column)ro r$ r& rX rX rZ r) + s �z UpdateBase.corresponding_columnrO c C s dd� t | j�D �S )Nc S s g | ]}|�qS rX rX r{ rX rX rZ r~ 4 s z4UpdateBase._all_selected_columns.<locals>.<listcomp>)r r� r� rX rX rZ r 2 s z UpdateBase._all_selected_columns�;ReadOnlyColumnCollection[Optional[str], ColumnElement[Any]]c C s t dd� | jD ���� S )zxReturn the RETURNING columns as a column collection for this
statement.
.. versionadded:: 1.4
c s s" � | ] }t |�r|j|fV qd S rW )r rz r{ rX rX rZ r @ s � �
�z.UpdateBase.exported_columns.<locals>.<genexpr>)r! r � as_readonlyr� rX rX rZ r( 6 s
��zUpdateBase.exported_columns�*�text�str�
selectable�Optional[_DMLTableArgument]� dialect_namec C s8 |du r| j }nt�tj|�}| j�||f|i�| _| S )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)rs r r� r � DMLTableRoler� r )ro r- r/ r1 rX rX rZ � with_hintF s
$zUpdateBase.with_hintrq c C � t �| �j}|| �S )a= Return a :term:`plugin-enabled` description of the table and/or
entity which this DML construct is operating against.
This attribute is generally useful when using the ORM, as an
extended structure which includes information about mapped
entities is returned. The section :ref:`queryguide_inspection`
contains more background.
For a Core statement, the structure returned by this accessor
is derived from the :attr:`.UpdateBase.table` attribute, and
refers to the :class:`.Table` being inserted, updated, or deleted::
>>> stmt = insert(user_table)
>>> stmt.entity_description
{
"name": "user_table",
"table": Table("user_table", ...)
}
.. versionadded:: 1.4.33
.. seealso::
:attr:`.UpdateBase.returning_column_descriptions`
:attr:`.Select.column_descriptions` - entity information for
a :func:`.select` construct
:ref:`queryguide_inspection` - ORM background
)rS r� rv �ro �methrX rX rZ �entity_descriptionq s !z UpdateBase.entity_descriptionrw c C r4 )a� Return a :term:`plugin-enabled` description of the columns
which this DML construct is RETURNING against, in other words
the expressions established as part of :meth:`.UpdateBase.returning`.
This attribute is generally useful when using the ORM, as an
extended structure which includes information about mapped
entities is returned. The section :ref:`queryguide_inspection`
contains more background.
For a Core statement, the structure returned by this accessor is
derived from the same objects that are returned by the
:attr:`.UpdateBase.exported_columns` accessor::
>>> stmt = insert(user_table).returning(user_table.c.id, user_table.c.name)
>>> stmt.entity_description
[
{
"name": "id",
"type": Integer,
"expr": Column("id", Integer(), table=<user>, ...)
},
{
"name": "name",
"type": String(),
"expr": Column("name", String(), table=<user>, ...)
},
]
.. versionadded:: 1.4.33
.. seealso::
:attr:`.UpdateBase.entity_description`
:attr:`.Select.column_descriptions` - entity information for
a :func:`.select` construct
:ref:`queryguide_inspection` - ORM background
)rS r� r� r5 rX rX rZ � returning_column_descriptions� s *��z(UpdateBase.returning_column_descriptions)
r� r0 r� r r r" r r rT r� )r r rl r rT r )r r rT r; )r r? r r r r� rT r; )r r! r r� r" r rT ri r� )r$ r% r& r� rT r' )rT rO )rT r* )Nr, )r- r. r/ r0 r1 r. rT r; )rT rq )rT rw ) r� r� r� �__doc__r� r �
EMPTY_DICTr� r� �named_with_columnr4 � LABEL_STYLE_DISAMBIGUATE_ONLYr� r r� r� r� �is_dmlr r
r r
r r# r) �ro_memoized_propertyr r( r3 r� r7 r8 rX rX rX rZ ri � sR
�
�
�
� g�q � �* #ri c @ s� e Zd ZU dZdZdZdZded< dZded< dZ d ed
< d Z
d ed
< dZ ded< dZ ded< dZ
ded< d$dd�Zeeddddd�d�d%d"d#���ZdS )&r� zTSupplies support for :meth:`.ValuesBase.values` to
INSERT and UPDATE constructs.� values_baseFNzOptional[Select[Any]]�selectzOptional[ClauseElement]�_post_values_clausez4Optional[util.immutabledict[_DMLColumnElement, Any]]r� rX zRTuple[Union[Sequence[Dict[_DMLColumnElement, Any]], Sequence[Sequence[Any]]], ...]r� re rf zOptional[List[str]]r� r� �_inliners rA c C � t jtj|| d�| _d S �N��apply_propagate_attrs�r r� r r2 rs �ro rs rX rX rZ rp � � �zValuesBase.__init__z,This construct already inserts from a SELECT�1This statement already has ordered values present)r� rf )�msgs�args�/Union[_DMLColumnKeyMapping[Any], Sequence[Any]]�kwargsr rT r; c O s* |re|d }|r
t �d��t|�dkrt �d��t|tj�rd|r:t|d t�r:t�| �j }| j
|| |�f7 _
| S |rOt|d t t f�rO| j
|f7 _
| S t
rXt| t�sXJ �dd� t| jj|�D �}n td|�}|rqt �d��t�| �j}t|| |�� d��}| jr�| j�|�| _| S t�|�| _| S ) aY 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:
.. sourcecode:: sql
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:`tutorial_multiple_parameters` - an introduction to
the traditional Core method of multiple parameter set
invocation for INSERTs and other statements.
The UPDATE construct also supports rendering the SET parameters
in a specific order. For this feature refer to the
:meth:`_expression.Update.ordered_values` method.
.. seealso::
:meth:`_expression.Update.ordered_values`
r z;Can't pass positional and kwargs to values() simultaneouslyr zWOnly a single dictionary/tuple or list of dictionaries/tuples is accepted positionally.c S r� rX r� r� rX rX rZ r� � s z%ValuesBase.values.<locals>.<dictcomp>z Dict[_DMLColumnArgument, Any]T)r: r �lenr� r� r r� rS r� r� r� r� r� r r� r� rs r} r r� r� r� r r �
immutabledict)ro rL rN r �multi_kv_generator� kv_generator� coerced_argrX rX rZ r� � sL t� � ���
� �zValuesBase.values�rs rA )rL rM rN r rT r; )r� r� r� r9 r� �_supports_multi_parametersr@ r� rA r� r� rf r� rB rp r r r� rX rX rX rZ r� � s0
�
�� r� c
s� e Zd ZU dZdZdZdZdZdZde d< dZ
de d < d e j fd
e j
fd e jfd e jfd
e jfde j fde j fde jfde jfde j
fde jfde j
fg ej ej ej ej ZdK� fdd� Z e dLdd��Z e dMdNd d ��Z e r�e!dd!�dOd&d'��Z"e!dd!�dPd+d'��Z"e!dd!�dQd/d'��Z"e!dd!�dRd3d'��Z"e!dd!�dSd7d'��Z"e!dd!�dTd;d'��Z"e!dd!�dUd?d'��Z"e!dd!�dVdCd'��Z"e!dd!�dWdId'��Z"dd!�dWdJd'�Z"� Z#S � Z#S )Xr� z�Represent an INSERT construct.
The :class:`_expression.Insert` object is created using the
:func:`_expression.insert()` function.
r� TNFr� r r5 rs rB r� r� r� r@ rA r� r� r r� rA c � t � �|� d S rW ��superrp rH �� __class__rX rZ rp � � zInsert.__init__rT r; c C �
d| _ | S )a� Make this :class:`_expression.Insert` construct "inline" .
When set, 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.
.. versionchanged:: 1.4 the :paramref:`_expression.Insert.inline`
parameter
is now superseded by the :meth:`_expression.Insert.inline` method.
T�rB r� rX rX rZ �inline� s z
Insert.inline�names� Sequence[_DMLColumnArgument]rQ �include_defaultsc C s@ | j rt�d��dd� |D �| _d| _|| _t�tj |�| _
| S )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**.
z0This construct already inserts value expressionsc S r� r� r� r� rX rX rZ r~ r� z&Insert.from_select.<locals>.<listcomp>T) r� r: r� r� rB �#include_insert_from_select_defaultsr r� r �
DMLSelectRoler@ )ro r_ r@ ra rX rX rZ � from_select� s )��zInsert.from_selectr �
_Insert__ent0�
_TCCA[_T0]r �ReturningInsert[Tuple[_T0]]c C rV rW rX )ro re r rX rX rZ r# � zInsert.returning�
_Insert__ent1�
_TCCA[_T1]� ReturningInsert[Tuple[_T0, _T1]]c C rV rW rX )ro re ri r rX rX rZ r# " � �
_Insert__ent2�
_TCCA[_T2]�%ReturningInsert[Tuple[_T0, _T1, _T2]]c C rV rW rX )ro re ri rm r rX rX rZ r# + � �
_Insert__ent3�
_TCCA[_T3]�*ReturningInsert[Tuple[_T0, _T1, _T2, _T3]]c C rV rW rX )ro re ri rm rq r rX rX rZ r# 5 � �
_Insert__ent4�
_TCCA[_T4]�/ReturningInsert[Tuple[_T0, _T1, _T2, _T3, _T4]]c C rV rW rX )ro re ri rm rq ru r rX rX rZ r# @ �
�
_Insert__ent5�
_TCCA[_T5]�4ReturningInsert[Tuple[_T0, _T1, _T2, _T3, _T4, _T5]]c C rV rW rX )ro re ri rm rq ru ry r rX rX rZ r# L s �
_Insert__ent6�
_TCCA[_T6]�9ReturningInsert[Tuple[_T0, _T1, _T2, _T3, _T4, _T5, _T6]]c C rV rW rX ) ro re ri rm rq ru ry r| r rX rX rZ r# Y s �
_Insert__ent7�
_TCCA[_T7]�>ReturningInsert[Tuple[_T0, _T1, _T2, _T3, _T4, _T5, _T6, _T7]]c
C rV rW rX )
ro re ri rm rq ru ry r| r r rX rX rZ r# g s r r! � _Insert__kwr �ReturningInsert[Any]c O rV rW rX �ro r r r� rX rX rZ r# z s c O rV rW rX r� rX rX rZ r# � s rT �rT r; )T)r_ r` r@ rQ ra r� rT r; )re rf r r� rT rg )re rf ri rj r r� rT rk )
re rf ri rj rm rn r r� rT ro ) re rf ri rj rm rn rq rr r r� rT rs )re rf ri rj rm rn rq rr ru rv r r� rT rw )re rf ri rj rm rn rq rr ru rv ry rz r r� rT r{ )re rf ri rj rm rn rq rr ru rv ry rz r| r} r r� rT r~ )re rf ri rj rm rn rq rr ru rv ry rz r| r} r r� r r� rT r� )r r! r r� r� r rT r� )$r� r� r� r9 r� rU r@ rb r r� r r8 �dp_clauseelement�
dp_boolean�dp_string_list�
dp_dml_values�dp_dml_multi_values�dp_clauseelement_tuple�dp_table_hint_listr2 � _has_prefixes_traverse_internalsr$ �"_dialect_kwargs_traverse_internalsr% � _executable_traverse_internalsr1 � _has_ctes_traverse_internals�_traverse_internalsrp r r^ rd r r r# �
__classcell__rX rX rY rZ r� � s�
������� �6��� �
�
� �
��
��r� c @ � e Zd ZdZdS )�ReturningInsertz�Typing-only class that establishes a generic type form of
:class:`.Insert` which tracks returned column types.
This datatype is delivered when calling the
:meth:`.Insert.returning` method.
.. versionadded:: 2.0
N�r� r� r� r9 rX rX rX rZ r� � � r� c @ s\ e Zd ZU ded< dZded< edd
d ��Zddd�Zd dd�Zd dd�Z e
d dd��Z dS ) r� r� rs rX z Tuple[ColumnElement[Any], ...]r� � whereclause� _ColumnExpressionArgument[bool]rT r; c G s0 |D ]}t jtj|| d�}| j|f7 _q| S )a� Return a new construct with the given expression(s) 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_correlated_updates`
:ref:`tutorial_update_from`
:ref:`tutorial_multi_table_deletes`
rE )r r� r �WhereHavingRoler� )ro r� � criterion�where_criteriarX rX rZ �where� s �zDMLWhereBase.where�criteria� roles.ExpressionElementRole[Any]c G s
| j |� S )zbA synonym for the :meth:`_dml.DMLWhereBase.where` method.
.. versionadded:: 1.4
)r� )ro r� rX rX rZ �filter� s
zDMLWhereBase.filterc C s | j S rW )rs r� rX rX rZ �_filter_by_zero� s z DMLWhereBase._filter_by_zerorN r c s( | � � � � fdd�|�� D �}| j|� S )zWapply the given filtering criterion as a WHERE clause
to this select.
c s g | ] \}}t � |�|k�qS rX r r� �� from_entityrX rZ r~ � s ��z*DMLWhereBase.filter_by.<locals>.<listcomp>)r� r� r� )ro rN �clausesrX r� rZ � filter_by� s
�
zDMLWhereBase.filter_byr' c C s t �| j�S )a Return the completed WHERE clause for this :class:`.DMLWhereBase`
statement.
This assembles the current collection of WHERE criteria
into a single :class:`_expression.BooleanClauseList` construct.
.. versionadded:: 1.4
)r( �_construct_for_whereclauser� r� rX rX rZ r� � s
�zDMLWhereBase.whereclauseN)r� r� rT r; )r� r� rT r; r� )rN r rT r; )rT r' ) r� r� r� r� r� r r� r� r� r� r� r� rX rX rX rZ r� � s
r� c
s> e Zd ZdZdZdZdejfdejfdej fdej
fdej fd ejfd
ej fd ej fd ejfg e
j ej ej ej Zd@� fdd� ZedAdd��ZedBdd��Zer�edCdd ��Z edDd d ��Z edEd$d ��Z edFd(d ��Z edGd,d ��Z edHd0d ��Z edId4d ��Z edJd8d ��Z edKd>d ��Z dKd?d �Z � Z S � Z S )Lr� z�Represent an Update construct.
The :class:`_expression.Update` object is created using the
:func:`_expression.update()` function.
r� Trs r� rB rf r� r� r� r r� rA c rV rW rW rH rY rX rZ rp r[ zUpdate.__init__rL � Tuple[_DMLColumnArgument, Any]rT r; c G s> | j rt�d��| jrt�d��t�| �j}|| |d�| _| S )a� Specify the VALUES clause of this UPDATE statement with an explicit
parameter ordering that will be maintained in the SET clause of the
resulting UPDATE statement.
E.g.::
stmt = table.update().ordered_values(("name", "ed"), ("ident", "foo"))
.. seealso::
:ref:`tutorial_parameter_ordered_updates` - full example of the
:meth:`_expression.Update.ordered_values` method.
.. versionchanged:: 1.4 The :meth:`_expression.Update.ordered_values`
method
supersedes the
:paramref:`_expression.update.preserve_parameter_order`
parameter, which will be removed in SQLAlchemy 2.0.
z)This statement already has values presentrJ T)r� r: r rf rS r� r� )ro rL rR rX rX rZ �ordered_values s �� zUpdate.ordered_valuesc C r\ )aJ Make this :class:`_expression.Update` construct "inline" .
When set, 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.CursorResult.last_updated_params`.
.. versionchanged:: 1.4 the :paramref:`_expression.update.inline`
parameter
is now superseded by the :meth:`_expression.Update.inline` method.
Tr] r� rX rX rZ r^ ) s z
Update.inline�
_Update__ent0rf �ReturningUpdate[Tuple[_T0]]c C rV rW rX )ro r� rX rX rZ r# B rh zUpdate.returning�
_Update__ent1rj � ReturningUpdate[Tuple[_T0, _T1]]c C rV rW rX )ro r� r� rX rX rZ r# G rh �
_Update__ent2rn �%ReturningUpdate[Tuple[_T0, _T1, _T2]]c C rV rW rX )ro r� r� r� rX rX rZ r# L rh �
_Update__ent3rr �*ReturningUpdate[Tuple[_T0, _T1, _T2, _T3]]c C rV rW rX )ro r� r� r� r� rX rX rZ r# Q rl �
_Update__ent4rv �/ReturningUpdate[Tuple[_T0, _T1, _T2, _T3, _T4]]c C rV rW rX )ro r� r� r� r� r� rX rX rZ r# Z rp �
_Update__ent5rz �4ReturningUpdate[Tuple[_T0, _T1, _T2, _T3, _T4, _T5]]c C rV rW rX )ro r� r� r� r� r� r� rX rX rZ r# d rt �
_Update__ent6r} �9ReturningUpdate[Tuple[_T0, _T1, _T2, _T3, _T4, _T5, _T6]]c C rV rW rX )ro r� r� r� r� r� r� r� rX rX rZ r# o rx �
_Update__ent7r� �>ReturningUpdate[Tuple[_T0, _T1, _T2, _T3, _T4, _T5, _T6, _T7]]c C rV rW rX ) ro r� r� r� r� r� r� r� r� rX rX rZ r# { �
r r! � _Update__kwr �ReturningUpdate[Any]c O rV rW rX �ro r r� rX rX rZ r# � rh c O rV rW rX r� rX rX rZ r# � � rT )rL r� rT r; r� )r� rf rT r� )r� rf r� rj rT r� )r� rf r� rj r� rn rT r� )
r� rf r� rj r� rn r� rr rT r� ) r� rf r� rj r� rn r� rr r� rv rT r� )r� rf r� rj r� rn r� rr r� rv r� rz rT r� )r� rf r� rj r� rn r� rr r� rv r� rz r� r} rT r� )r� rf r� rj r� rn r� rr r� rv r� rz r� r} r� r� rT r� )r r! r� r rT r� ) r� r� r� r9 r� � is_updater8 r� r� r� �dp_dml_ordered_valuesr� r� r2 r� r$ r� r% r� r1 r� r� rp r r� r^ r r r# r� rX rX rY rZ r� � sf ������� "
�r� c @ r� )�ReturningUpdatez�Typing-only class that establishes a generic type form of
:class:`.Update` which tracks returned column types.
This datatype is delivered when calling the
:meth:`.Update.returning` method.
.. versionadded:: 2.0
Nr� rX rX rX rZ r� � r� r� c @ s� e Zd ZdZdZdZdejfdejfdejfdej fge
j e j
ej ej Zd5d d
�Zerued6dd��Zed7dd��Zed8dd��Zed9d d��Zed:d d��Zed;d$d��Zed<d(d��Zed=d,d��Zed>d2d��Zd>d3d�Zd4S d4S )?r� z�Represent a DELETE construct.
The :class:`_expression.Delete` object is created using the
:func:`_expression.delete()` function.
r� Trs r� r� r� rA c C rC rD rG rH rX rX rZ rp � rI zDelete.__init__�
_Delete__ent0rf rT �ReturningDelete[Tuple[_T0]]c C rV rW rX )ro r� rX rX rZ r# � rh zDelete.returning�
_Delete__ent1rj � ReturningDelete[Tuple[_T0, _T1]]c C rV rW rX )ro r� r� rX rX rZ r# � rh �
_Delete__ent2rn �%ReturningDelete[Tuple[_T0, _T1, _T2]]c C rV rW rX )ro r� r� r� rX rX rZ r# � rh �
_Delete__ent3rr �*ReturningDelete[Tuple[_T0, _T1, _T2, _T3]]c C rV rW rX )ro r� r� r� r� rX rX rZ r# � rl �
_Delete__ent4rv �/ReturningDelete[Tuple[_T0, _T1, _T2, _T3, _T4]]c C rV rW rX )ro r� r� r� r� r� rX rX rZ r# � rp �
_Delete__ent5rz �4ReturningDelete[Tuple[_T0, _T1, _T2, _T3, _T4, _T5]]c C rV rW rX )ro r� r� r� r� r� r� rX rX rZ r# � rt �
_Delete__ent6r} �9ReturningDelete[Tuple[_T0, _T1, _T2, _T3, _T4, _T5, _T6]]c C rV rW rX )ro r� r� r� r� r� r� r� rX rX rZ r# � rx �
_Delete__ent7r� �>ReturningDelete[Tuple[_T0, _T1, _T2, _T3, _T4, _T5, _T6, _T7]]c C rV rW rX ) ro r� r� r� r� r� r� r� r� rX rX rZ r# � r� r r! � _Delete__kwr �ReturningDelete[Any]c O rV rW rX �ro r r� rX rX rZ r# rh c O rV rW rX r� rX rX rZ r# r� NrT )r� rf rT r� )r� rf r� rj rT r� )r� rf r� rj r� rn rT r� )
r� rf r� rj r� rn r� rr rT r� ) r� rf r� rj r� rn r� rr r� rv rT r� )r� rf r� rj r� rn r� rr r� rv r� rz rT r� )r� rf r� rj r� rn r� rr r� rv r� rz r� r} rT r� )r� rf r� rj r� rn r� rr r� rv r� rz r� r} r� r� rT r� )r r! r� r rT r� )r� r� r� r9 r� � is_deleter8 r� r� r� r2 r� r$ r� r% r� r1 r� r� rp r r r# rX rX rX rZ r� � sP ���� ��
�r� c @ r� )�ReturningDeletez�Typing-only class that establishes a generic type form of
:class:`.Delete` which tracks returned column types.
This datatype is delivered when calling the
:meth:`.Delete.returning` method.
.. versionadded:: 2.0
Nr� rX rX rX rZ r� r� r� )rR rS rT rU )rR rS rT r] )rR rS rT r_ )ur9 �
__future__r �collections.abc�abcr� �operator�typingr r r r r r r r
r r r
r r r r r � r r r r� �_typingr r r r �baser r r r r r! r" r# r$ r% r& r' �elementsr( r) r* r+ r- r/ r. r/ r0 r1 r2 r3 r4 r5 r6 �sqltypesr7 �visitorsr8 r: � util.typingr; r< r= r> r? r@ rA rB rC rD rE rF rG rH rI rJ �_TCCArK rk rL rM rN rO rP rQ r[ r^ r` �
attrgetterra r. �_DMLColumnElementr� rS �
plugin_forr� r� r� �DMLRoleri r� r� r� r� r� r� r� r� rX rX rX rZ �<module> s�
F
(
� D W p L 5 x