,h bSrSSKJr SSKJr SSKrSSKJr SSKJ r SSKJ r SSKJ r SSKJ r SS KJ r SS KJr SS KJr SS KJr SS KJr SSKJr SSKJr SSKJr SSKJr SSKJr SSKJr SSKJr SSKJr SSKJr SSKJr SSKJr SSKJ r SSKJ!r! SSK"J#r# SSK"J$r$ SSK"J%r% SSK"J&r& SS K"J'r' SS!K"J(r( SS"K"J)r) SS#K"J*r* SS$K"J+r+ SS%K"J,r, SS&K"J-r- SS'K"J.r. SS(K/J0r0 SS)K/J1r1 SS*K/J2r2 SS+K/J3r3 SS,K/J4r4 SS-K5J6r6 SS.K5J7r7 SS/K5J8r8 SS0K5J9r9 SS1K5J:r: SS2K5J;r; SS3K5Jr> SS6K?J@r@ SS7KAJBrB S8S9KJCrC S8SKJr S8S:KDJErE S8S;KDJFrF \(aSSKJIrI SS?KJJrJ SS@KJKrK SSAKJLrL SSBKJMrM SSCKJNrN SSDKJOrO SSEKJPrP SSFKJQrQ SSGKJRrR SSHKJSrS SSIKJTrU SSJK"JVrV SSKKWJXrX SSLK/JYrY SSMK5JZrZ SSNK5J[r[ SSOK5J\r\ SSPK5J]r] SwSRjr^SxSSjr_SySTjr`O6\R"SU5r^\R"SV5r_\R"SW5r`\"SX\SY9rb\\c\2\4rd\\=\6\;4re"SZSQ\*5rf\*R"S[S\5"S]S^\f55rh\*R"S[S_5"S`Sa\f55ri\*R"S[Sb5"ScSd\f55rj"SeSf\R\9\.\+\:\-\7\15 rl"SgSh\l5rm"SiSj\m5rn"SkSl\n\>\5ro"SmSn5rp"SoSp\p\m5rq"SqSr\q\>\5rr"SsSt\p\l5rs"SuSv\q\>\5rtg)zzd 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) SelectableDMLStatecgNdmls J/var/www/auris/envauris/lib/python3.13/site-packages/sqlalchemy/sql/dml.pyisupdaterX`ccgrSrTrUs rWisdeleter\brYrZcgrSrTrUs rWisinsertr^drYrZrXr\r^_T)boundcp\rSrSr%SrSrS\S'SrS\S'SrS\S 'Sr S \S 'S \S 'Sr Sr Sr Sr S\S'SSjr\SSj5r\S Sj5r\S!Sj5r\(a \S"Sj5r\S#Sj5r\S$Sj5rS%SjrS&SjrS&SjrS'SjrS(SjrSrg))rQrTNz0Optional[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 statementc [5erSNotImplementedError)selfrjcompilerkws rW__init__DMLState.__init__s "##rZc[UR5(aURROSURS.$)N)nametable)rrurtclsrjs rWget_entity_descriptionDMLState.get_entity_descriptions6 ( 88$$__   rZcvURVs/sHnURURUS.PM sn$s snf)N)rttypeexpr)_all_selected_columnskeyr{)rwrjcs rW!get_returning_column_descriptions*DMLState.get_returning_column_descriptionssF44  5   5    s$6c.URR$rS)rjrurns rW dml_tableDMLState.dml_tables~~###rZcgrSrTrvs rWget_plugin_classDMLState.get_plugin_classsLOrZc UVVVs/sHLnUR5VVs0sH+upE[R"[RU5U_M- snnPMN snnn$s snnfs snnnfrS)itemsrexpectr DMLColumnRole)rwrjmulti_kv_iteratormappingkvs rW_get_multi_crud_kv_pairs!DMLState._get_multi_crud_kv_pairssj-  -$MMO +DA  !4!4a8!;+ -     sA%2AA%A%c UVVs/sH`upE[R"[RU5U(dUO,[R"[RU[ 5SS94PMb snn$s snnf)NT)type_is_crud)rrrrExpressionElementRoler6)rwrj kv_iteratorneeds_to_be_cacheablerrs rW_get_crud_kv_pairsDMLState._get_crud_kv_pairsss*$ $  !4!4a81"))33&j $  $   sA'A1c/n[[R"UR55nUSnU1nURnUR (a&U[ UR R55- nUHan[U5HOnURUR5(dURU5 URUR5 MQ Mc URUSS5 XB4$)Nrr)listsql_utiltables_from_leftmostru_where_criteriarctuplevaluesr intersection _cloned_setappendupdateextend) rnrjfroms all_tables primary_tableseenconsidercrititems rW_make_extra_fromsDMLState._make_extra_fromss#%(77 HI "1 ,,  d33::<= =HD%d+(()9)9::LL& D,,-,  Z^$##rZcXUR(aURUlSUlggNF)_no_parameters_valuesrcrnrjs rW_process_valuesDMLState._process_valuess&   $-$5$5D !"'D  rZcURceURVs0sH o"[5_M nnUR(aSUlX0lgS5es snf)NFz%This statement already has parameters) _select_namesr,rrc)rnrjrt parameterss rW_process_select_valuesDMLState._process_select_valuessg&&222%.%<%<> %    "'D $. ! BA A5> sAcd[R"SURR5-5e)Nz6%s construct does not support multiple parameter sets.)r9InvalidRequestError__visit_name__upperrs rW_no_multi_values_supported#DMLState._no_multi_values_supporteds2%% ')2)A)A)G)G)I J  rZc.[R"S5e)NzCan'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.)r9rrs rW_cant_mix_formats_error DMLState._cant_mix_formats_errors%%   rZ)rcr)rjrirorKrpr)rjrireturnDict[str, Any])rjrirList[Dict[str, Any]]r_DMLTableElement)rjr%rzType[DMLState])rjrirz'Iterable[Dict[_DMLColumnArgument, Any]]rz"List[Dict[_DMLColumnElement, Any]])rjrirz(Iterable[Tuple[_DMLColumnArgument, Any]]rboolrz#List[Tuple[_DMLColumnElement, Any]])rj DMLWhereBaserz#Tuple[FromClause, List[FromClause]]rj ValuesBaserNone)rjrrr )rr )__name__ __module__ __qualname____firstlineno__rrc__annotations__rdrfrg_supports_implicit_returningrXr\r^rq classmethodrxrpropertyrrrrrrrrrr__static_attributes__rTrZrWrQrQrsrNIMFM  FJOBI=A:A#' HHH$#$/:$BE$     "      $$ O O    C   ,      >  $  -   .$%$ ,$,( B  rZdefaultinsertcz\rSrSrSrSrSrS S Sjjr\RS Sj5r S Sjr S Sjr Sr g )InsertDMLStateiTFc "XlURUlU(aSUlSUlUR (aUR U5 URbURU5 UR(aURU5 gg)NFT) rjrurhrr^rrrr _multi_values_process_multi_values)rnrjrodisable_implicit_returningrps rWrqInsertDMLState.__init__st#'oo %05D -  " "  ' ' 2    (   +  " "  & &y 1 #rZc UR=(d SVs/sH'n[R"[RUSS9PM) sn$s snf)NrTTas_key)rcrrrr)rncols rW_insert_col_keysInsertDMLState._insert_col_keys$sL ,,22 2   U00#d C2   s.A cUR(a SUlURUlSUlgUR(aUR 5 ggr)r_has_multi_parametersrrcrrs rWrInsertDMLState._process_values,sC   ).D &$-$5$5D !"'D   ' '  ( ( *(rZc JURGHnUVVVs/sHdn[U[R5(a@[ UR R U5VVs0sHupEURU_M snnOUPMf nnnnUR(a*SUlSUl X`l URSUl MUR(dUR5 MUR(deURRU5 GM gs snnfs snnnf)NFTr)r isinstancecollections_abcr ziprurr~rrrdrcrr)rnrjr parameter_setrvaluemulti_parameterss rWr$InsertDMLState._process_multi_values4s#11J&0 N&0M"-1I1IJJ),IOO,=,=}(M(MHAu (M ' '&0  N""&+#-1*)9&(,(>(>q(A%//,,.----&&--.>?-2 NsAD D8 D D )rcrrdrrhrr^rjNF)rjInsertrorKrrrpr)rz List[str]r)rrrrr^include_table_with_column_exprsrrqrmemoized_propertyrrrrrTrZrWrrshH&+#! ,1 222%) 2  2*   +@rZrrc0\rSrSrSrSrSSjrS SjrSrg) UpdateDMLStateiNTFc tXlSUlURbURU5 OAURbUR U5 O"UR (aURU5 URU5upEX@l XPl U=Ul n[U=(a UR5UlgNT)rjrXrf_process_ordered_valuesrrrrrrh _extra_froms is_multitabler'render_table_with_column_in_update_fromr)rnrjrorptefmts rWrqUpdateDMLState.__init__Ts"  $ $ 0  ( ( 3    *   +  $ $  + +I 6&&y1"$$R/3  C8CC0 ,rZcURnUR(a?SUlUce[U5UlX lUVVs/sHup4UPM snnUlg[ R "S5es snnf)NFzQCan only invoke ordered_values() once, and not mixed with any other values() call)rfrdictrcrgr9r)rnrjrr~rs rWr&UpdateDMLState._process_ordered_valuesgst..   "'D ) ))$($4D !#- >H'Ij j'ID $))/ (JsA3) rcrrrfrgrhrrrXrjN)rjUpdaterorKrprr) rrrrrXrrqrrrTrZrWrrNsH&+# & rZrdeletec"\rSrSrSrSSjrSrg)DeleteDMLStateiwTc hXlSUlURU5upEX@lXPlXPlgr)rjr\rrhrr)rnrjrorprrs rWrqDeleteDMLState.__init__{s2" &&y1rZ)rrhrr\rjN)rjDeleterorKrpr)rrrrr\rqrrTrZrWrrws H rZrc\rSrSr%SrSr\RrS\ S'Sr \ Rr S\ S'S \ S 'SrS rS \ S 'S rS \ S'SrS\ S'SrS"SjrS#Sjr\S$Sj5r\S SS.S%Sjj5rS&Sjr\SS.S'Sjj5rS(S)Sjjr\R6S*Sj5r\R6S+Sj5r\S,S-Sjj5r\S.Sj5r \S/S j5r!S!r"g )0riizDForm the base for ``INSERT``, ``UPDATE``, and ``DELETE`` statements. update_basez5util.immutabledict[Tuple[_DMLTableElement, str], str]_hintsFr3 _label_stylerruNz+Optional[Tuple[_ColumnsClauseElement, ...]]_return_defaults_columns_supplemental_returningrTz!Tuple[_ColumnsClauseElement, ...] _returningTcX^^^URUUU4SjUR55 g)Nc3j># UH(n[U5(dMURTTTS9v M* g7f)) primary_key foreign_keysN)r _make_proxy).0rr fromclausers rW AUpdateBase._generate_fromclause_column_proxies..s;( 2 %  COO ,  2s33)_populate_separate_keysr})rnrcolumnsrrs ` ``rW#_generate_fromclause_column_proxies.UpdateBase._generate_fromclause_column_proxiess( ''( 11 (  rZc[S5e)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).rl)rnargrps rWparamsUpdateBase.paramss" *  rZc (URU5 U$)zAdd 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)rnopts rWwith_dialect_optionsUpdateBase.with_dialect_optionss %%c* rZ)supplemental_colssort_by_parameter_ordercUR(aeUR(aLU(aE[[R"UR5R SU555UlOSUlO[SU55UlSUlU(a.UR (d[R"S5eSUl U(avSU5nURc&[[R"U55Ul U$[[R"UR[U5-55Ul U$)aMake 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 `, 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 ` 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` c3l# UH*n[R"[RU5v M, g7frSrrrColumnsClauseRolerrs rWr-UpdateBase.return_defaults..s.I!%A"(()@)@!DD!%24rTc3l# UH*n[R"[RU5v M, g7frSr-r/s rWrr0s)2FJ   !8!8!<>''J-1D ) $*$ ++3/4$$%9:0, 05$$44 4560, rZcg)zReturn ``True`` if this :class:`.ReturnsRows` is 'derived' from the given :class:`.FromClause`. Since these are DMLs, we dont want such statements ever being adapted so we return False for derives. FrT)rnrs rWis_derived_fromUpdateBase.is_derived_fromsrZr*c.U(a [SU5eUR(a[R"S5eU=R[ SU55- slU(a.UR (d[R"S5eSUlU$)a: 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 statementc3l# UH*n[R"[RU5v M, g7frSr-r/s rWr'UpdateBase.returning..)s)! BFQI  U44a 8 8$r1zWThe 'sort_by_parameter_order' argument to returning() only applies to INSERT statementsT) rr4r9rrrr7r8r9)rnr*r;_UpdateBase__kws rW returningUpdateBase.returnings~  !94@ @  ))K  5! BF!    #>>''8-1D ) rZc4URRXS9$)N)require_embedded)exported_columnscorresponding_column)rncolumnrJs rWrLUpdateBase.corresponding_column5s%$$99 :  rZcV[UR5Vs/sHoPM sn$s snfrS)r r)rnrs rWr} UpdateBase._all_selected_columns<s%,T__=>=a=>>>s &cV[SUR55R5$)z`Return the RETURNING columns as a column collection for this statement. .. versionadded:: 1.4 c3b# UH%n[U5(dMURU4v M' g7frS)rr~r/s rWr.UpdateBase.exported_columns..Js) / # QUUAJ/s//)r!r} as_readonlyrs rWrKUpdateBase.exported_columns@s-  //   +-  rZcUc URnO%[R"[RU5nUR R X#4U05UlU$)abAdd 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. )rurrr DMLTableRolerr6)rntext selectable dialect_names rW with_hintUpdateBase.with_hintPsOH  J"))%*<*>> 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 )rQrrxrnmeths rWentity_descriptionUpdateBase.entity_description{s%B((.EEDzrZcP[RU5RnU"U5$)aReturn 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=, ...) }, { "name": "name", "type": String(), "expr": Column("name", String(), table=, ...) }, ] .. 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 )rQrrr^s rWreturning_column_descriptions(UpdateBase.returning_column_descriptionss-T((  + + DzrZ)rr4rr9r) rr/rz.ColumnCollection[str, KeyedColumnElement[Any]]rr"rzSet[KeyedColumnElement[Any]]rr)r!rrprrr )r&rrr:)r;r>r)z&Optional[Iterable[_DMLColumnArgument]]r*rrr:)rzOptional[FromClause]rr)r;_ColumnsClauseArgument[Any]r*rrFrrrir)rMzKeyedColumnElement[Any]rJrrOptional[ColumnElement[Any]])rrN)rz;ReadOnlyColumnCollection[Optional[str], ColumnElement[Any]])N*)rXstrrYzOptional[_DMLTableArgument]rZrhrr:)rr)rr)#rrrr__doc__rr EMPTY_DICTrrnamed_with_columnr3LABEL_STYLE_DISAMBIGUATE_ONLYrr4rrris_dmlrr"rr'r=r@rGrLro_memoized_propertyr}rKr[rr`rcrrTrZrWriris3O"N  A 66"  ILPHO46J16 F    @    3        EI(- d!dBd"& d  ddL).n*n"&n n  nnbIN - AE %  ??   D  37 ((0( (  ((T!!F,,rZric\rSrSr%SrSrSrSrS\S'Sr S\S 'Sr S \S 'S r S \S'Sr S\S'Sr S\S'SrS\S'SSjr\\"SSSSS.S9SSj55rSrg)rizPSupplies support for :meth:`.ValuesBase.values` to INSERT and UPDATE constructs. values_baseFNzOptional[Select[Any]]selectzOptional[ClauseElement]_post_values_clausez4Optional[util.immutabledict[_DMLColumnElement, Any]]rrTzRTuple[Union[Sequence[Dict[_DMLColumnElement, Any]], Sequence[Sequence[Any]]], ...]rrerfzOptional[List[str]]rr_inlinecT[R"[RXS9UlgNapply_propagate_attrsrrrrWrurnrus rWrqValuesBase.__init__%%     rZz,This construct already inserts from a SELECT1This statement already has ordered values present)rrf)msgscPU(GaaUSnU(a[R"S5e[U5S:a[R"S5e[U[R 5(aU(aU[US[ 5(a=[RU5RnU=RU"X54- sl U$U(a6[US[[45(aU=RU4- sl U$[(a[U[5(de[UR R"U5VVs0sHupVUR$U_M nnnO)['SU5nU(a[R"S5e[RU5R(n[ U"XR+5S55nUR,(a"UR,R/U5UlU$[0R2"U5UlU$s snnf)aSpecify 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` rz;Can't pass positional and kwargs to values() simultaneouslyrzWOnly a single dictionary/tuple or list of dictionaries/tuples is accepted positionally.zDict[_DMLColumnArgument, Any]T)r9r8lenrrr rrQrrrrrrrrrurr~rrrrr6r immutabledict) rnargskwargsr!multi_kv_generatorrr kv_generator coerced_args rWrValuesBase.valuessh  q'C''%TQ''D C!9!9:::c!fd33)1)B)B*..'&&+=d+H*JJ&K:c!ftUm<<&&3&0&K =&dF333358 c4JK4Jquue|4JK 6?C''D 006II <iik4@A <<<<--k:DL  --k:DL 1Ls H")rrurur@)rz/Union[_DMLColumnKeyMapping[Any], Sequence[Any]]rrrr:)rrrrrir_supports_multi_parametersrqrrrrrrfrrsrqrrrrrTrZrWrrs%#N!&$(F !(43707)EIG AH  FJOBI)-M&-GT K  g g  g ggrZrc B^\rSrSr%SrSrSrSrSrSr S\ S'Sr S \ S 'S \ R4S \ R4S \ R4S \ R 4S\ R"4S\ R4S\ R4S\ R$4S\ R&4S\ R4S\ R$4S\ R4/ \R*-\R.-\R2-\R6-rS$U4Sjjr\S%Sj5r\S&S'Sjj5r \!(a\"SS.S(Sjj5r#\"SS.S)Sjj5r#\"SS.S*Sjj5r#\"SS.S+Sjj5r#\"SS.S,Sjj5r#\"SS.S-Sjj5r#\"SS.S.Sjj5r#\"SS.S/S jj5r#\"SS.S0S!jj5r#SS.S0S"jjr#S#r$U=r%$S#r$U=r%$)1rizRepresent an INSERT construct. The :class:`_expression.Insert` object is created using the :func:`_expression.insert()` function. rTNFrr9r4rursrrrrqrrrrr4rc$>[TU]U5 grSsuperrqrnru __class__s rWrqInsert.__init__ rZcSUlU$)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. Trsrs rWinline Insert.inlines$  rZc @UR(a[R"S5eUVs/sH'n[R"[ R USS9PM) snUlSUlX0l [R"[ RU5Ul U$s snf)aSReturn 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 expressionsTr) rr9rrrrrrrs#include_insert_from_select_defaults DMLSelectRolerq)rnnamesrqinclude_defaultsrts rW from_selectInsert.from_selectsR <<))B      U00$t D  3C0&&u':':FC   s.BrBcgrSrT)rn _Insert__ent0r*s rWrGInsert.returning'+.rZcgrSrT)rnr _Insert__ent1r*s rWrGr,s03rZcgrSrT)rnrr _Insert__ent2r*s rWrGr5s58rZcgrSrT)rnrrr _Insert__ent3r*s rWrGr?s:=rZcgrSrT)rnrrrr _Insert__ent4r*s rWrGrJs?BrZcgrSrT)rnrrrrr _Insert__ent5r*s rWrGrVs DGrZcgrSrT) rnrrrrrr _Insert__ent6r*s rWrGrcs ILrZc grSrT) rnrrrrrrr _Insert__ent7r*s rWrGrqs rZcgrSrTrnr*r; _Insert__kws rWrGrs $'rZcgrSrTrs rWrGrs $'rZ)rsrrrqrrr:)T)rzSequence[_DMLColumnArgument]rqrPrrrr:)r _TCCA[_T0]r*rrzReturningInsert[Tuple[_T0]])rrr _TCCA[_T1]r*rrz ReturningInsert[Tuple[_T0, _T1]]) rrrrr _TCCA[_T2]r*rrz%ReturningInsert[Tuple[_T0, _T1, _T2]]) rrrrrrr _TCCA[_T3]r*rrz*ReturningInsert[Tuple[_T0, _T1, _T2, _T3]])rrrrrrrrr _TCCA[_T4]r*rrz/ReturningInsert[Tuple[_T0, _T1, _T2, _T3, _T4]])rrrrrrrrrrr _TCCA[_T5]r*rrz4ReturningInsert[Tuple[_T0, _T1, _T2, _T3, _T4, _T5]])rrrrrrrrrrrrr _TCCA[_T6]r*rrz9ReturningInsert[Tuple[_T0, _T1, _T2, _T3, _T4, _T5, _T6]])rrrrrrrrrrrrrrr _TCCA[_T7]r*rrz>ReturningInsert[Tuple[_T0, _T1, _T2, _T3, _T4, _T5, _T6, _T7]])r;rer*rrrrzReturningInsert[Any])&rrrrrirrrqrr9rr7r7dp_clauseelement dp_booleandp_string_list dp_dml_valuesdp_dml_multi_valuesdp_clauseelement_tupledp_table_hint_listr1 _has_prefixes_traverse_internalsr$"_dialect_kwargs_traverse_internalsr%_executable_traverse_internalsr0_has_ctes_traverse_internals_traverse_internalsrqrrrrr rGr __classcell__rs@rWrrsN!% F*/'%*d*I '88 9 )44 5 />> ? )77 8 /CC D (99 : "$5$F$F G ,CC D (;; < !2!=!= >*!88 ():)E)E F "  6 6# 7$  : :% ;&  3 3' 4(  - -) .0 ( "& 4+44 4  44l IN .$ .BF . ( .  .  -2  3 3 3 &*  3 .  3  3 -2  8 8 8  8 &*  83 8  8 -2 = = =  =   =&* =8 =  = -2 B B B B  B  B&* B= B  B -2 G G G G  G  G G&* GB G  G -2 L L L L  L  L L L&* LG L  L -2              &*     $ -2 '. '&* '  ' "  '  '-2 '. '&* '  ' "  ' 'WrZrc\rSrSrSrSrg)ReturningInsertizTyping-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 rTNrrrrrirrTrZrWrrrZrct\rSrSr%S\S'SrS\S'\S Sj5rSSjrSS jr SS jr \ SS j5r Sr g )rirrurTzTuple[ColumnElement[Any], ...]rcUH<n[R"[RX S9nU=RU4- slM> U$)apReturn 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` rv)rrrWhereHavingRoler)rn whereclause criterionwhere_criterias rWwhereDMLWhereBase.wheresF,%I1:1A1A%%y2N  ^$5 5 %  rZc UR"U6$)zRA synonym for the :meth:`_dml.DMLWhereBase.where` method. .. versionadded:: 1.4 )r)rncriterias rWfilterDMLWhereBase.filterszz8$$rZcUR$rSrurs rW_filter_by_zeroDMLWhereBase._filter_by_zeros zzrZc UR5nUR5VVs/sHup4[X#5U:HPM nnnUR"U6$s snnf)zGapply the given filtering criterion as a WHERE clause to this select. )rrrr)rnr from_entityr~rclausess rW filter_byDMLWhereBase.filter_bys\ **, %lln ,  "+ 3u <,  {{G$$  sAcB[R"UR5$)zReturn 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_whereclauserrs rWrDMLWhereBase.whereclauses !;;    rZN)rz_ColumnExpressionArgument[bool]rr:)rz roles.ExpressionElementRole[Any]rr:r)rrrr:)rrf)rrrrrrrrrrrrrrrTrZrWrrsH 68O388% %  rZrc V^\rSrSrSrSrSrS\R4S\R4S\R4S\R4S \R4S \R4S \R4S \R4S \R4/ \R-\R"-\R&-\R*-rSU4Sjjr\SSj5r\SSj5r\(a\SSj5r\S Sj5r\S!Sj5r\S"Sj5r\S#Sj5r\S$Sj5r\S%Sj5r\S&Sj5r\S'Sj5rS'SjrSrU=r$SrU=r$)(rizRepresent an Update construct. The :class:`_expression.Update` object is created using the :func:`_expression.update()` function. rTrurrsrfrrrr4rc$>[TU]U5 grSrrs rWrqUpdate.__init__ rrZcUR(a[R"S5eUR(a[R"S5e[R U5R nU"XS5UlU$)aUSpecify 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)rr9r8rfrQrr)rnrrs rWordered_valuesUpdate.ordered_valuessn, <<##;  ! !##C  006II +D= rZcSUlU$)aMake 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. Trrs rWr Update.inline3s   rZcgrSrT)rn _Update__ent0s rWrGUpdate.returningLrrZcgrSrT)rnr _Update__ent1s rWrGrQ03rZcgrSrT)rnrr _Update__ent2s rWrGrV58rZcgrSrT)rnrrr _Update__ent3s rWrGr[:=rZcgrSrT)rnrrrr _Update__ent4s rWrGrd?BrZcgrSrT)rnrrrrr _Update__ent5s rWrGrn DGrZcgrSrT)rnrrrrrr _Update__ent6s rWrGry ILrZc grSrT) rnrrrrrrr _Update__ent7s rWrGr rZcgrSrTrnr; _Update__kws rWrGr$'rZcgrSrTrs rWrGr#&rZ)rsrfr)rzTuple[_DMLColumnArgument, Any]rr:r)rrrzReturningUpdate[Tuple[_T0]])rrrrrz ReturningUpdate[Tuple[_T0, _T1]])rrrrrrrz%ReturningUpdate[Tuple[_T0, _T1, _T2]]) rrrrrrrrrz*ReturningUpdate[Tuple[_T0, _T1, _T2, _T3]]) rrrrrrrrrrrz/ReturningUpdate[Tuple[_T0, _T1, _T2, _T3, _T4]])rrrrrrrrrrrrrz4ReturningUpdate[Tuple[_T0, _T1, _T2, _T3, _T4, _T5]])rrrrrrrrrrrrrrrz9ReturningUpdate[Tuple[_T0, _T1, _T2, _T3, _T4, _T5, _T6]])rrrrrrrrrrrrrrrrrz>ReturningUpdate[Tuple[_T0, _T1, _T2, _T3, _T4, _T5, _T6, _T7]])r;rerrrzReturningUpdate[Any]) rrrrrir is_updater7rrrdp_dml_ordered_valuesrrr1rr$rr%rr0rrrqrrrrr rGrrrs@rWrrsNI'88 9  1 H H I )44 5  1 G G H )77 8 ,CC D (;; < !2!=!= >*!88    6 6 7  : : ;  3 3! 4"  - -# .*   D$  .$ . ( .  .  3$ 3.8 3 - 3  3  8$ 8.8 8BL 8 2 8  8  = = =  =   = 8  =  =  B B B  B   B   B= B  B  G G G  G   G   G GB G  G  L L L L  L  L L LG L  L                  '4 '>A ' ! '  ' '4 '>A ' ! ' 'krZrc\rSrSrSrSrg)ReturningUpdateizTyping-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 rTNrrTrZrWrrrrZrc\rSrSrSrSrSrS\R4S\R4S\R4S\R4/\ R-\ R-\R -\R$-rSS jr\(a\SS j5r\SS j5r\SS j5r\SS j5r\SSj5r\SSj5r\SSj5r\SSj5r\SSj5rSSjrSrgSrg) r izRepresent a DELETE construct. The :class:`_expression.Delete` object is created using the :func:`_expression.delete()` function. rTrurrrcT[R"[RXS9Ulgrurxrys rWrqDelete.__init__r{rZcgrSrT)rn _Delete__ent0s rWrGDelete.returningrrZcgrSrT)rnr _Delete__ent1s rWrGrrrZcgrSrT)rnrr _Delete__ent2s rWrGrrrZcgrSrT)rnrrr _Delete__ent3s rWrGrrrZcgrSrT)rnrrrr _Delete__ent4s rWrGrrrZcgrSrT)rnrrrrr _Delete__ent5s rWrGrrrZcgrSrT)rnrrrrrr _Delete__ent6s rWrGrrrZc grSrT) rnrrrrrrr  _Delete__ent7s rWrGr rrZcgrSrTrnr; _Delete__kws rWrGrrrZcgrSrTr$s rWrGrr rZrNr)rrrzReturningDelete[Tuple[_T0]])rrrrrz ReturningDelete[Tuple[_T0, _T1]])rrrrrrrz%ReturningDelete[Tuple[_T0, _T1, _T2]]) rrrrrrrrrz*ReturningDelete[Tuple[_T0, _T1, _T2, _T3]]) rrrrrrrrrrrz/ReturningDelete[Tuple[_T0, _T1, _T2, _T3, _T4]])rrrrrrrrrrrrrz4ReturningDelete[Tuple[_T0, _T1, _T2, _T3, _T4, _T5]])rrrrrrrrrrrrr rrz9ReturningDelete[Tuple[_T0, _T1, _T2, _T3, _T4, _T5, _T6]])rrrrrrrrrrrrr rr"rrz>ReturningDelete[Tuple[_T0, _T1, _T2, _T3, _T4, _T5, _T6, _T7]])r;rer%rrzReturningDelete[Any])rrrrrir is_deleter7rrrr1rr$rr%rr0rrrqrr rGrrTrZrWr r sMNI'88 9  1 H H I ,CC D (;; <   6 6  7  : : ;  3 3 4  - - .   .$ . ( .  .  3$ 3.8 3 - 3  3  8$ 8.8 8BL 8 2 8  8  = = =  =   = 8  =  =  B B B  B   B   B= B  B  G G G  G   G   G GB G  G  L L L L  L  L L LG L  L                  '4 '>A ' ! '  ' '4 '>A ' ! 'krZr c\rSrSrSrSrg)ReturningDeletei$zTyping-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 rTNrrTrZrWr)r)$rrZr))rVrQrzTypeGuard[UpdateDMLState])rVrQrzTypeGuard[DeleteDMLState])rVrQrzTypeGuard[InsertDMLState])uri __future__rcollections.abcabcroperatortypingrrrrrr r r r r rrrrrrrrrr_typingrrrrbaserrrrr r!r"r#r$r%r&r'elementsr(r)r*r+r,rYr-r.r/r0r1r2r3r4r5sqltypesr6visitorsr7r9 util.typingr:r;r<r=r>r?r@rArBrCrDrErFrGrHrI_TCCArJrorKrLrMrNrOrPrXr\r^ attrgetterr_rh_DMLColumnElementrrQ plugin_forrrrDMLRolerirrrrrrr r)rTrZrWr;s #)! #&)'$#"!'#"#-"#(#('#2/+-*<.%,1+"&AAA"":.H"":.H"":.H T#|C001eT12R |R jH-C@XC@.C@LH-%X%.%PH-  X  .  G  MM G TSSll'Zl'^ f.s3 I I Xq'\:q'h f.s3 u'\:u'p f.s3 rZ