Файловый менеджер - Редактировать - /opt/imh-python/lib/python3.9/site-packages/sqlalchemy/sql/__pycache__/dml.cpython-39.pyc
Ðазад
a _�hX� � @ s, d Z ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddl m Z ddl m Z dd l m Z dd l m Z dd l mZ dd l mZ dd lmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ G dd� deeeee�ZG dd� de�ZG dd� de�ZG dd� de�ZG dd � d e�Zd S ) zd Provide :class:`_expression.Insert`, :class:`_expression.Update` and :class:`_expression.Delete`. � )�util)� _from_objects)� _generative)� DialectKWArgs)� Executable)�_clone)�_column_as_key)�_literal_as_text)�and_)� ClauseElement)�Null)�_interpret_as_from)�_interpret_as_select)�HasCTE)� HasPrefixes� )�excc @ s� e Zd ZdZdZej�ddi�Ze� � Z dZ dZ dZ dZdd � Zd d � Zd d � Zdd� Zeee�Zedd� �Zeddd��ZdS )� UpdateBasezDForm the base for ``INSERT``, ``UPDATE``, and ``DELETE`` statements.Z update_baseZ autocommitTN� Fc s� �fdd�� �j rZ|d urZt|t�r6|r>t|d t�s>td��dd� |D ��_t|�dfS t|ttf�r�|r�t|d tttf�r��js�t� d��� fd d�|D �d fS � |�dfS d S ) Nc s2 t | ttf�r*tdd� t� jj| �D ��S | S d S )Nc s s | ]\}}|j |fV qd S �N)�key)�.0�cZpvalr r ��/root/rpmbuild/BUILDROOT/imh-python39-modules-3.9.7-92.el8.x86_64/opt/imh-python/lib/python3.9/site-packages/sqlalchemy/sql/dml.py� <genexpr>2 � zHUpdateBase._process_colparams.<locals>.process_single.<locals>.<genexpr>)� isinstance�list�tuple�dict�zip�tabler )�p��selfr r �process_single0 s z5UpdateBase._process_colparams.<locals>.process_single� zOWhen preserve_parameter_order is True, values() only accepts a list of 2-tuplesc S s g | ] \}}|�qS r r )r r �valuer r r � <listcomp>> r z1UpdateBase._process_colparams.<locals>.<listcomp>Fz8This construct does not support multiple parameter sets.c s g | ] }� |��qS r r )r r" )r% r r r( N r T) �_preserve_parameter_orderr r r � ValueError�_parameter_orderingr �_supports_multi_parametersr �InvalidRequestError)r$ � parametersr )r% r$ r �_process_colparams/ s0 � �� ����z UpdateBase._process_colparamsc 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).N)�NotImplementedError)r$ �arg�kwr r r �paramsR s �zUpdateBase.paramsc C s | j p | jjS )zuReturn a 'bind' linked to this :class:`.UpdateBase` or a :class:`_schema.Table` associated with it. )�_bindr! �bindr# r r r r5 ` s zUpdateBase.bindc C s || _ d S r )r4 )r$ r5 r r r � _set_bindg s zUpdateBase._set_bindc G s* | j rt�d��| jr t�d� || _dS )a� Add a :term:`RETURNING` or equivalent clause to this statement. e.g.:: stmt = table.update().\ where(table.c.data == 'value').\ values(status='X').\ returning(table.c.server_flag, table.c.updated_timestamp) for server_flag, updated_timestamp in connection.execute(stmt): print(server_flag, updated_timestamp) 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:: stmt = table.insert().returning( (table.c.first_name + " " + table.c.last_name). label('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.ResultProxy.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. z9return_defaults() is already configured on this statementz�The returning() method does not currently support multiple additive calls. The existing RETURNING clause being replaced by new columns.N)�_return_defaultsr r- � _returningr �warn�r$ �colsr r r � returningl s 6��zUpdateBase.returning�*c C s( |du r| j }| j�||f|i�| _dS )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)r! �_hints�union)r$ �text� selectableZ dialect_namer r r � with_hint� s zUpdateBase.with_hint)Nr= )�__name__� __module__� __qualname__�__doc__�__visit_name__r Z_execution_optionsr? r Z immutabledictr> r+ � _prefixesZnamed_with_columnr7 r/ r3 r5 r6 �propertyr r< rB r r r r r s& �# Ar c @ sH e Zd ZdZdZdZdZdZdZdZ dd� Z e dd� �Z e d d � �Z dS ) � ValuesBasezTSupplies support for :meth:`.ValuesBase.values` to INSERT and UPDATE constructs.Z values_baseFNc C s. t |�| _| �|�\| _| _|r*| �|� d S r )r r! r/ r. �_has_multi_parameters�_setup_prefixes)r$ r! �values�prefixesr r r �__init__� s � zValuesBase.__init__c O s | j durt�d��| jr(|r(t�d��|rLt|�dkrBt�d��|d }ni }| jdu rn| �|�\| _| _nx| jr�t| j�| _| �|�\}| _| js�t�d��| j� |� n8| j� � | _| �|�\}| _| jr�t�d��| j� |� |�r | jr�t�d��n | j� |� dS ) a& 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:`execute_multiple` - 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.ResultProxy.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 :class:`_expression.Update` construct supports a special form which is a list of 2-tuples, which when provided must be passed in conjunction with the :paramref:`_expression.update.preserve_parameter_order` parameter. This form causes the UPDATE statement to render the SET clauses using the order of parameters given to :meth:`_expression.Update.values`, rather than the ordering of columns given in the :class:`_schema.Table`. .. versionadded:: 1.0.10 - added support for parameter-ordered UPDATE statements via the :paramref:`_expression.update.preserve_parameter_order` flag. .. seealso:: :ref:`updates_order_parameters` - full example of the :paramref:`_expression.update.preserve_parameter_order` flag .. seealso:: :ref:`inserts_and_updates` - SQL Expression Language Tutorial :func:`_expression.insert` - produce an ``INSERT`` statement :func:`_expression.update` - produce an ``UPDATE`` statement Nz,This construct already inserts from a SELECTz3This construct already has multiple parameter sets.r zWOnly a single dictionary/tuple or list of dictionaries/tuples is accepted positionally.r& zDCan't mix single-values and multiple values formats in one statementz<Can't pass kwargs and multiple parameter sets simultaneously) �selectr r- rK �len� ArgumentErrorr. r/ r �extend�copy�update)r$ �args�kwargs�vr" r r r rM � sV � � � �� � � �zValuesBase.valuesc G s | j rt�d��|pd| _dS )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.ResultProxy.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. 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.ResultProxy.returned_defaults` will be ``None`` :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.ResultProxy.returned_defaults` z1RETURNING is already configured on this statementTN)r8 r r- r7 r: r r r �return_defaults� s E�zValuesBase.return_defaults)rC rD rE rF rG r, rK r) rP Z_post_values_clauserO r rM rY r r r r rJ � s <rJ c @ sD e Zd ZdZdZdZddd�Zdd � Zedd d ��Z e fd d �Z dS )�Insertz�Represent an INSERT construct. The :class:`_expression.Insert` object is created using the :func:`_expression.insert()` function. .. seealso:: :ref:`coretutorial_insert_expressions` �insertTNFc K sH t �| |||� || _d | _| _d| _|| _|| _| �|� || _ dS )a� Construct an :class:`_expression.Insert` object. Similar functionality is available via the :meth:`_expression.TableClause.insert` method on :class:`_schema.Table`. :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 `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:`~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:`coretutorial_insert_expressions` - SQL Expression Tutorial :ref:`inserts_and_updates` - SQL Expression Tutorial NF) rJ rO r4 rP � select_names�#include_insert_from_select_defaults�inliner8 �_validate_dialect_kwargsr7 ) r$ r! rM r^ r5 rN r< rY � dialect_kwr r r rO s ; zInsert.__init__c K s | j d ur| j fS dS d S �Nr )rP �r$ rW r r r � get_childrenD s zInsert.get_childrenc C sL | j rt�d��| �dd� |D ��\| _ | _|| _d| _|| _t|�| _ dS )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**. .. 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.ResultProxy.inserted_primary_key` accessor does not apply. z0This construct already inserts value expressionsc S s i | ]}t |�t� �qS r )r r )r �nr r r � <dictcomp>� r z&Insert.from_select.<locals>.<dictcomp>TN) r. r r- r/ rK r\ r^ r] r rP )r$ �namesrP Zinclude_defaultsr r r � from_selectJ s 2� � zInsert.from_selectc K s& | j �� | _ | jd ur"t| j�| _d S r )r. rT rP r �r$ �cloner2 r r r �_copy_internals� s zInsert._copy_internals)NFNNNF)T) rC rD rE rF rG r, rO rc r rg r rj r r r r rZ � s � D ?rZ c @ sJ e Zd ZdZdZddd�Zdd� Zefd d �Ze d d � �Z e d d� �Z dS )�Updatez�Represent an Update construct. The :class:`_expression.Update` object is created using the :func:`update()` function. rU NFc K sV | | _ t�| |||� || _|| _|dur6t|�| _nd| _|| _| �| � || _ dS )a; Construct an :class:`_expression.Update` object. E.g.:: from sqlalchemy import update stmt = update(users).where(users.c.id==5).\ values(name='user #5') Similar functionality is available via the :meth:`_expression.TableClause.update` method on :class:`_schema.Table`:: stmt = users.update().\ where(users.c.id==5).\ values(name='user #5') :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.ResultProxy.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` - full example of the :paramref:`_expression.update.preserve_parameter_order` flag 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).\ as_scalar() ) .. seealso:: :ref:`inserts_and_updates` - SQL Expression Language Tutorial N) r) rJ rO r4 r8 r � _whereclauser^ r_ r7 ) r$ r! � whereclauserM r^ r5 rN r< rY Zpreserve_parameter_orderr` r r r rO � s q zUpdate.__init__c K s | j d ur| j fS dS d S ra �rl rb r r r rc s zUpdate.get_childrenc K s$ || j fi |��| _ | j�� | _d S r )rl r. rT rh r r r rj s zUpdate._copy_internalsc C s, | j dur t| j t|��| _ n t|�| _ dS )a� Return a new update() construct with the given expression 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_1x_correlated_updates` :ref:`multi_table_updates` :ref:`multi_table_deletes` N�rl r r �r$ rm r r r �where$ s �z Update.wherec C sp g }t t�| j��}|d h}| jd urZt| j�D ]&}|�|j�sL|�|� |� |j� q2|� |dd � � |S )Nr& r ) r �sql_utilZtables_from_leftmostr! rl r � intersection� _cloned_set�appendrU rS )r$ �fromsZ all_tables�seen�itemr r r � _extra_fromsA s zUpdate._extra_froms)NNFNNNFF) rC rD rE rF rG rO rc r rj r rq rI ry r r r r rk � s" � } rk c @ sJ e Zd ZdZdZddd�Zdd� Zedd � �Ze d d � �Z e fd d �Z dS )�Deletez�Represent a DELETE construct. The :class:`_expression.Delete` object is created using the :func:`delete()` function. �deleteNc K sL || _ t|�| _|| _|r$| �|� |dur8t|�| _nd| _| �|� dS )a= Construct :class:`_expression.Delete` object. Similar functionality is available via the :meth:`_expression.TableClause.delete` method on :class:`_schema.Table`. :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 N)r4 r r! r8 rL r rl r_ )r$ r! rm r5 r< rN r` r r r rO ] s zDelete.__init__c K s | j d ur| j fS dS d S ra rn rb r r r rc � s zDelete.get_childrenc C s, | j dur t| j t|��| _ n t|�| _ dS )a� Add the given WHERE clause to a newly returned delete construct. 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_1x_correlated_updates` :ref:`multi_table_updates` :ref:`multi_table_deletes` Nro rp r r r rq � s �z Delete.wherec C sL g }| j h}| jd urHt| j�D ]&}|�|j�s:|�|� |�|j� q |S r )r! rl r rs rt ru rU )r$ rv rw rx r r r ry � s zDelete._extra_fromsc K s || j fi |��| _ d S r rn rh r r r rj � s zDelete._copy_internals)NNNN) rC rD rE rF rG rO rc r rq rI ry r rj r r r r rz R s � ) rz N)rF � r rr �baser r r r �elementsr r r r r r rA r r r r r r rJ rZ rk rz r r r r �<module> s: � 6 " B
| ver. 1.1 | |
.
| PHP 8.3.30 | Ð“ÐµÐ½ÐµÑ€Ð°Ñ†Ð¸Ñ Ñтраницы: 0 |
proxy
|
phpinfo
|
ÐаÑтройка