+h`%ddlmZddlmZddlmZddlmZddlmZddlmZddlm Z dd lm Z dd l m Z dd lmZdd lmZdd lmZdZGdde Z ee ddZGddeZGddeZGddeZy))ext)util) coercions)roles)schema)_exclusive_against) _generative)ColumnCollection)Insert) ClauseElement)alias)public_factory)r insertceZdZdZdZdZejdZe dddiZ e e d d Z e e d d Z y) r a PostgreSQL-specific implementation of INSERT. Adds methods for PG-specific syntaxes such as ON CONFLICT. The :class:`_postgresql.Insert` object is created using the :func:`sqlalchemy.dialects.postgresql.insert` function. .. versionadded:: 1.1 postgresqlFcDt|jdjS)akProvide the ``excluded`` namespace for an ON CONFLICT statement PG's ON CONFLICT clause allows reference to the row that would be inserted, known as ``excluded``. This attribute provides all columns in this row to be referenceable. .. tip:: The :attr:`_postgresql.Insert.excluded` attribute is an instance of :class:`_expression.ColumnCollection`, which provides an interface the same as that of the :attr:`_schema.Table.c` collection described at :ref:`metadata_tables_and_columns`. With this collection, ordinary names are accessible like attributes (e.g. ``stmt.excluded.some_column``), but special names and dictionary method names should be accessed using indexed access, such as ``stmt.excluded["column name"]`` or ``stmt.excluded["values"]``. See the docstring for :class:`_expression.ColumnCollection` for further examples. .. seealso:: :ref:`postgresql_insert_on_conflict` - example of how to use :attr:`_expression.Insert.excluded` excluded)name)rtablecolumns)selfs U/var/www/html/venv/lib/python3.12/site-packages/sqlalchemy/dialects/postgresql/dml.pyrzInsert.excluded(s2TZZj1999_post_values_clausezCThis Insert construct already has an ON CONFLICT clause established)msgsNc,t||||||_y)as Specifies a DO UPDATE SET action for ON CONFLICT clause. Either the ``constraint`` or ``index_elements`` argument is required, but only one of these can be specified. :param constraint: The name of a unique or exclusion constraint on the table, or the constraint object itself if it has a .name attribute. :param index_elements: A sequence consisting of string column names, :class:`_schema.Column` objects, or other column expression objects that will be used to infer a target index. :param index_where: Additional WHERE criterion that can be used to infer a conditional target index. :param set\_: A dictionary or other mapping object where the keys are either names of columns in the target table, or :class:`_schema.Column` objects or other ORM-mapped columns matching that of the target table, and expressions or literals as values, specifying the ``SET`` actions to take. .. versionadded:: 1.4 The :paramref:`_postgresql.Insert.on_conflict_do_update.set_` parameter supports :class:`_schema.Column` objects from the target :class:`_schema.Table` as keys. .. warning:: This dictionary does **not** take into account Python-specified default UPDATE values or generation functions, e.g. those specified using :paramref:`_schema.Column.onupdate`. These values will not be exercised for an ON CONFLICT style of UPDATE, unless they are manually specified in the :paramref:`.Insert.on_conflict_do_update.set_` dictionary. :param where: Optional argument. If present, can be a literal SQL string or an acceptable expression for a ``WHERE`` clause that restricts the rows affected by ``DO UPDATE SET``. Rows not meeting the ``WHERE`` condition will not be updated (effectively a ``DO NOTHING`` for those rows). .. versionadded:: 1.1 .. seealso:: :ref:`postgresql_insert_on_conflict` N)OnConflictDoUpdater)r constraintindex_elements index_whereset_wheres ron_conflict_do_updatezInsert.on_conflict_do_updateKs~$6  T5$  rc(t||||_y)a) Specifies a DO NOTHING action for ON CONFLICT clause. The ``constraint`` and ``index_elements`` arguments are optional, but only one of these can be specified. :param constraint: The name of a unique or exclusion constraint on the table, or the constraint object itself if it has a .name attribute. :param index_elements: A sequence consisting of string column names, :class:`_schema.Column` objects, or other column expression objects that will be used to infer a target index. :param index_where: Additional WHERE criterion that can be used to infer a conditional target index. .. versionadded:: 1.1 .. seealso:: :ref:`postgresql_insert_on_conflict` N)OnConflictDoNothingrrrr r!s ron_conflict_do_nothingzInsert.on_conflict_do_nothings>$7  $  rNNNNNNNN)__name__ __module__ __qualname____doc__stringify_dialect inherit_cachermemoized_propertyrr _on_conflict_exclusiver r$r(rrr r s %M ::40 !$0   ? ? B@D  rr z.dialects.postgresql.insertz.dialects.postgresql.InsertceZdZdZddZy)OnConflictClauserNc|Tt|tjs:t|tjt j frt|dxs|}|| tdt|tjr||_ d|_ d|_ nt|tjr+|j}|jdjd}n]t|t j r|j }|j"}n*|j }|jdjd}|d|_ ||_ ||_ y|dx|_ x|_ |_ yy)Nrz8'constraint' and 'index_elements' are mutually exclusiverr#) isinstancer string_typesr ConstraintrExcludeConstraintgetattr ValueErrorconstraint_targetinferred_target_elementsinferred_target_whereclauseIndex expressionsdialect_optionsgetrr#r's r__init__zOnConflictClause.__init__sc  !j$*;*;<""C$9$9:B%Z8FJ  !) N*d&7&78)3&04-370J 5!+!7!7(88FJJ J(=(=>!+!3!3(.. !+!3!3(88FJJ   %%)D ",:D )/:D ,  48 8D " 8-0 rr*)r+r,r-r/rDr3rrr5r5s $(8rr5ceZdZdZy)r&r(N)r+r,r-__visit_name__r3rrr&r&s-Nrr&c.eZdZdZ dfd ZxZS)rr$ctt| ||||j|j t dt |tr |s2t dt |tr t|}n t d|jDcgc]+\}}tjtj||f-c}}|_||_ycc}}w)N)rr r!zVEither constraint or index_elements, but not both, must be specified unless DO NOTHINGz*set parameter dictionary must not be emptyzqset parameter must be a non-empty dictionary or a ColumnCollection such as the `.c.` collection of a Table object)superrrDr>r=r<r7dictr itemsrexpectr DMLColumnRoleupdate_values_to_setupdate_whereclause) rrr r!r"r#keyvalue __class__s rrDzOnConflictDoUpdate.__init__s  $0!)# 1   ) ) 1&&.D  dD ! !MNN . /:D$ #jjl% U  e113 7 ?% !#( % s0Cr))r+r,r-rFrD __classcell__)rRs@rrrs#,N  &(&(rrN)rrsqlrrrsql.baser r r sql.dmlr StandardInsert sql.elementsr sql.expressionrutil.langhelpersr__all__rr5r&rr3rrr]s}*#(/)#. V ^V r  )+H  +8}+8\.*.)())(r