관리-도구
편집 파일: dml.cpython-38.pyc
U -?�fN � @ s8 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 ddl m Z 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+l3m4Z4 dd,l3m5Z5 dd-l3m6Z6 dd.l3m7Z7 dd/l3m8Z8 dd0l3m9Z9 dd1l3m:Z: dd2l3m;Z; dd3l3m<Z< dd4l=m>Z> dd5l?m@Z@ d6d7lmAZA d6dlmZ d6d8lBmCZC d6d9lBmDZD e�r�dd:l mEZE dd;l mFZF 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 mRZS ddHl!mTZT ddIlUmVZV ddJl-mWZW ddKl3mXZX ddLl3mYZY ddMl3mZZZ ddNl3m[Z[ dOdPdQ�dRdS�Z\dOdTdQ�dUdV�Z]dOdWdQ�dXdY�Z^n e�_dS�Z\e�_dV�Z]e�_dY�Z^edZed[�Z`eeae0e f Zbee;e4e9f ZcG d\dO� dOe(�Zde(�ed]d^�G d_d`� d`ed��Zfe(�ed]da�G dbdc� dced��Zge(�ed]dd�G dedf� dfed��ZhG dgdh� dhejie7e,e)e8e+e5e/� ZjG didj� djej�ZkG dkdl� dlek�ZlG dmdn� dnele<e �ZmG dodp� dp�ZnG dqdr� drenek�ZoG dsdt� dteoe<e �ZpG dudv� dvenej�ZqG dwdx� dxeoe<e �ZrdS )yzd Provide :class:`_expression.Insert`, :class:`_expression.Update` and :class:`_expression.Delete`. � )� annotationsN)�Any)�cast)�Dict)�Iterable)�List)�MutableMapping)�NoReturn)�Optional)�overload)�Sequence)�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)� 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�DMLStatezTypeGuard[UpdateDMLState])�dml�returnc C s d S �N� �rQ rT rT �B/opt/hc_python/lib64/python3.8/site-packages/sqlalchemy/sql/dml.py�isupdate^ � rW zTypeGuard[DeleteDMLState]c C s d S rS rT rU rT rT rV �isdelete` rX rY zTypeGuard[InsertDMLState]c C s d S rS rT rU rT rT rV �isinsertb rX rZ �_T)�boundc @ sB e Zd ZU dZdZded< dZded< dZded< dZd ed < d ed < dZ d Z d Z d Z ded< dddd�dd�Z eddd�dd��Zeddd�dd��Zed d �d d ��Zer�ed d!d�d"d#��Zedd$d%d&�d'd(��Zedd)d*d+d,�d-d.��Zd/d0d�d1d2�Zd3d4d�d5d6�Zd3d4d�d7d8�Zd3d9d�d:d;�Zd9d �d<d=�ZdS )>rP TNz0Optional[MutableMapping[_DMLColumnElement, Any]]�_dict_parametersz6Optional[List[MutableMapping[_DMLColumnElement, Any]]]�_multi_parameters�-Optional[List[Tuple[_DMLColumnElement, Any]]]�_ordered_valuesz!Optional[List[_DMLColumnElement]]�_parameter_orderingr. �_primary_tableF� UpdateBase� statementrJ r �rd �compiler�kwc K s t � �d S rS ��NotImplementedError)�selfrd rf rg rT rT rV �__init__� s zDMLState.__init__�Dict[str, Any]�rd rR c C s t |j�r|jjnd |jd�S )N)�name�table)r ro rn ��clsrd rT rT rV �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 ))rn �type�expr)�keyrt ��.0�crT rT rV � <listcomp>� s ��z>DMLState.get_returning_column_descriptions.<locals>.<listcomp>)�_all_selected_columnsrp rT rT rV �!get_returning_column_descriptions� s �z*DMLState.get_returning_column_descriptions�_DMLTableElement�rR c C s | j jS rS )rd ro �rj rT rT rV � dml_table� s zDMLState.dml_tabler# zType[DMLState]c C s d S rS rT rp rT rT rV �get_plugin_class� s zDMLState.get_plugin_classz'Iterable[Dict[_DMLColumnArgument, Any]]z"List[Dict[_DMLColumnElement, Any]])rd �multi_kv_iteratorrR c C s dd� |D �S )Nc S s g | ]}d d� |� � D ��qS )c S s i | ]\}}t �tj|�|�qS rT �r �expectr � DMLColumnRole�rx �k�vrT rT rV � <dictcomp>� s � z@DMLState._get_multi_crud_kv_pairs.<locals>.<listcomp>.<dictcomp>)�items)rx �mappingrT rT rV rz � s ��z5DMLState._get_multi_crud_kv_pairs.<locals>.<listcomp>rT )rq rd r� rT rT rV �_get_multi_crud_kv_pairs� s �z!DMLState._get_multi_crud_kv_pairsz(Iterable[Tuple[_DMLColumnArgument, Any]]�boolz#List[Tuple[_DMLColumnElement, Any]])rd � kv_iterator�needs_to_be_cacheablerR c s � fdd�|D �S )Nc s< g | ]4\}}t �tj|�� s |nt jtj|t� d d�f�qS )T)�type_Zis_crud)r r� r r� ZExpressionElementRoler5 r� �r� rT rV rz � s � ���z/DMLState._get_crud_kv_pairs.<locals>.<listcomp>rT )rq rd r� r� rT r� rV �_get_crud_kv_pairs� s �zDMLState._get_crud_kv_pairs� DMLWhereBasez#Tuple[FromClause, List[FromClause]]c C s� g }t t�|j��}|d }|h}|j}| jr@|t| j�� �7 }|D ]4}t|�D ]&}|� |j �sj|� |� |� |j � qPqD|� |dd � � ||fS )Nr r )�list�sql_utilZtables_from_leftmostro �_where_criteriar] �tuple�valuesr � intersectionZ _cloned_set�append�update�extend) rj rd ZfromsZ all_tablesZ primary_table�seenZconsider�crit�itemrT rT rV �_make_extra_froms� s zDMLState._make_extra_froms� ValuesBase�Nonec C s | j r|j| _d| _ d S �NF)�_no_parameters�_valuesr] �rj rd rT rT rV �_process_values� s zDMLState._process_valuesc C sB |j d k st�dd� |j D �}| jr2d| _|| _n ds>td��d S )Nc S s i | ] }|t � �qS rT r* �rx rn rT rT rV r� � s z3DMLState._process_select_values.<locals>.<dictcomp>Fz%This statement already has parameters)� _select_names�AssertionErrorr� r] �rj rd � parametersrT rT rV �_process_select_values� s �z DMLState._process_select_valuesr c C s t �d|j�� ��d S )Nz6%s construct does not support multiple parameter sets.)r8 �InvalidRequestError�__visit_name__�upperr� rT rT rV �_no_multi_values_supported� s ��z#DMLState._no_multi_values_supportedc C s t �d��d S )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.)r8 r� r rT rT rV �_cant_mix_formats_error� s �z DMLState._cant_mix_formats_error) �__name__� __module__� __qualname__r� r] �__annotations__r^ r` ra � _supports_implicit_returningrW rY rZ rk � classmethodrr r| �propertyr� r r� r� r� r� r� r� r� r� rT rT rT rV rP p s> � �default�insertc @ sb e Zd ZdZdZdZdddddd�dd �Zejd d �d d ��Z ddd�dd�Z ddd�dd�Z dS )�InsertDMLStateTF�InsertrJ r� r )rd rf �disable_implicit_returningrg c K sV || _ |j| _|rd| _d| _|jr.| �|� |jd k rB| �|� |j rR| � |� d S )NFT) rd ro rb r� rZ r� r� r� r� � _multi_values�_process_multi_values)rj rd rf r� rg rT rT rV rk s zInsertDMLState.__init__z List[str]r~ c C s dd� | j pdD �S )Nc S s g | ]}t jtj|d d��qS �T)Zas_keyr� �rx �colrT rT rV rz % s �z3InsertDMLState._insert_col_keys.<locals>.<listcomp>rT )r] r rT rT rV �_insert_col_keys" s �z InsertDMLState._insert_col_keysr� r� rm c C s. | j r d| _|j| _d| _ n| jr*| �� d S r� )r� �_has_multi_parametersr� r] r� r� rT rT rV r� * s z InsertDMLState._process_valuesc sn � j D ]b}� fdd�|D �}| jrBd| _d| _|| _| jd | _q| jsR| �� q| js\t�| j�|� qd S )Nc s4 g | ],}t |tj�r,d d� t� jj|�D �n|�qS )c S s i | ]\}}|j |�qS rT �rv �rx ry �valuerT rT rV r� 6 s � zCInsertDMLState._process_multi_values.<locals>.<listcomp>.<dictcomp>)� isinstance�collections_abcr �zipro ry )rx Z parameter_set�rd rT rV rz 4 s � � �z8InsertDMLState._process_multi_values.<locals>.<listcomp>FTr )r� r� r� r^ r] r� r� r� )rj rd r� Zmulti_parametersrT r� rV r� 2 s � z$InsertDMLState._process_multi_valuesN)F) r� r� r� rZ � include_table_with_column_exprsr� rk r Zmemoized_propertyr� r� r� rT rT rT rV r� s �r� r� c @ s6 e Zd ZdZdZdddd�dd�Zd d d �d d �ZdS )�UpdateDMLStateTF�UpdaterJ r re c K s� || _ d| _|jd k r"| �|� n&|jd k r8| �|� n|jrH| �|� | �|�\}}|| _ || _ | | _ }t |ov|j �| _d S �NT)rd rW r` �_process_ordered_valuesr� r� r� r� r� rb � _extra_froms� is_multitabler� Z'render_table_with_column_in_update_fromr� )rj rd rf rg �t�ef�mtrT rT rV rk R s �zUpdateDMLState.__init__r� r� rm c C sN |j }| jr@d| _|d k s t�t|�| _|| _ dd� |D �| _n t�d��d S )NFc S s g | ] \}}|�qS rT rT �rx rv r� rT rT rV rz m s z:UpdateDMLState._process_ordered_values.<locals>.<listcomp>zQCan only invoke ordered_values() once, and not mixed with any other values() call)r` r� r� �dictr] ra r8 r� r� rT rT rV r� e s �z&UpdateDMLState._process_ordered_valuesN)r� r� r� rW r� rk r� rT rT rT rV r� L s r� �deletec @ s" e Zd ZdZdddd�dd�ZdS ) �DeleteDMLStateT�DeleterJ r re c K s0 || _ d| _| �|�\}}|| _|| _|| _d S r� )rd rY r� rb r� r� )rj rd rf rg r� r� rT rT rV rk y s zDeleteDMLState.__init__N)r� r� r� rY rk rT rT rT rV r� u s r� c @ sX e Zd ZU dZdZejZded< dZ e j Z ded< ded < dZ d Zd ed < d Zd ed < dZded< dZddd�dd�Zdddd�dd�Zedd d �d d ��Zed dd �d!d"d#d d$�d%d&��Zedd'�d(d#dd d)�d*d+��ZdDd,d#d-d.�d/d0�Zejd1d2�d3d4��Zejd5d2�d6d7��ZedEd9d:d9d d;�d<d=��Z e d>d2�d?d@��Z e dAd2�dBdC��Z d S )Frc zDForm the base for ``INSERT``, ``UPDATE``, and ``DELETE`` statements.Z update_basez5util.immutabledict[Tuple[_DMLTableElement, str], str]�_hintsFr2 � _label_styler} ro Nz+Optional[Tuple[_ColumnsClauseElement, ...]]�_return_defaults_columns�_supplemental_returningrT z!Tuple[_ColumnsClauseElement, ...]� _returningTr. r� )� fromclauserR c s � j �� fdd�| jD �� d S )Nc 3 s | ]}t |�r|�� �V qd S rS )r Z _make_proxyr� �r� rT rV � <genexpr>� s �zAUpdateBase._generate_fromclause_column_proxies.<locals>.<genexpr>)Z_columnsZ_populate_separate_keysr{ )rj r� rT r� rV �#_generate_fromclause_column_proxies� s �z.UpdateBase._generate_fromclause_column_proxiesr r )�argrg rR c O s t d��dS )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).Nrh )rj r� rg rT rT rV �params� s �zUpdateBase.paramsr9 )�optrR 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. )Z_validate_dialect_kwargs)rj r� rT rT rV �with_dialect_options� s z UpdateBase.with_dialect_options)�supplemental_cols�sort_by_parameter_orderr= z&Optional[Iterable[_DMLColumnArgument]]r� )�colsr� r� rR c G s� | j r<| jr4|r4tt�| j��dd� |D ���| _qPd| _ntdd� |D ��| _d| _ |rp| jsjt�d��d| _ |r�dd� |D �}| j dkr�tt� |��| _ ntt� | 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 s | ]}t �tj|�V qd S rS �r r� r ZColumnsClauseRolerw rT rT rV r� � s �z-UpdateBase.return_defaults.<locals>.<genexpr>rT c s s | ]}t �tj|�V qd S rS r� rw rT rT rV r� � s Tz]The 'sort_by_parameter_order' argument to return_defaults() only applies to INSERT statementsc s s | ]}t �tj|�V qd S rS r� rw rT rT rV r� � s �N) �_return_defaultsr� r� r Z OrderedSet�union� is_insertr8 � ArgumentError�_sort_by_parameter_orderr� Z unique_list)rj r� r� r� Zsupplemental_col_tuprT rT rV �return_defaults� sF 8 ��� �� ����zUpdateBase.return_defaults�r� �_ColumnsClauseArgument[Any])r� r� �_UpdateBase__kwrR c O sX |rt d|��| jr t�d��| jtdd� |D ��7 _|rT| jsNt�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 s | ]}t �tj|�V qd S rS r� rw rT rT rV r� s z'UpdateBase.returning.<locals>.<genexpr>zWThe 'sort_by_parameter_order' argument to returning() only applies to INSERT statementsT) r r� r8 r� r� r� r� r� r� )rj r� r� r� rT rT rV � returning� s _ �� �zUpdateBase.returningzKeyedColumnElement[Any]� Optional[ColumnElement[Any]])�column�require_embeddedrR c C s | j j||d�S )N)r� )�exported_columns�corresponding_column)rj r� r� rT rT rV r� # s �z UpdateBase.corresponding_columnrM r~ c C s dd� t | j�D �S )Nc S s g | ]}|�qS rT rT rw rT rT rV rz , s z4UpdateBase._all_selected_columns.<locals>.<listcomp>)r r� r rT rT rV r{ * s z UpdateBase._all_selected_columnsz;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 rS )r rv rw rT rT rV r� 8 s �z.UpdateBase.exported_columns.<locals>.<genexpr>)r r{ Z as_readonlyr rT rT rV r� . s �zUpdateBase.exported_columns�*�strzOptional[_DMLTableArgument])�text� selectable� dialect_namerR c C s8 |dkr| 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)ro r r� r � DMLTableRoler� r� )rj r� r� r rT rT rV � with_hint> s $zUpdateBase.with_hintrl c C s 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 )rP r� rr �rj �methrT rT rV �entity_descriptioni s ! z UpdateBase.entity_descriptionrs c C s t �| �j}|| �S )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 )rP r� r| r rT rT rV � returning_column_descriptions� s *�z(UpdateBase.returning_column_descriptions)F)Nr� ) r� r� r� �__doc__r� r � EMPTY_DICTr� r� Znamed_with_columnr2 Z LABEL_STYLE_DISAMBIGUATE_ONLYr� r� r� r� r� Zis_dmlr� r� r r� r� r� r� Zro_memoized_propertyr{ r� r r� r r rT rT rT rV rc � sP � � � � g�q � �*#rc c @ s� e Zd ZU dZdZdZdZded< dZded< dZ d ed < d Z d ed < dZ ded< dZ ded< dZ ded< dd�dd�Zeeddddd�d�d d d d �d d!���ZdS )"r� zTSupplies support for :meth:`.ValuesBase.values` to INSERT and UPDATE constructs.Z values_baseFNzOptional[Select[Any]]�selectzOptional[ClauseElement]�_post_values_clausez4Optional[util.immutabledict[_DMLColumnElement, Any]]r� rT zRTuple[Union[Sequence[Dict[_DMLColumnElement, Any]], Sequence[Sequence[Any]]], ...]r� r_ r` zOptional[List[str]]r� r� �_inliner? �ro c C s t jtj|| d�| _d S �N�Zapply_propagate_attrs�r r� r r ro �rj ro rT rT rV rk � s �zValuesBase.__init__z,This construct already inserts from a SELECT�1This statement already has ordered values present)r� r` )Zmsgsz/Union[_DMLColumnKeyMapping[Any], Sequence[Any]]r r9 )�args�kwargsrR c O s. |r�|d }|r t �d��q�t|�dkr4t �d��q�t|tj�r�|rxt|d t�rxt�| �j }| j || |�f7 _ | S |r�t|d t t f�r�| j |f7 _ | S t r�t| t�s�t�dd� t| jj|�D �}ntd|�}|r�t �d��t�| �j}t|| |�� d��}| j�r | j�|�| _n t�|�| _| S ) aL 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:`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 s i | ]\}}|j |�qS rT r� r� rT rT rV r� t s z%ValuesBase.values.<locals>.<dictcomp>z Dict[_DMLColumnArgument, Any]T)r8 r� �lenr� r� r r� rP r� r� r� r� r� r r� r� r� ro ry r r� r� r� r� r Z immutabledict)rj r r r� Zmulti_kv_generator� kv_generatorZ coerced_argrT rT rV r� � sD p� � � � zValuesBase.values)r� r� r� r r� �_supports_multi_parametersr r� r r� r� r` r� r rk r r r� rT rT rT rV r� � s* � �� r� c sN 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 Zdd�� fdd� Z e dd�dd��Z e dId d ddd �d d ��Z e �rFe!dd!�d"dd#d$�d%d&��Z"e!dd!�d"d'dd(d)�d*d&��Z"e!dd!�d"d'd+dd,d-�d.d&��Z"e!dd!�d"d'd+d/dd0d1�d2d&��Z"e!dd!�d"d'd+d/d3dd4d5�d6d&��Z"e!dd!�d"d'd+d/d3d7dd8d9�d:d&��Z"e!dd!�d"d'd+d/d3d7d;dd<d=� d>d&��Z"e!dd!�d"d'd+d/d3d7d;d?dd@dA� dBd&��Z"e!dd!�dCddDdEdF�dGd&��Z"dd!�dCddDdEdF�dHd&�Z"� Z#S )Jr� z�Represent an INSERT construct. The :class:`_expression.Insert` object is created using the :func:`_expression.insert()` function. r� TNFr� r� r3 ro r r� r� r� r r r� r� r� r� r? r c s t � �|� d S rS ��superrk r �� __class__rT rV rk � s zInsert.__init__r9 r~ c C s 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�r r rT rT rV �inline� s z Insert.inlinez Sequence[_DMLColumnArgument]rO )�namesr �include_defaultsrR c 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 s g | ]}t jtj|d d��qS r� r� r� rT rT rV rz s �z&Insert.from_select.<locals>.<listcomp>T) r� r8 r� r� r �#include_insert_from_select_defaultsr r� r Z DMLSelectRoler )rj r r r rT rT rV � from_select� s )��zInsert.from_selectr� � _TCCA[_T0]zReturningInsert[Tuple[_T0]])� _Insert__ent0r� rR c C s d S rS rT )rj r" r� rT rT rV r� s zInsert.returning� _TCCA[_T1]z ReturningInsert[Tuple[_T0, _T1]])r" � _Insert__ent1r� rR c C s d S rS rT )rj r" r$ r� rT rT rV r� s � _TCCA[_T2]z%ReturningInsert[Tuple[_T0, _T1, _T2]])r" r$ � _Insert__ent2r� rR c C s d S rS rT )rj r" r$ r& r� rT rT rV r� s � _TCCA[_T3]z*ReturningInsert[Tuple[_T0, _T1, _T2, _T3]])r" r$ r& � _Insert__ent3r� rR c C s d S rS rT )rj r" r$ r& r( r� rT rT rV r� ) s � _TCCA[_T4]z/ReturningInsert[Tuple[_T0, _T1, _T2, _T3, _T4]])r" r$ r& r( � _Insert__ent4r� rR c C s d S rS rT )rj r" r$ r& r( r* r� rT rT rV r� 4 s � _TCCA[_T5]z4ReturningInsert[Tuple[_T0, _T1, _T2, _T3, _T4, _T5]])r" r$ r& r( r* � _Insert__ent5r� rR c C s d S rS rT )rj r" r$ r& r( r* r, r� rT rT rV r� @ s � _TCCA[_T6]z9ReturningInsert[Tuple[_T0, _T1, _T2, _T3, _T4, _T5, _T6]]) r" r$ r& r( r* r, � _Insert__ent6r� rR c C s d S rS rT ) rj r" r$ r& r( r* r, r. r� rT rT rV r� M s � _TCCA[_T7]z>ReturningInsert[Tuple[_T0, _T1, _T2, _T3, _T4, _T5, _T6, _T7]]) r" r$ r& r( r* r, r. � _Insert__ent7r� rR c C s d S rS rT ) rj r" r$ r& r( r* r, r. r0 r� rT rT rV r� [ s r� r zReturningInsert[Any])r� r� � _Insert__kwrR c O s d S rS rT �rj r� r� r1 rT rT rV r� n s c O s d S rS rT r2 rT rT rV r� v s )T)$r� r� r� r r� r r r r� r� r� r6 �dp_clauseelement� dp_booleanZdp_string_list� dp_dml_valuesZdp_dml_multi_values�dp_clauseelement_tuple�dp_table_hint_listr0 � _has_prefixes_traverse_internalsr" �"_dialect_kwargs_traverse_internalsr# � _executable_traverse_internalsr/ � _has_ctes_traverse_internals�_traverse_internalsrk r r r r r r� � __classcell__rT rT r rV r� � s� ������� �6��� � � �" �$ �&� �r� c @ s 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� r rT rT rT rV r> ~ s r> c @ sv e Zd ZU ded< dZded< eddd�d d ��Zd dd �d d�Zdd�dd�Zddd�dd�Z e dd�dd��Z dS )r� r} ro rT z Tuple[ColumnElement[Any], ...]r� z _ColumnExpressionArgument[bool]r9 )� whereclauserR 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` r )r r� r ZWhereHavingRoler� )rj r@ � criterionZwhere_criteriarT rT rV �where� s �zDMLWhereBase.wherez roles.ExpressionElementRole[Any])�criteriarR c G s | j |� S )zbA synonym for the :meth:`_dml.DMLWhereBase.where` method. .. versionadded:: 1.4 )rB )rj rC rT rT rV �filter� s zDMLWhereBase.filterr~ c C s | j S rS r r rT rT rV �_filter_by_zero� s z DMLWhereBase._filter_by_zeror )r rR c s( | � � � � fdd�|�� D �}| j|� S )zWapply the given filtering criterion as a WHERE clause to this select. c s g | ]\}}t � |�|k�qS rT r r� �Z from_entityrT rV rz � s �z*DMLWhereBase.filter_by.<locals>.<listcomp>)rE r� rD )rj r ZclausesrT rF rV � 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& Z_construct_for_whereclauser� r rT rT rV r@ � s �zDMLWhereBase.whereclauseN) r� r� r� r� r� r rB rD rE rG r� r@ rT rT rT rV r� � s r� c s� e Zd ZdZdZdZdejfdejfdej fdej fdej fd ejfd ej fd ej fd ejfg e j ej ej ej Zd d�� fdd� Zeddd�dd��Zedd�dd��Ze�r�eddd�d d ��Z edd d d �d!d ��Z edd d"d#d$�d%d ��Z edd d"d&d'd(�d)d ��Z edd d"d&d*d+d,�d-d ��Z edd d"d&d*d.d/d0�d1d ��Z edd d"d&d*d.d2d3d4�d5d ��Z edd d"d&d*d.d2d6d7d8� d9d ��Z ed:d;d<d=�d>d ��Z d:d;d<d=�d?d �Z � Z S )@r� z�Represent an Update construct. The :class:`_expression.Update` object is created using the :func:`_expression.update()` function. r� Tro r� r r` r� r� r� r� r� r? r c s t � �|� d S rS r r r rT rV rk � s zUpdate.__init__z Tuple[_DMLColumnArgument, Any]r9 )r rR c G s@ | j rt�d��n| jr"t�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 presentr T)r� r8 r� r` rP r� r� )rj r r rT rT rV �ordered_values� s �� zUpdate.ordered_valuesr~ c C s d| _ | S )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 rT rT rV r s z Update.inliner! zReturningUpdate[Tuple[_T0]])� _Update__ent0rR c C s d S rS rT )rj rI rT rT rV r� 8 s zUpdate.returningr# z ReturningUpdate[Tuple[_T0, _T1]])rI � _Update__ent1rR c C s d S rS rT )rj rI rJ rT rT rV r� = s r% z%ReturningUpdate[Tuple[_T0, _T1, _T2]])rI rJ � _Update__ent2rR c C s d S rS rT )rj rI rJ rK rT rT rV r� B s r' z*ReturningUpdate[Tuple[_T0, _T1, _T2, _T3]])rI rJ rK � _Update__ent3rR c C s d S rS rT )rj rI rJ rK rL rT rT rV r� G s r) z/ReturningUpdate[Tuple[_T0, _T1, _T2, _T3, _T4]])rI rJ rK rL � _Update__ent4rR c C s d S rS rT )rj rI rJ rK rL rM rT rT rV r� P s r+ z4ReturningUpdate[Tuple[_T0, _T1, _T2, _T3, _T4, _T5]])rI rJ rK rL rM � _Update__ent5rR c C s d S rS rT )rj rI rJ rK rL rM rN rT rT rV r� Z s r- z9ReturningUpdate[Tuple[_T0, _T1, _T2, _T3, _T4, _T5, _T6]])rI rJ rK rL rM rN � _Update__ent6rR c C s d S rS rT )rj rI rJ rK rL rM rN rO rT rT rV r� e s r/ z>ReturningUpdate[Tuple[_T0, _T1, _T2, _T3, _T4, _T5, _T6, _T7]]) rI rJ rK rL rM rN rO � _Update__ent7rR c C s d S rS rT ) rj rI rJ rK rL rM rN rO rP rT rT rV r� q s r� r zReturningUpdate[Any])r� � _Update__kwrR c O s d S rS rT �rj r� rQ rT rT rV r� � s c O s d S rS rT rR rT rT rV r� � s ) r� r� r� r r� Z is_updater6 r3 r6 r4 Zdp_dml_ordered_valuesr5 r7 r0 r8 r" r9 r# r: r/ r; r< rk r rH r r r r� r= rT rT r rV r� � sb �������$ r� c @ s e Zd ZdZdS )�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? rT rT rT rV rS � s rS c @ sh e Zd ZdZdZdZdejfdejfdejfdej fge j e j ej ej Zdd �d d �Ze�rded d d�dd��Zed ddd�dd��Zed dddd�dd��Zed ddddd�d d��Zed dddd d d �d d��Zed dddd d!d"d#�d$d��Zed dddd d!d%d&d'�d(d��Zed dddd d!d%d)d*d+� d,d��Zed-d.d/d0�d1d��Zd-d.d/d0�d2d�Zd3S )4r� z�Represent a DELETE construct. The :class:`_expression.Delete` object is created using the :func:`_expression.delete()` function. r� Tro r� r� r� r? r c C s t jtj|| d�| _d S r r r rT rT rV rk � s �zDelete.__init__r! zReturningDelete[Tuple[_T0]])� _Delete__ent0rR c C s d S rS rT )rj rT rT rT rV r� � s zDelete.returningr# z ReturningDelete[Tuple[_T0, _T1]])rT � _Delete__ent1rR c C s d S rS rT )rj rT rU rT rT rV r� � s r% z%ReturningDelete[Tuple[_T0, _T1, _T2]])rT rU � _Delete__ent2rR c C s d S rS rT )rj rT rU rV rT rT rV r� � s r' z*ReturningDelete[Tuple[_T0, _T1, _T2, _T3]])rT rU rV � _Delete__ent3rR c C s d S rS rT )rj rT rU rV rW rT rT rV r� � s r) z/ReturningDelete[Tuple[_T0, _T1, _T2, _T3, _T4]])rT rU rV rW � _Delete__ent4rR c C s d S rS rT )rj rT rU rV rW rX rT rT rV r� � s r+ z4ReturningDelete[Tuple[_T0, _T1, _T2, _T3, _T4, _T5]])rT rU rV rW rX � _Delete__ent5rR c C s d S rS rT )rj rT rU rV rW rX rY rT rT rV r� � s r- z9ReturningDelete[Tuple[_T0, _T1, _T2, _T3, _T4, _T5, _T6]])rT rU rV rW rX rY � _Delete__ent6rR c C s d S rS rT )rj rT rU rV rW rX rY rZ rT rT rV r� � s r/ z>ReturningDelete[Tuple[_T0, _T1, _T2, _T3, _T4, _T5, _T6, _T7]]) rT rU rV rW rX rY rZ � _Delete__ent7rR c C s d S rS rT ) rj rT rU rV rW rX rY rZ r[ rT rT rV r� � s r� r zReturningDelete[Any])r� � _Delete__kwrR c O s d S rS rT �rj r� r\ rT rT rV r� s c O s d S rS rT r] rT rT rV r� s N)r� r� r� r r� Z is_deleter6 r3 r6 r7 r0 r8 r" r9 r# r: r/ r; r< rk r r r� rT rT rT rV r� � sL ���� �� r� c @ s e Zd ZdZdS )�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? rT rT rT rV r^ s r^ )sr � __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� Z_typingr r r r �baser r r r r r r! r" r# r$ r% �elementsr& r' r( r) r+ r� r, r- r. r/ r0 r1 r2 r3 r4 Zsqltypesr5 Zvisitorsr6 r8 Z util.typingr9 r: r; r< r= r> r? r@ rA rB rC rD rE rF rG rH Z_TCCArI rf rJ rK rL rM rN rO rW rY rZ � attrgetterr[ r� Z_DMLColumnElementr} rP Z plugin_forr� r� r� ZDMLRolerc r� r� r> r� r� rS r� r^ rT rT rT rV �<module> s� F ( � > S p L 7 x