-h SrSSKJr SSKJr SSKJr SSKJr SSKJ r SSKJ r SS KJ r SS KJ r SS KJ r SS KJr SS KJr SSKJr SSKJr SSKJr SSKJr SSKJr SSKJr SSKJr SSKJr SSKJr SSKJr SSKJr SSKJr "SS\5r\R>"SS5"SS\55r \R>"SS 5"S!S"\55r!\R>"SS#5"S$S%\55r""S&S'\RF\\\\\\\5 r$"S(S)\$5r%"S*S+\%5r&"S,S-\'5r("S.S/\(\%5r)"S0S1\(\$5r*g2)3zd Provide :class:`_expression.Insert`, :class:`_expression.Update` and :class:`_expression.Delete`. )NullType) coercions)roles)util)_entity_namespace_key)_exclusive_against) _from_objects) _generative)ColumnCollection) CompileState) DialectKWArgs) Executable)HasCompileState)BooleanClauseList) ClauseElement)Null)HasCTE) HasPrefixes) ReturnsRows)InternalTraversal)exc)collections_abcc\rSrSrSrSrSrSrSrSr Sr Sr Sr Sr \S5r\S5r\S5r\S 5rS rS rS rS rSrSrSrg)DMLState%TNFc [5eNNotImplementedErrorself statementcompilerkws gC:\Users\ROHAN GUPTA\OneDrive\Desktop\mathbuddy-assessment\venv\Lib\site-packages\sqlalchemy/sql/dml.py__init__DMLState.__init__0s !##cHURRURS.$)N)nametable)r-r,)clsr$s r'get_entity_descriptionDMLState.get_entity_description3s!,,yGGr*cvURVs/sHnURURUS.PM sn$s snf)N)r,typeexpr)_all_selected_columnskeyr2)r.r$cs r'!get_returning_column_descriptions*DMLState.get_returning_column_descriptions7sF44  5   5    s$6c.URR$r)r$r-r#s r' dml_tableDMLState.dml_tableBs~~###r*c UVVs/sHWup4[R"[RU5[R"[RU[ 5SS94PMY snn$s snnf)NT)type_is_crud)rexpectr DMLColumnRoleExpressionElementRoler)r.r$ kv_iteratorkvs r'_get_crud_kv_pairsDMLState._get_crud_kv_pairsFsi$  $  !4!4a8  //"*  $   sAA(cr/n[[R"UR55nUS1nURHan[ U5HOnUR UR5(dURU5 URUR5 MQ Mc URUSS5 U$)Nrr) listsql_utiltables_from_leftmostr-_where_criteriar intersection _cloned_setappendupdateextend)r#r$froms all_tablesseencrititems r'_make_extra_fromsDMLState._make_extra_fromsUs(77 HI 1 --D%d+(()9)9::LL& D,,-,.  Z^$ r*c UR(d1[R"SURR 5-5eUR HnUVVVs/sHdn[ U[R5(a@[URRU5VVs0sHupEURU_M snnOUPMf nnnnUR(a*SUl SUlX`lURSUlMUR(dUR#5 MURR%U5 M gs snnfs snnnf)Nz6%s construct does not support multiple parameter sets.FTr)_supports_multi_parametersrInvalidRequestError__visit_name__upper _multi_values isinstancerSequencezipr-r6r5_no_parameters_has_multi_parameters_multi_parameters_dict_parameters_cant_mix_formats_errorrQ)r#r$ parameters parameter_setr6valuemulti_parameterss r'_process_multi_valuesDMLState._process_multi_valuesds-33))+-6-E-E-K-K-MN  $11J&0 &0Mm_-E-EFF%( (9(9=$I$IEE5L$I # # &0  ""&+#-1*)9&(,(>(>q(A%//,,.&&--.>?'2 sAE E9 E E cUR(a SUlURUlSUlgUR(aUR 5 gg)NF)rbrc_valuesrerf)r#r$s r'_process_valuesDMLState._process_valuessC   ).D &$-$5$5D !"'D   ' '  ( ( *(r*c,URnUR(a:SUl[U5UlX lUVVs/sHup4UPM snnUlgUR (aUR 5 g[R"S5es snnf)NFzQCan only invoke ordered_values() once, and not mixed with any other values() call) _ordered_valuesrbdictre_parameter_orderingrcrfrr[)r#r$rgr5ris r'_process_ordered_values DMLState._process_ordered_valuess}..   "'D $($4D !#- >H'Ij j'ID $  ' '  ( ( *))/  (JsBc URVs0sH0n[R"[RUSS9[ 5_M2 nnUR (aSUlX0lgS5es snf)NT)as_keyFz%This statement already has parameters) _select_namesrr@rrArrbre)r#r$r,rgs r'_process_select_valuesDMLState._process_select_valuessr"// /   U00$t Ddf L/    "'D $. ! BA A5 s7A.c.[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.)rr[r:s r'rf DMLState._cant_mix_formats_errors%%   r*)rercrdrbrrrt)__name__ __module__ __qualname____firstlineno__rbrerdrrrtrcisupdateisdeleteisinsertr( classmethodr/r7propertyr;rFrWrkrorurzrf__static_attributes__r*r'rr%sNO!HHH$HH  $$     @8+ B r*rdefaultinsertcF\rSrSrSrSrSr\RS5r Sr g)InsertDMLStateTFc XlSUlUR(aURU5 URbUR U5 UR (aURU5 ggNT)r$rryrzrnror^rkr"s r'r(InsertDMLState.__init__s["  " "  ' ' 2    (   +  " "  & &y 1 #r*cURVs/sH(n[R"[RU5PM* sn$s snfr)rer expect_as_keyrrA)r#cols r'_insert_col_keysInsertDMLState._insert_col_keyssB ,, ,  # #E$7$7 =,   s/A)rr$N) r~rrrrinclude_table_with_column_exprsr(rmemoized_propertyrrrr*r'rrs,H&+# 2   r*rrPc"\rSrSrSrSrSrSrg)UpdateDMLStateTFc XlSUlURUlURbUR U5 OAUR bUR U5 O"UR(aURU5 URU5=Ul nU=(a UR=Ul nU=(a URUlgr)r$r_preserve_parameter_orderrrrurnror^rkrW _extra_fromsre is_multitable'render_table_with_column_in_update_fromr)r#r$r%r&efmts r'r(UpdateDMLState.__init__s" )2)L)L&  $ $ 0  ( ( 3    *   +  $ $  & &y 1!%!7!7 !BBB"$">)>)>>R  C8CC ,r*)rrrrrr$N)r~rrrrrr(rrr*r'rrsH&+# r*rdeletec\rSrSrSrSrSrg)DeleteDMLStateTc JXlSUlURU5Ulgr)r$rrWrr"s r'r(DeleteDMLState.__init__s!"  229=r*)rrr$N)r~rrrrr(rrr*r'rrs H>r*rc@\rSrSrSrSr\RRSS05r\ R"5r Sr Sr SrSrSr\S 5rS rS r\S 5rS rSrSr\"\\5r\S5r\S5r\S5r\SSj5r\S5r\S5r Sr!g) UpdateBasezDForm the base for ``INSERT``, ``UPDATE``, and ``DELETE`` statements. update_base autocommitTFNrc [SSSSSSSSS 9n[R"S 0UVs0sHnUS XES U-S U-S .-4_M snD6$s snf)NzThe :paramref:`%(func)s.whereclause` parameter will be removed in SQLAlchemy 2.0. Please refer to the :meth:`%(classname)s.where` method.zThe :paramref:`%(func)s.values` parameter will be removed in SQLAlchemy 2.0. Please refer to the :meth:`%(classname)s.values` method.zuThe :paramref:`%(func)s.bind` parameter will be removed in SQLAlchemy 2.0. Please use explicit connection execution.zThe :paramref:`%(func)s.inline` parameter will be removed in SQLAlchemy 2.0. Please use the :meth:`%(classname)s.inline` method.zThe :paramref:`%(func)s.prefixes parameter will be removed in SQLAlchemy 2.0. Please use the :meth:`%(classname)s.prefix_with` method.zThe :paramref:`%(func)s.return_defaults` parameter will be removed in SQLAlchemy 2.0. Please use the :meth:`%(classname)s.return_defaults` method.zThe :paramref:`%(func)s.returning` parameter will be removed in SQLAlchemy 2.0. Please use the :meth:`%(classname)s.returning`` method.zThe :paramref:`%(func)s.preserve_parameter_order` parameter will be removed in SQLAlchemy 2.0. Use the :meth:`%(classname)s.ordered_values` method with a list of tuples. ) whereclausevaluesbindinlineprefixesreturn_defaults returningpreserve_parameter_orderz2.0z_expression.%s)func classnamer)rsrdeprecated_params)r.fn_nameclsnamenamesparam_to_method_lookupr,s r'_constructor_20_deprecations'UpdateBase._constructor_20_deprecationss"&6 7 M7 @ ; Q-" ^%%  " "D*0 07 :%5%?"    sA cd^TRRU4SjUR55 g)Nc3D># UHoRT5v M g7fr) _make_proxy).0r fromclauses r' AUpdateBase._generate_fromclause_column_proxies..Fs4 3BCOOJ ' '?s )_columns_populate_separate_keys _returning)r#rs `r'#_generate_fromclause_column_proxies.UpdateBase._generate_fromclause_column_proxiesEs(334 37??4  r*c[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).r )r#argr&s r'paramsUpdateBase.paramsJs" *  r*c &URU5 g)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. N)_validate_dialect_kwargs)r#opts r'with_dialect_optionsUpdateBase.with_dialect_optionsXs %%c*r*c[R"SURR-5 UR U5 g)NzPassing dialect keyword arguments directly to the %s constructor is deprecated and will be removed in SQLAlchemy 2.0. Please use the ``with_dialect_options()`` method.)rwarn_deprecated_20 __class__r~r)r# dialect_kws r'#_validate_dialect_kwargs_deprecated.UpdateBase._validate_dialect_kwargs_deprecatedgs:  F~~&& ( %%j1r*cTUR=(d URR$)zeReturn a 'bind' linked to this :class:`.UpdateBase` or a :class:`_schema.Table` associated with it. )_bindr-rr:s r'rUpdateBase.bindps zz,TZZ__,r*cXlgr)r)r#rs r' _set_bindUpdateBase._set_bindws r*cUR(a[R"S5eU=R[ SU55- slg)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) 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) 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. .. seealso:: :meth:`.ValuesBase.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` z9return_defaults() is already configured on this statementc3l# UH*n[R"[RU5v M, g7fr)rr@rColumnsClauseRolerr6s r'r'UpdateBase.returning..s)! BFQI  U44a 8 8$s24N)_return_defaultsrr[rtupler#colss r'rUpdateBase.returning|sHN  ))K  5! BF!   r*cUR$r)rr:s r'r4 UpdateBase._all_selected_columnss r*cV[SUR55R5$)z`Return the RETURNING columns as a column collection for this statement. .. versionadded:: 1.4 c3<# UHoRU4v M g7fr)r5rs r'r.UpdateBase.exported_columns..s :1UUAJ :s)r r4 as_immutabler:s r'exported_columnsUpdateBase.exported_columnss+  $ : :  ,. r*chUc URnURRX#4U05Ulg)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. N)r-_hintsunion)r#text selectable dialect_names r' with_hintUpdateBase.with_hints1>  Jkk''*)CT(JK r*cP[RU5RnU"U5$)aReturn 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 )rget_plugin_classr/r#meths r'entity_descriptionUpdateBase.entity_descriptions%B((.EEDzr*cP[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 )rrr7rs r'returning_column_descriptions(UpdateBase.returning_column_descriptions$s-T((  + + Dzr*)rr)N*)"r~rrr__doc__r\r_execution_optionsrr immutabledictrnamed_with_columnr_return_defaults_columnsris_dmlrrrrr rrrrrrr4rrrrrrr*r'rrs#O"N#66<< t   !F#J F= = ~   + +2- D) $DL L \  !L!LF!!F,,r*rc\rSrSrSrSrSrSrSrSr Sr Sr Sr Sr SrSr\\"SS S S S .S 9S55r\\"SSS0S\0S9S55rSrg) ValuesBaseiTzPSupplies support for :meth:`.ValuesBase.values` to INSERT and UPDATE constructs. values_baseFNrc[R"[RXS9UlUbUR R X5 U(aURU5 gg)Napply_propagate_attrs)rr@r DMLTableRoler-rnon_generative_setup_prefixes)r#r-rrs r'r(ValuesBase.__init__fsO%%        KK & &t 4    * r*ryrrz,This construct already inserts from a SELECT1This statement already has ordered values present)ryrr)msgsc<U(Ga4USnU(a[R"S5e[U5S:a[R"S5eUR(d[ U[ R 5(aU(a:[ US[[[45(aU=RU4- sl g[URRU5VVs0sHupEURU_M nnnO[UR(a*[ U[ R 5(d [S5eOUnU(a[R"S5e[ R#U5R$nUR(aU"X5UlgU"XR)55VVs0sHupxXx_M nnnUR*(a!UR*R-U5Ulg[.R0"U5Ulgs snnfs 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:: 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. .. versionchanged:: 1.0.0 an INSERT that uses a multiple-VALUES clause, even a list of length one, implies that the :paramref:`_expression.Insert.inline` flag is set to True, indicating that the statement will not attempt to fetch the "last inserted primary key" or other defaults. The statement deals with an arbitrary number of rows, so the :attr:`_engine.CursorResult.inserted_primary_key` accessor does not apply. .. versionchanged:: 1.0.0 A multiple-VALUES INSERT now supports columns with Python side default values and callables in the same way as that of an "executemany" style of invocation; the callable is invoked for each row. See :ref:`bug_3288` for other details. The 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.NzOWhen preserve_parameter_order is True, values() only accepts a list of 2-tuples)r ArgumentErrorlenrr_rr`rIrsrr^rar-r6r5 ValueErrorrrrFrritemsrnrrr) r#argskwargsrr6ri kv_generatorrDrEs r'rValuesBase.valuesost  q'C''%TQ''D 33 _--99:c!ftT5.ABB&&3&0&58 c4JK4Jquue|4JK// _--99!?C''D 006II  ) )#/#:D $0yy{$CD$CDA14$CCD||#||11#6 #11#6 EL<Es $H3Hrz1RETURNING is already configured on this statement)rdefaultscSUlXlg)a Make use of a :term:`RETURNING` clause for the purpose of fetching server-side expressions and defaults. E.g.:: stmt = table.insert().values(data='newdata').return_defaults() result = connection.execute(stmt) server_created_at = result.returned_defaults['created_at'] When used against a backend that supports RETURNING, all column values generated by SQL expression or server-side-default will be added to any existing RETURNING clause, provided that :meth:`.UpdateBase.returning` is not used simultaneously. The column values will then be available on the result using the :attr:`_engine.CursorResult.returned_defaults` accessor as a dictionary, referring to values keyed to the :class:`_schema.Column` object as well as its ``.key``. This method differs from :meth:`.UpdateBase.returning` in these ways: 1. :meth:`.ValuesBase.return_defaults` is only intended for use with an INSERT or an UPDATE statement that matches exactly one row per parameter set. While the RETURNING construct in the general sense supports multiple rows for a multi-row UPDATE or DELETE statement, or for special cases of INSERT that return multiple rows (e.g. INSERT from SELECT, multi-valued VALUES clause), :meth:`.ValuesBase.return_defaults` is intended only for an "ORM-style" single-row INSERT/UPDATE statement. The row returned by the statement is also consumed implicitly when :meth:`.ValuesBase.return_defaults` is used. By contrast, :meth:`.UpdateBase.returning` leaves the RETURNING result-set intact with a collection of any number of rows. 2. It is compatible with the existing logic to fetch auto-generated primary key values, also known as "implicit returning". Backends that support RETURNING will automatically make use of RETURNING in order to fetch the value of newly generated primary keys; while the :meth:`.UpdateBase.returning` method circumvents this behavior, :meth:`.ValuesBase.return_defaults` leaves it intact. 3. It can be called against any backend. Backends that don't support RETURNING will skip the usage of the feature, rather than raising an exception. The return value of :attr:`_engine.CursorResult.returned_defaults` will be ``None`` 4. An INSERT statement invoked with executemany() is supported if the backend database driver supports the ``insert_executemany_returning`` feature, currently this includes PostgreSQL with psycopg2. 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 :meth:`.ValuesBase.return_defaults` is used by the ORM to provide an efficient implementation for the ``eager_defaults`` feature of :func:`.mapper`. :param cols: optional list of column key names or :class:`_schema.Column` objects. If omitted, all column expressions evaluated on the server are added to the returning list. .. versionadded:: 0.9.0 .. seealso:: :meth:`.UpdateBase.returning` :attr:`_engine.CursorResult.returned_defaults` :attr:`_engine.CursorResult.returned_defaults_rows` :attr:`_engine.CursorResult.inserted_primary_key` :attr:`_engine.CursorResult.inserted_primary_key_rows` TN)rr rs r'rValuesBase.return_defaults)sx!%(,%r*)rrrr rnr-)r~rrrrr\rZrselect_post_values_clausernr^rrryrr(r r rrrrr*r'r r Ts%#N!& % FGMOMJ+K  n7n7` M  + U-U-r*r c .^\rSrSrSrSrSrSrSrSr S\ R4S\ R4S \ R4S \ R4S \ R4S \ R4S \ R4S\ R 4S\ R"4S\ R4S\ R 4/ \R&-\R*-\R.-\R2-r\R9SS/SQ5SU4Sjj5r\S5r\SSj5r Sr!U=r"$)InsertizRepresent an INSERT construct. The :class:`_expression.Insert` object is created using the :func:`_expression.insert()` function. rTNFr-_inlineryrnr^r#r$rrrr )rrrrrrc >[[U] XU5 X@lX0lU(aX`lU(aUR U5 U(a$SUl[U[5(dXpl ggg)aConstruct an :class:`_expression.Insert` object. E.g.:: from sqlalchemy import insert stmt = ( insert(user_table). values(name='username', fullname='Full Username') ) Similar functionality is available via the :meth:`_expression.TableClause.insert` method on :class:`_schema.Table`. .. seealso:: :ref:`tutorial_core_insert` - in the :ref:`unified_tutorial` :param table: :class:`_expression.TableClause` which is the subject of the insert. :param values: collection of values to be inserted; see :meth:`_expression.Insert.values` for a description of allowed formats here. Can be omitted entirely; a :class:`_expression.Insert` construct will also dynamically render the VALUES clause at execution time based on the parameters passed to :meth:`_engine.Connection.execute`. :param inline: if True, no attempt will be made to retrieve the SQL-generated default values to be provided within the statement; in particular, this allows SQL expressions to be rendered 'inline' within the statement without the need to pre-execute them beforehand; for backends that support "returning", this turns off the "implicit returning" feature for the statement. If both :paramref:`_expression.Insert.values` and compile-time bind parameters are present, the compile-time bind parameters override the information specified within :paramref:`_expression.Insert.values` on a per-key basis. The keys within :paramref:`_expression.Insert.values` can be either :class:`~sqlalchemy.schema.Column` objects or their string identifiers. Each key may reference one of: * a literal data value (i.e. string, number, etc.); * a Column object; * a SELECT statement. If a ``SELECT`` statement is specified which references this ``INSERT`` statement's table, the statement will be correlated against the ``INSERT`` statement. .. seealso:: :ref:`tutorial_core_insert` - in the :ref:`unified_tutorial` TN) superr&r(rr'rrrr_boolr ) r#r-rrrrrrrrs r'r(Insert.__init__sbh fd$UH=  'O   4 4Z @ $(D !ot440?-5 r*cSUlg)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. TNr'r:s r'r Insert.inlines $ r*cUR(a[R"S5eXlSUlX0l[ R"[RU5Ul g)aReturn a new :class:`_expression.Insert` construct which represents an ``INSERT...FROM SELECT`` statement. e.g.:: sel = select(table1.c.a, table1.c.b).where(table1.c.c > 5) ins = table2.insert().from_select(['a', 'b'], sel) :param names: a sequence of string column names or :class:`_schema.Column` objects representing the target columns. :param select: a :func:`_expression.select` construct, :class:`_expression.FromClause` or other construct which resolves into a :class:`_expression.FromClause`, such as an ORM :class:`_query.Query` object, etc. The order of columns returned from this FROM clause should correspond to the order of columns sent as the ``names`` parameter; while this is not checked before passing along to the database, the database would normally raise an exception if these column lists don't correspond. :param include_defaults: if True, non-server default values and SQL expressions as specified on :class:`_schema.Column` objects (as documented in :ref:`metadata_defaults_toplevel`) not otherwise specified in the list of names will be rendered into the INSERT and SELECT statements, so that these values are also included in the data to be inserted. .. note:: A Python-side default that uses a Python callable function will only be invoked **once** for the whole statement, and **not per row**. .. versionadded:: 1.0.0 - :meth:`_expression.Insert.from_select` now renders Python-side and SQL expression column defaults into the SELECT statement for columns otherwise not included in the list of column names. .. versionchanged:: 1.0.0 an INSERT that uses FROM SELECT implies that the :paramref:`_expression.insert.inline` flag is set to True, indicating that the statement will not attempt to fetch the "last inserted primary key" or other defaults. The statement deals with an arbitrary number of rows, so the :attr:`_engine.CursorResult.inserted_primary_key` accessor does not apply. z0This construct already inserts value expressionsTN) rnrr[ryr'#include_insert_from_select_defaultsrr@r DMLSelectRoler#)r#rr#include_defaultss r' from_selectInsert.from_select&sQf <<))B # 3C0&&u':':FC r*)rr'rr rryr0r#)NFNNNF)T)#r~rrrrr\rZr#r0 is_insertrdp_clauseelement dp_booleandp_string_list dp_dml_valuesdp_dml_multi_valuesdp_clauseelement_tupledp_table_hint_listr _has_prefixes_traverse_internalsr"_dialect_kwargs_traverse_internalsr_executable_traverse_internalsr_has_ctes_traverse_internals_traverse_internalsr rr(r rr3r __classcell__rs@r'r&r&sN!% F*/'I'88 9 )44 5 />> ? )77 8 /CC D (99 : "$5$F$F G ,CC D (;; < !2!=!= >*!88   6 6! 7"  : :# ;$  3 3% 4&  - -' ..,,   S@ S@j&:D:Dr*r&cJ\rSrSrSr\S5rSrSrSr \ S5r Sr g) DMLWhereBaseidrcUH>n[R"[RU5nU=RU4- slM@ g)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` N)rr@rWhereHavingRolerL)r#r criterionwhere_criterias r'whereDMLWhereBase.wheregs:,%I&--e.C.CYON  ^$5 5 %r*c UR"U6$)zRA synonym for the :meth:`_dml.DMLWhereBase.where` method. .. versionadded:: 1.4 )rJ)r#criterias r'filterDMLWhereBase.filterszz8$$r*cUR$r)r-r:s r'_filter_by_zeroDMLWhereBase._filter_by_zeros zzr*c UR5nUR5VVs/sHup4[X#5U:HPM nnnUR"U6$s snnf)zGapply the given filtering criterion as a WHERE clause to this select. )rQrrrN)r#r from_entityr5riclausess r' 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_whereclauserLr:s r'rDMLWhereBase.whereclauses !;;    r*N) r~rrrrLr rJrNrQrVrrrrr*r'rErEds<O662% %  r*rEc ^\rSrSrSrSrSrS\R4S\R4S\R4S\R4S \R4S \R4S \R4S \R4S \R4/ \R-\R"-\R&-\R*-r\R1SS/SQ5SU4Sjj5r\S5r\S5rSrU=r$)UpdateizRepresent an Update construct. The :class:`_expression.Update` object is created using the :func:`_expression.update()` function. rPTr-rLr'rrrnrrrr )rrrrrrrrc  >Xl[[U]XU5 XPlU(aXplUb9U=R [R"[RU54- slX@l U (aURU 5 Xl g)a Construct an :class:`_expression.Update` object. E.g.:: from sqlalchemy import update stmt = ( update(user_table). where(user_table.c.id == 5). values(name='user #5') ) Similar functionality is available via the :meth:`_expression.TableClause.update` method on :class:`_schema.Table`. :param table: A :class:`_schema.Table` object representing the database table to be updated. :param whereclause: Optional SQL expression describing the ``WHERE`` condition of the ``UPDATE`` statement; is equivalent to using the more modern :meth:`~Update.where()` method to specify the ``WHERE`` clause. :param values: Optional dictionary which specifies the ``SET`` conditions of the ``UPDATE``. If left as ``None``, the ``SET`` conditions are determined from those parameters passed to the statement during the execution and/or compilation of the statement. When compiled standalone without any parameters, the ``SET`` clause generates for all columns. Modern applications may prefer to use the generative :meth:`_expression.Update.values` method to set the values of the UPDATE statement. :param inline: if True, SQL defaults present on :class:`_schema.Column` objects via the ``default`` keyword will be compiled 'inline' into the statement and not pre-executed. This means that their values will not be available in the dictionary returned from :meth:`_engine.CursorResult.last_updated_params`. :param preserve_parameter_order: if True, the update statement is expected to receive parameters **only** via the :meth:`_expression.Update.values` method, and they must be passed as a Python ``list`` of 2-tuples. The rendered UPDATE statement will emit the SET clause for each referenced column maintaining this order. .. versionadded:: 1.0.10 .. seealso:: :ref:`updates_order_parameters` - illustrates the :meth:`_expression.Update.ordered_values` method. If both ``values`` and compile-time bind parameters are present, the compile-time bind parameters override the information specified within ``values`` on a per-key basis. The keys within ``values`` can be either :class:`_schema.Column` objects or their string identifiers (specifically the "key" of the :class:`_schema.Column`, normally but not necessarily equivalent to its "name"). Normally, the :class:`_schema.Column` objects used here are expected to be part of the target :class:`_schema.Table` that is the table to be updated. However when using MySQL, a multiple-table UPDATE statement can refer to columns from any of the tables referred to in the WHERE clause. The values referred to in ``values`` are typically: * a literal data value (i.e. string, number, etc.) * a SQL expression, such as a related :class:`_schema.Column`, a scalar-returning :func:`_expression.select` construct, etc. When combining :func:`_expression.select` constructs within the values clause of an :func:`_expression.update` construct, the subquery represented by the :func:`_expression.select` should be *correlated* to the parent table, that is, providing criterion which links the table inside the subquery to the outer table being updated:: users.update().values( name=select(addresses.c.email_address).\ where(addresses.c.user_id==users.c.id).\ scalar_subquery() ) .. seealso:: :ref:`inserts_and_updates` - SQL Expression Language Tutorial N)rr)r\r(rrrLrr@rrGr'rr) r#r-rrrrrrrrrrs r'r(Update.__init__s{|*B& fd$UH= 'O  "    !6!6 D%     4 4Z @ /r*cUR(a[R"S5eUR(a[R"S5e[R U5R nU"X5Ulg)acSpecify 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 presentrN)rnrrrrrrrF)r#rrs r'ordered_valuesUpdate.ordered_valuesYsg0 <<##;  ! !##C  006II +D7r*cSUlg)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. TNr-r:s r'r Update.inline}s  r*)rr'rrrrr)NNFNNNFF)r~rrrrr\ is_updaterr6r;r7dp_dml_ordered_valuesr9r<rr=rr>rr?rr@rAr rr(r r`rrrBrCs@r'r\r\sYNI'88 9  1 H H I )44 5  1 G G H )77 8 ,CC D (;; < !2!=!= >*!88    6 6 7  : : ;  3 3! 4"  - -# .*,,  " !&|0 |0|!8!8Fr*r\c6\rSrSrSrSrSrS\R4S\R4S\R4S\R4/\ R-\ R-\R -\R$-r\R+SS/S Q5S S j5rS rg )DeleteizRepresent a DELETE construct. The :class:`_expression.Delete` object is created using the :func:`_expression.delete()` function. rTr-rLrr)rrrrrNc TX0l[R"[RXS9UlU(aX@lU(aURU5 Ub9U=R[R"[RU54- slU(aURU5 gg)aConstruct :class:`_expression.Delete` object. E.g.:: from sqlalchemy import delete stmt = ( delete(user_table). where(user_table.c.id == 5) ) Similar functionality is available via the :meth:`_expression.TableClause.delete` method on :class:`_schema.Table`. .. seealso:: :ref:`inserts_and_updates` - in the :ref:`1.x tutorial ` :ref:`tutorial_core_update_delete` - in the :ref:`unified_tutorial` :param table: The table to delete rows from. :param whereclause: Optional SQL expression describing the ``WHERE`` condition of the ``DELETE`` statement; is equivalent to using the more modern :meth:`~Delete.where()` method to specify the ``WHERE`` clause. .. seealso:: :ref:`deletes` - SQL Expression Tutorial rN) rrr@rrr-rrrLrGr)r#r-rrrrrs r'r(Delete.__init__sb %%      'O    *  "    !6!6 D%     4 4Z @ r*)rrr-)NNNN)r~rrrrr\ is_deleterr6r;r<rr=rr>rr?rr@rAr rr(rrr*r'rgrgsNI'88 9  1 H H I ,CC D (;; <   6 6  7  : : ;  3 3 4  - - .,,B  <A  <Ar*rgN)+rsqlalchemy.typesrrrrrJbaserr r r r r rrrelementsrrrrrrrvisitorsrrrr plugin_forrrrDMLRolerr r&objectrEr\rgrr*r'rssS &'$"!'###'"G |G TH- X . 2H- X . ,H->X>.>f MM fR r-r-j XDZXDvE 6E Pa\:aHZA\:ZAr*