+h}2dZddlmZddlZddlZddlZddlmZddlm Z ddlm Z ddlm Z dd l m Z dd l mZdd l mZdd l mZdd l mZddlmZddlmZddlmZddlmZddlmZddlmZddlmZddlmZddlmZddlmZddlmZddlmZddlm Z ddlm!Z!ddl"m#Z#ddl"m$Z$ddl"m%Z%dd l"m&Z&dd!l"m'Z'dd"l"m(Z(dd#l"m)Z)d$Z*d%Z+ejXGd&d'eZ-d(Z.Gd)d*e/Z0Gd+d,e/Z1y)-a Heuristics related to join conditions as used in :func:`_orm.relationship`. Provides the :class:`.JoinCondition` object, which encapsulates SQL annotation and aliasing behavior focused on the `primaryjoin` and `secondaryjoin` aspects of :func:`_orm.relationship`. )absolute_importN) attributes)_is_mapped_class) PASSIVE_MERGE) state_str) MANYTOMANY) MANYTOONE) ONETOMANY)PropComparator)StrategizedProperty) _orm_annotate)_orm_deannotate)CascadeOptions)exc)log)schema)sql)util)inspect) coercions) expression) operators)roles)visitors)_deep_deannotate)_shallow_annotate)adapt_criterion_to_null) ClauseAdapter)join_condition)selectables_overlapvisit_binary_productcbttjtj|ddiS)aAnnotate a portion of a primaryjoin expression with a 'remote' annotation. See the section :ref:`relationship_custom_foreign` for a description of use. .. seealso:: :ref:`relationship_custom_foreign` :func:`.foreign` remoteT_annotate_columnsrexpectrColumnArgumentRoleexprs O/var/www/html/venv/lib/python3.12/site-packages/sqlalchemy/orm/relationships.pyr&r&6s. 11488T:J cbttjtj|ddiS)aAnnotate a portion of a primaryjoin expression with a 'foreign' annotation. See the section :ref:`relationship_custom_foreign` for a description of use. .. seealso:: :ref:`relationship_custom_foreign` :func:`.remote` foreignTr'r+s r-r0r0Is. 11489d:K r.c"ZeZdZdZdZdZdZedddddZdZ ddddddddddddddeded ded dddddded ed ddddddddf"fd Z dZ dZ Gdde Zd5dZ d6dZdZd7dZdZdZej,fdZ d8dZedZedZdZej>ej@ddZ!ej>dZ"fd Z#d!Z$d"Z%d#Z&ed$Z'ed%Z(ej>ej@d&d'Z)ej@dd(Z*ed)Z+e+jXd*Z+d+Z-d,Z.d-Z/d.Z0d/Z1ej@d0d1Z2ej>d2Z3ej>d3Z4 d9d4Z5xZ6S):RelationshipPropertyzDescribes an object property that holds a single item or list of items that correspond to a related database table. Public constructor is the :func:`_orm.relationship` function. .. seealso:: :ref:`relationship_config_toplevel` relationshipTFpassive_deletespassive_updatesenable_typechecksactive_historycascade_backrefsNselectr5r6r7r8r9c$\tt| ||_||_||_||_||_| |_d|_ | |_ | r|j|||||| r|"rtjd|"|_||_||_||_||_||_||_||_||_||_||_||_||_||_||_|#|_||_|!rt?j@d|!|_!||_"||_#||_$|xstjJ|_&|jM|d|_'t?jP|| | |_)d|jff|_*tW|_,| r%tWt[j\d| |_/nd|_/| dur| |_0n|jrd |_0nd |_0||_1| |_2|jdr|rtjd d|_3y||_3y) a(Provide a relationship between two mapped classes. This corresponds to a parent-child or associative table relationship. The constructed class is an instance of :class:`.RelationshipProperty`. A typical :func:`_orm.relationship`, used in a classical mapping:: mapper(Parent, properties={ 'children': relationship(Child) }) Some arguments accepted by :func:`_orm.relationship` optionally accept a callable function, which when called produces the desired value. The callable is invoked by the parent :class:`_orm.Mapper` at "mapper initialization" time, which happens only when mappers are first used, and is assumed to be after all mappings have been constructed. This can be used to resolve order-of-declaration and other dependency issues, such as if ``Child`` is declared below ``Parent`` in the same file:: mapper(Parent, properties={ "children":relationship(lambda: Child, order_by=lambda: Child.id) }) When using the :ref:`declarative_toplevel` extension, the Declarative initializer allows string arguments to be passed to :func:`_orm.relationship`. These string arguments are converted into callables that evaluate the string as Python code, using the Declarative class-registry as a namespace. This allows the lookup of related classes to be automatic via their string name, and removes the need for related classes to be imported into the local module space before the dependent classes have been declared. It is still required that the modules in which these related classes appear are imported anywhere in the application at some point before the related mappings are actually used, else a lookup error will be raised when the :func:`_orm.relationship` attempts to resolve the string reference to the related class. An example of a string- resolved class is as follows:: from sqlalchemy.ext.declarative import declarative_base Base = declarative_base() class Parent(Base): __tablename__ = 'parent' id = Column(Integer, primary_key=True) children = relationship("Child", order_by="Child.id") .. seealso:: :ref:`relationship_config_toplevel` - Full introductory and reference documentation for :func:`_orm.relationship`. :ref:`tutorial_orm_related_objects` - ORM tutorial introduction. :param argument: A mapped class, or actual :class:`_orm.Mapper` instance, representing the target of the relationship. :paramref:`_orm.relationship.argument` may also be passed as a callable function which is evaluated at mapper initialization time, and may be passed as a string name when using Declarative. .. warning:: Prior to SQLAlchemy 1.3.16, this value is interpreted using Python's ``eval()`` function. **DO NOT PASS UNTRUSTED INPUT TO THIS STRING**. See :ref:`declarative_relationship_eval` for details on declarative evaluation of :func:`_orm.relationship` arguments. .. versionchanged 1.3.16:: The string evaluation of the main "argument" no longer accepts an open ended Python expression, instead only accepting a string class name or dotted package-qualified name. .. seealso:: :ref:`declarative_configuring_relationships` - further detail on relationship configuration when using Declarative. :param secondary: For a many-to-many relationship, specifies the intermediary table, and is typically an instance of :class:`_schema.Table`. In less common circumstances, the argument may also be specified as an :class:`_expression.Alias` construct, or even a :class:`_expression.Join` construct. :paramref:`_orm.relationship.secondary` may also be passed as a callable function which is evaluated at mapper initialization time. When using Declarative, it may also be a string argument noting the name of a :class:`_schema.Table` that is present in the :class:`_schema.MetaData` collection associated with the parent-mapped :class:`_schema.Table`. .. warning:: When passed as a Python-evaluable string, the argument is interpreted using Python's ``eval()`` function. **DO NOT PASS UNTRUSTED INPUT TO THIS STRING**. See :ref:`declarative_relationship_eval` for details on declarative evaluation of :func:`_orm.relationship` arguments. The :paramref:`_orm.relationship.secondary` keyword argument is typically applied in the case where the intermediary :class:`_schema.Table` is not otherwise expressed in any direct class mapping. If the "secondary" table is also explicitly mapped elsewhere (e.g. as in :ref:`association_pattern`), one should consider applying the :paramref:`_orm.relationship.viewonly` flag so that this :func:`_orm.relationship` is not used for persistence operations which may conflict with those of the association object pattern. .. seealso:: :ref:`relationships_many_to_many` - Reference example of "many to many". :ref:`self_referential_many_to_many` - Specifics on using many-to-many in a self-referential case. :ref:`declarative_many_to_many` - Additional options when using Declarative. :ref:`association_pattern` - an alternative to :paramref:`_orm.relationship.secondary` when composing association table relationships, allowing additional attributes to be specified on the association table. :ref:`composite_secondary_join` - a lesser-used pattern which in some cases can enable complex :func:`_orm.relationship` SQL conditions to be used. .. versionadded:: 0.9.2 :paramref:`_orm.relationship.secondary` works more effectively when referring to a :class:`_expression.Join` instance. :param active_history=False: When ``True``, indicates that the "previous" value for a many-to-one reference should be loaded when replaced, if not already loaded. Normally, history tracking logic for simple many-to-ones only needs to be aware of the "new" value in order to perform a flush. This flag is available for applications that make use of :func:`.attributes.get_history` which also need to know the "previous" value of the attribute. :param backref: A reference to a string relationship name, or a :func:`_orm.backref` construct, which will be used to automatically generate a new :func:`_orm.relationship` on the related class, which then refers to this one using a bi-directional :paramref:`_orm.relationship.back_populates` configuration. In modern Python, explicit use of :func:`_orm.relationship` with :paramref:`_orm.relationship.back_populates` should be preferred, as it is more robust in terms of mapper configuration as well as more conceptually straightforward. It also integrates with new :pep:`484` typing features introduced in SQLAlchemy 2.0 which is not possible with dynamically generated attributes. .. seealso:: :ref:`relationships_backref` - notes on using :paramref:`_orm.relationship.backref` :ref:`tutorial_orm_related_objects` - in the :ref:`unified_tutorial`, presents an overview of bi-directional relationship configuration and behaviors using :paramref:`_orm.relationship.back_populates` :func:`.backref` - allows control over :func:`_orm.relationship` configuration when using :paramref:`_orm.relationship.backref`. :param back_populates: Indicates the name of a :func:`_orm.relationship` on the related class that will be synchronized with this one. It is usually expected that the :func:`_orm.relationship` on the related class also refer to this one. This allows objects on both sides of each :func:`_orm.relationship` to synchronize in-Python state changes and also provides directives to the :term:`unit of work` flush process how changes along these relationships should be persisted. .. seealso:: :ref:`tutorial_orm_related_objects` - in the :ref:`unified_tutorial`, presents an overview of bi-directional relationship configuration and behaviors. :ref:`relationship_patterns` - includes many examples of :paramref:`_orm.relationship.back_populates`. :param overlaps: A string name or comma-delimited set of names of other relationships on either this mapper, a descendant mapper, or a target mapper with which this relationship may write to the same foreign keys upon persistence. The only effect this has is to eliminate the warning that this relationship will conflict with another upon persistence. This is used for such relationships that are truly capable of conflicting with each other on write, but the application will ensure that no such conflicts occur. .. versionadded:: 1.4 .. seealso:: :ref:`error_qzyx` - usage example :param bake_queries=True: Legacy parameter, not used. .. versionchanged:: 1.4.23 the "lambda caching" system is no longer used by loader strategies and the ``bake_queries`` parameter has no effect. :param cascade: A comma-separated list of cascade rules which determines how Session operations should be "cascaded" from parent to child. This defaults to ``False``, which means the default cascade should be used - this default cascade is ``"save-update, merge"``. The available cascades are ``save-update``, ``merge``, ``expunge``, ``delete``, ``delete-orphan``, and ``refresh-expire``. An additional option, ``all`` indicates shorthand for ``"save-update, merge, refresh-expire, expunge, delete"``, and is often used as in ``"all, delete-orphan"`` to indicate that related objects should follow along with the parent object in all cases, and be deleted when de-associated. .. seealso:: :ref:`unitofwork_cascades` - Full detail on each of the available cascade options. :param cascade_backrefs=True: A boolean value indicating if the ``save-update`` cascade should operate along an assignment event intercepted by a backref. When set to ``False``, the attribute managed by this relationship will not cascade an incoming transient object into the session of a persistent parent, if the event is received via backref. .. deprecated:: 1.4 The :paramref:`_orm.relationship.cascade_backrefs` flag will default to False in all cases in SQLAlchemy 2.0. .. seealso:: :ref:`backref_cascade` - Full discussion and examples on how the :paramref:`_orm.relationship.cascade_backrefs` option is used. :param collection_class: A class or callable that returns a new list-holding object. will be used in place of a plain list for storing elements. .. seealso:: :ref:`custom_collections` - Introductory documentation and examples. :param comparator_factory: A class which extends :class:`.RelationshipProperty.Comparator` which provides custom SQL clause generation for comparison operations. .. seealso:: :class:`.PropComparator` - some detail on redefining comparators at this level. :ref:`custom_comparators` - Brief intro to this feature. :param distinct_target_key=None: Indicate if a "subquery" eager load should apply the DISTINCT keyword to the innermost SELECT statement. When left as ``None``, the DISTINCT keyword will be applied in those cases when the target columns do not comprise the full primary key of the target table. When set to ``True``, the DISTINCT keyword is applied to the innermost SELECT unconditionally. It may be desirable to set this flag to False when the DISTINCT is reducing performance of the innermost subquery beyond that of what duplicate innermost rows may be causing. .. versionchanged:: 0.9.0 - :paramref:`_orm.relationship.distinct_target_key` now defaults to ``None``, so that the feature enables itself automatically for those cases where the innermost query targets a non-unique key. .. seealso:: :ref:`loading_toplevel` - includes an introduction to subquery eager loading. :param doc: Docstring which will be applied to the resulting descriptor. :param foreign_keys: A list of columns which are to be used as "foreign key" columns, or columns which refer to the value in a remote column, within the context of this :func:`_orm.relationship` object's :paramref:`_orm.relationship.primaryjoin` condition. That is, if the :paramref:`_orm.relationship.primaryjoin` condition of this :func:`_orm.relationship` is ``a.id == b.a_id``, and the values in ``b.a_id`` are required to be present in ``a.id``, then the "foreign key" column of this :func:`_orm.relationship` is ``b.a_id``. In normal cases, the :paramref:`_orm.relationship.foreign_keys` parameter is **not required.** :func:`_orm.relationship` will automatically determine which columns in the :paramref:`_orm.relationship.primaryjoin` condition are to be considered "foreign key" columns based on those :class:`_schema.Column` objects that specify :class:`_schema.ForeignKey`, or are otherwise listed as referencing columns in a :class:`_schema.ForeignKeyConstraint` construct. :paramref:`_orm.relationship.foreign_keys` is only needed when: 1. There is more than one way to construct a join from the local table to the remote table, as there are multiple foreign key references present. Setting ``foreign_keys`` will limit the :func:`_orm.relationship` to consider just those columns specified here as "foreign". 2. The :class:`_schema.Table` being mapped does not actually have :class:`_schema.ForeignKey` or :class:`_schema.ForeignKeyConstraint` constructs present, often because the table was reflected from a database that does not support foreign key reflection (MySQL MyISAM). 3. The :paramref:`_orm.relationship.primaryjoin` argument is used to construct a non-standard join condition, which makes use of columns or expressions that do not normally refer to their "parent" column, such as a join condition expressed by a complex comparison using a SQL function. The :func:`_orm.relationship` construct will raise informative error messages that suggest the use of the :paramref:`_orm.relationship.foreign_keys` parameter when presented with an ambiguous condition. In typical cases, if :func:`_orm.relationship` doesn't raise any exceptions, the :paramref:`_orm.relationship.foreign_keys` parameter is usually not needed. :paramref:`_orm.relationship.foreign_keys` may also be passed as a callable function which is evaluated at mapper initialization time, and may be passed as a Python-evaluable string when using Declarative. .. warning:: When passed as a Python-evaluable string, the argument is interpreted using Python's ``eval()`` function. **DO NOT PASS UNTRUSTED INPUT TO THIS STRING**. See :ref:`declarative_relationship_eval` for details on declarative evaluation of :func:`_orm.relationship` arguments. .. seealso:: :ref:`relationship_foreign_keys` :ref:`relationship_custom_foreign` :func:`.foreign` - allows direct annotation of the "foreign" columns within a :paramref:`_orm.relationship.primaryjoin` condition. :param info: Optional data dictionary which will be populated into the :attr:`.MapperProperty.info` attribute of this object. :param innerjoin=False: When ``True``, joined eager loads will use an inner join to join against related tables instead of an outer join. The purpose of this option is generally one of performance, as inner joins generally perform better than outer joins. This flag can be set to ``True`` when the relationship references an object via many-to-one using local foreign keys that are not nullable, or when the reference is one-to-one or a collection that is guaranteed to have one or at least one entry. The option supports the same "nested" and "unnested" options as that of :paramref:`_orm.joinedload.innerjoin`. See that flag for details on nested / unnested behaviors. .. seealso:: :paramref:`_orm.joinedload.innerjoin` - the option as specified by loader option, including detail on nesting behavior. :ref:`what_kind_of_loading` - Discussion of some details of various loader options. :param join_depth: When non-``None``, an integer value indicating how many levels deep "eager" loaders should join on a self-referring or cyclical relationship. The number counts how many times the same Mapper shall be present in the loading condition along a particular join branch. When left at its default of ``None``, eager loaders will stop chaining when they encounter a the same target mapper which is already higher up in the chain. This option applies both to joined- and subquery- eager loaders. .. seealso:: :ref:`self_referential_eager_loading` - Introductory documentation and examples. :param lazy='select': specifies How the related items should be loaded. Default value is ``select``. Values include: * ``select`` - items should be loaded lazily when the property is first accessed, using a separate SELECT statement, or identity map fetch for simple many-to-one references. * ``immediate`` - items should be loaded as the parents are loaded, using a separate SELECT statement, or identity map fetch for simple many-to-one references. * ``joined`` - items should be loaded "eagerly" in the same query as that of the parent, using a JOIN or LEFT OUTER JOIN. Whether the join is "outer" or not is determined by the :paramref:`_orm.relationship.innerjoin` parameter. * ``subquery`` - items should be loaded "eagerly" as the parents are loaded, using one additional SQL statement, which issues a JOIN to a subquery of the original statement, for each collection requested. * ``selectin`` - items should be loaded "eagerly" as the parents are loaded, using one or more additional SQL statements, which issues a JOIN to the immediate parent object, specifying primary key identifiers using an IN clause. .. versionadded:: 1.2 * ``noload`` - no loading should occur at any time. This is to support "write-only" attributes, or attributes which are populated in some manner specific to the application. * ``raise`` - lazy loading is disallowed; accessing the attribute, if its value were not already loaded via eager loading, will raise an :exc:`~sqlalchemy.exc.InvalidRequestError`. This strategy can be used when objects are to be detached from their attached :class:`.Session` after they are loaded. .. versionadded:: 1.1 * ``raise_on_sql`` - lazy loading that emits SQL is disallowed; accessing the attribute, if its value were not already loaded via eager loading, will raise an :exc:`~sqlalchemy.exc.InvalidRequestError`, **if the lazy load needs to emit SQL**. If the lazy load can pull the related value from the identity map or determine that it should be None, the value is loaded. This strategy can be used when objects will remain associated with the attached :class:`.Session`, however additional SELECT statements should be blocked. .. versionadded:: 1.1 * ``dynamic`` - the attribute will return a pre-configured :class:`_query.Query` object for all read operations, onto which further filtering operations can be applied before iterating the results. See the section :ref:`dynamic_relationship` for more details. * True - a synonym for 'select' * False - a synonym for 'joined' * None - a synonym for 'noload' .. seealso:: :doc:`/orm/loading_relationships` - Full documentation on relationship loader configuration. :ref:`dynamic_relationship` - detail on the ``dynamic`` option. :ref:`collections_noload_raiseload` - notes on "noload" and "raise" :param load_on_pending=False: Indicates loading behavior for transient or pending parent objects. When set to ``True``, causes the lazy-loader to issue a query for a parent object that is not persistent, meaning it has never been flushed. This may take effect for a pending object when autoflush is disabled, or for a transient object that has been "attached" to a :class:`.Session` but is not part of its pending collection. The :paramref:`_orm.relationship.load_on_pending` flag does not improve behavior when the ORM is used normally - object references should be constructed at the object level, not at the foreign key level, so that they are present in an ordinary way before a flush proceeds. This flag is not not intended for general use. .. seealso:: :meth:`.Session.enable_relationship_loading` - this method establishes "load on pending" behavior for the whole object, and also allows loading on objects that remain transient or detached. :param order_by: Indicates the ordering that should be applied when loading these items. :paramref:`_orm.relationship.order_by` is expected to refer to one of the :class:`_schema.Column` objects to which the target class is mapped, or the attribute itself bound to the target class which refers to the column. :paramref:`_orm.relationship.order_by` may also be passed as a callable function which is evaluated at mapper initialization time, and may be passed as a Python-evaluable string when using Declarative. .. warning:: When passed as a Python-evaluable string, the argument is interpreted using Python's ``eval()`` function. **DO NOT PASS UNTRUSTED INPUT TO THIS STRING**. See :ref:`declarative_relationship_eval` for details on declarative evaluation of :func:`_orm.relationship` arguments. :param passive_deletes=False: Indicates loading behavior during delete operations. A value of True indicates that unloaded child items should not be loaded during a delete operation on the parent. Normally, when a parent item is deleted, all child items are loaded so that they can either be marked as deleted, or have their foreign key to the parent set to NULL. Marking this flag as True usually implies an ON DELETE rule is in place which will handle updating/deleting child rows on the database side. Additionally, setting the flag to the string value 'all' will disable the "nulling out" of the child foreign keys, when the parent object is deleted and there is no delete or delete-orphan cascade enabled. This is typically used when a triggering or error raise scenario is in place on the database side. Note that the foreign key attributes on in-session child objects will not be changed after a flush occurs so this is a very special use-case setting. Additionally, the "nulling out" will still occur if the child object is de-associated with the parent. .. seealso:: :ref:`passive_deletes` - Introductory documentation and examples. :param passive_updates=True: Indicates the persistence behavior to take when a referenced primary key value changes in place, indicating that the referencing foreign key columns will also need their value changed. When True, it is assumed that ``ON UPDATE CASCADE`` is configured on the foreign key in the database, and that the database will handle propagation of an UPDATE from a source column to dependent rows. When False, the SQLAlchemy :func:`_orm.relationship` construct will attempt to emit its own UPDATE statements to modify related targets. However note that SQLAlchemy **cannot** emit an UPDATE for more than one level of cascade. Also, setting this flag to False is not compatible in the case where the database is in fact enforcing referential integrity, unless those constraints are explicitly "deferred", if the target backend supports it. It is highly advised that an application which is employing mutable primary keys keeps ``passive_updates`` set to True, and instead uses the referential integrity features of the database itself in order to handle the change efficiently and fully. .. seealso:: :ref:`passive_updates` - Introductory documentation and examples. :paramref:`.mapper.passive_updates` - a similar flag which takes effect for joined-table inheritance mappings. :param post_update: This indicates that the relationship should be handled by a second UPDATE statement after an INSERT or before a DELETE. This flag is used to handle saving bi-directional dependencies between two individual rows (i.e. each row references the other), where it would otherwise be impossible to INSERT or DELETE both rows fully since one row exists before the other. Use this flag when a particular mapping arrangement will incur two rows that are dependent on each other, such as a table that has a one-to-many relationship to a set of child rows, and also has a column that references a single child row within that list (i.e. both tables contain a foreign key to each other). If a flush operation returns an error that a "cyclical dependency" was detected, this is a cue that you might want to use :paramref:`_orm.relationship.post_update` to "break" the cycle. .. seealso:: :ref:`post_update` - Introductory documentation and examples. :param primaryjoin: A SQL expression that will be used as the primary join of the child object against the parent object, or in a many-to-many relationship the join of the parent object to the association table. By default, this value is computed based on the foreign key relationships of the parent and child tables (or association table). :paramref:`_orm.relationship.primaryjoin` may also be passed as a callable function which is evaluated at mapper initialization time, and may be passed as a Python-evaluable string when using Declarative. .. warning:: When passed as a Python-evaluable string, the argument is interpreted using Python's ``eval()`` function. **DO NOT PASS UNTRUSTED INPUT TO THIS STRING**. See :ref:`declarative_relationship_eval` for details on declarative evaluation of :func:`_orm.relationship` arguments. .. seealso:: :ref:`relationship_primaryjoin` :param remote_side: Used for self-referential relationships, indicates the column or list of columns that form the "remote side" of the relationship. :paramref:`_orm.relationship.remote_side` may also be passed as a callable function which is evaluated at mapper initialization time, and may be passed as a Python-evaluable string when using Declarative. .. warning:: When passed as a Python-evaluable string, the argument is interpreted using Python's ``eval()`` function. **DO NOT PASS UNTRUSTED INPUT TO THIS STRING**. See :ref:`declarative_relationship_eval` for details on declarative evaluation of :func:`_orm.relationship` arguments. .. seealso:: :ref:`self_referential` - in-depth explanation of how :paramref:`_orm.relationship.remote_side` is used to configure self-referential relationships. :func:`.remote` - an annotation function that accomplishes the same purpose as :paramref:`_orm.relationship.remote_side`, typically when a custom :paramref:`_orm.relationship.primaryjoin` condition is used. :param query_class: A :class:`_query.Query` subclass that will be used internally by the ``AppenderQuery`` returned by a "dynamic" relationship, that is, a relationship that specifies ``lazy="dynamic"`` or was otherwise constructed using the :func:`_orm.dynamic_loader` function. .. seealso:: :ref:`dynamic_relationship` - Introduction to "dynamic" relationship loaders. :param secondaryjoin: A SQL expression that will be used as the join of an association table to the child object. By default, this value is computed based on the foreign key relationships of the association and child tables. :paramref:`_orm.relationship.secondaryjoin` may also be passed as a callable function which is evaluated at mapper initialization time, and may be passed as a Python-evaluable string when using Declarative. .. warning:: When passed as a Python-evaluable string, the argument is interpreted using Python's ``eval()`` function. **DO NOT PASS UNTRUSTED INPUT TO THIS STRING**. See :ref:`declarative_relationship_eval` for details on declarative evaluation of :func:`_orm.relationship` arguments. .. seealso:: :ref:`relationship_primaryjoin` :param single_parent: When True, installs a validator which will prevent objects from being associated with more than one parent at a time. This is used for many-to-one or many-to-many relationships that should be treated either as one-to-one or one-to-many. Its usage is optional, except for :func:`_orm.relationship` constructs which are many-to-one or many-to-many and also specify the ``delete-orphan`` cascade option. The :func:`_orm.relationship` construct itself will raise an error instructing when this option is required. .. seealso:: :ref:`unitofwork_cascades` - includes detail on when the :paramref:`_orm.relationship.single_parent` flag may be appropriate. :param uselist: A boolean that indicates if this property should be loaded as a list or a scalar. In most cases, this value is determined automatically by :func:`_orm.relationship` at mapper configuration time, based on the type and direction of the relationship - one to many forms a list, many to one forms a scalar, many to many is a list. If a scalar is desired where normally a list would be present, such as a bi-directional one-to-one relationship, set :paramref:`_orm.relationship.uselist` to False. The :paramref:`_orm.relationship.uselist` flag is also available on an existing :func:`_orm.relationship` construct as a read-only attribute, which can be used to determine if this :func:`_orm.relationship` deals with collections or scalar attributes:: >>> User.addresses.property.uselist True .. seealso:: :ref:`relationships_one_to_one` - Introduction to the "one to one" relationship pattern, which is typically when the :paramref:`_orm.relationship.uselist` flag is needed. :param viewonly=False: When set to ``True``, the relationship is used only for loading objects, and not for any persistence operation. A :func:`_orm.relationship` which specifies :paramref:`_orm.relationship.viewonly` can work with a wider range of SQL operations within the :paramref:`_orm.relationship.primaryjoin` condition, including operations that feature the use of a variety of comparison operators as well as SQL functions such as :func:`_expression.cast`. The :paramref:`_orm.relationship.viewonly` flag is also of general use when defining any kind of :func:`_orm.relationship` that doesn't represent the full set of related objects, to prevent modifications of the collection from resulting in persistence operations. When using the :paramref:`_orm.relationship.viewonly` flag in conjunction with backrefs, the originating relationship for a particular state change will not produce state changes within the viewonly relationship. This is the behavior implied by :paramref:`_orm.relationship.sync_backref` being set to False. .. versionchanged:: 1.3.17 - the :paramref:`_orm.relationship.sync_backref` flag is set to False when using viewonly in conjunction with backrefs. .. seealso:: :paramref:`_orm.relationship.sync_backref` :param sync_backref: A boolean that enables the events used to synchronize the in-Python attributes when this relationship is target of either :paramref:`_orm.relationship.backref` or :paramref:`_orm.relationship.back_populates`. Defaults to ``None``, which indicates that an automatic value should be selected based on the value of the :paramref:`_orm.relationship.viewonly` flag. When left at its default, changes in state will be back-populated only if neither sides of a relationship is viewonly. .. versionadded:: 1.3.17 .. versionchanged:: 1.4 - A relationship that specifies :paramref:`_orm.relationship.viewonly` automatically implies that :paramref:`_orm.relationship.sync_backref` is ``False``. .. seealso:: :paramref:`_orm.relationship.viewonly` :param omit_join: Allows manual control over the "selectin" automatic join optimization. Set to ``False`` to disable the "omit join" feature added in SQLAlchemy 1.3; or leave as ``None`` to leave automatic optimization in place. .. note:: This flag may only be set to ``False``. It is not necessary to set it to ``True`` as the "omit_join" optimization is automatically detected; if it is not detected, then the optimization is not supported. .. versionchanged:: 1.3.11 setting ``omit_join`` to True will now emit a warning as this was not the intended use of this flag. .. versionadded:: 1.3 Nr4z-sync_backref and viewonly cannot both be Truezsetting omit_join to True is not supported; selectin loading of this relationship may not work correctly if this flag is set explicitly. omit_join optimization is automatically detected for conditions under which it is supported.lazyz\s*,\s*Fmergezsave-update, mergezCbackref and back_populates keyword arguments are mutually exclusive)4superr2__init__uselistargument secondary primaryjoin secondaryjoin post_update directionviewonly _warn_for_persistence_only_flagssa_exc ArgumentError sync_backrefr< single_parent_user_defined_foreign_keyscollection_classr5r9r6 remote_sider7 query_class innerjoindistinct_target_keydocr8_legacy_inactive_history_style join_depthrwarn omit_joinlocal_remote_pairs bake_queriesload_on_pending Comparatorcomparator_factory comparatorset_creation_orderinfo strategy_keyset_reverse_propertyresplit _overlapscascadeorder_byback_populatesbackref)%selfrBrCrDrE foreign_keysrArhrjrioverlapsrFrgrHr<rOr5r6rPr7rVr]rMrRrSrTr8r9r[rZ_local_remote_pairsrQr`rXrLrU __class__s% r-r@zRelationshipProperty.__init__ys:p "D24   "&*&    1 1 / /"3-!1 2   &&? ) **6' 0. 0.&!2&"#6 ,.L+$  II #"5(.  A"6"A"A 11$= %  DI$dii02!$  *h!?@DNDN % "DL ]]"DL/DL  ,   **- DL"DLr.c |jD]1\}}||j|k7stjd|d3y)NzSetting z on relationship() while also setting viewonly=True does not make sense, as a viewonly=True relationship does not perform persistence operations. This configuration may raise an error in a future release.)items_persistence_onlyrrW)rkkwkvs r-rIz5RelationshipProperty._warn_for_persistence_only_flags,sFHHJ DAqD**1-- /0 2 r.ctj|j|j|j ||||j y)N)r^ parententityrT)rregister_descriptorclass_keyr]rTrkmappers r-instrument_classz%RelationshipProperty.instrument_class>s8&& MM HH..tV<  r.ceZdZdZdZdZ ddZdZejdZ ejdZ ejdZ d Z d Zd Zd Zd ZdZdZddZddZddZdZdZdZejdZy)RelationshipProperty.ComparatoraProduce boolean, comparison, and other operators for :class:`.RelationshipProperty` attributes. See the documentation for :class:`.PropComparator` for a brief overview of ORM level operator definition. .. seealso:: :class:`.PropComparator` :class:`.ColumnProperty.Comparator` :class:`.ColumnOperators` :ref:`types_operators` :attr:`.TypeEngine.comparator_factory` Nr=cN||_||_||_|r||_||_y)zConstruction of :class:`.RelationshipProperty.Comparator` is internal to the ORM's attribute mechanics. N)prop _parententity_adapt_to_entity_of_type_extra_criteria)rkr parentmapperadapt_to_entityof_typeextra_criterias r-r@z(RelationshipProperty.Comparator.__init___s-DI!-D $3D ! ' #1D r.ch|j|j|j||jS)N)rr)ropropertyrr)rkrs r-rz/RelationshipProperty.Comparator.adapt_to_entityrs2>> "" / " r.cp|jt|jS|jjS)a+The target entity referred to by this :class:`.RelationshipProperty.Comparator`. This is either a :class:`_orm.Mapper` or :class:`.AliasedInsp` object. This is the "target" or "remote" side of the :func:`_orm.relationship`. )rrrentityrks r-rz&RelationshipProperty.Comparator.entityzs-}}(t}}--}}+++r.c.|jjS)zThe target :class:`_orm.Mapper` referred to by this :class:`.RelationshipProperty.Comparator`. This is the "target" or "remote" side of the :func:`_orm.relationship`. )rr|rs r-r|z&RelationshipProperty.Comparator.mappers=='' 'r.c.|jjSN)rparentrs r-rz-RelationshipProperty.Comparator._parententitys=='' 'r.c|jr|jjS|jjjSr)r selectablerr_with_polymorphic_selectablers r-_source_selectablez2RelationshipProperty.Comparator._source_selectables3$$,,777}}++HHHr.c|j}|jrt|j}nd}|jj |d|d|j \}}}}}}|||zS|S)NT)source_selectablesource_polymorphicof_type_entityalias_secondaryr)rrrr _create_joinsr) rk adapt_fromrpjsjsourcedestrCtarget_adapters r-__clause_element__z2RelationshipProperty.Comparator.__clause_element__s002J}}!(!7!% ++",#'- $#33 , ~Bw r.ctj|j|j|j||j S)zRedefine this object in terms of a polymorphic subclass. See :meth:`.PropComparator.of_type` for an example. rrr)r2r\rrrr)rkclss r-rz'RelationshipProperty.Comparator.of_typesA(22 "" $ 5 5#33 3 r.ctj|j|j|j|j |j |zS)zAdd AND criteria. See :meth:`.PropComparator.and_` for an example. .. versionadded:: 1.4 r)r2r\rrrrrrkothers r-and_z$RelationshipProperty.Comparator.and_sJ(22 "" $ 5 5 #33e; 3 r.ctd)zProduce an IN clause - this is not implemented for :func:`_orm.relationship`-based attributes at this time. zvin_() not yet supported for relationships. For a simple many-to-one, use in_() against the set of foreign key values.)NotImplementedErrorrs r-in_z#RelationshipProperty.Comparator.in_s &1 r.ct|tjtjfrc|j j ttfvr|jSt|j jd|jS|j jrtjdt|j j||jS)aImplement the ``==`` operator. In a many-to-one context, such as:: MyClass.some_prop == this will typically produce a clause such as:: mytable.related_id == Where ```` is the primary key of the given object. The ``==`` operator provides partial functionality for non- many-to-one comparisons: * Comparisons against collections are not supported. Use :meth:`~.RelationshipProperty.Comparator.contains`. * Compared to a scalar one-to-many, will produce a clause that compares the target columns in the parent to the given target. * Compared to a scalar many-to-many, an alias of the association table will be rendered as well, forming a natural join that is part of the main body of the query. This will not work for queries that go beyond simple AND conjunctions of comparisons, such as those which use OR. Use explicit joins, outerjoins, or :meth:`~.RelationshipProperty.Comparator.has` for more comprehensive non-many-to-one scalar membership tests. * Comparisons against ``None`` given in a one-to-many or many-to-many context produce a NOT EXISTS clause. N adapt_source]Can't compare a collection to an object or collection; use contains() to test for membership.) isinstancerNoneTyperNullrrGr r _criterion_existsr_optimized_compareadapterrArJInvalidRequestErrorrs r-__eq__z&RelationshipProperty.Comparator.__eq__sJ%$--!AB==**y*.EE 22444( 88 t||9 &&00= %MM44DLL5r.c 8t|ddrzt|j}|j|j|j }}}|j jr|s|j}|j}||||z}n|}nd}d}|jr|j}nd}|j j||\} } } } } }|D]<}t|j jj|||k(}||}8||z}>| t| | z}n!t| |j j}||r|s|j!|}||j#ddi}|t$j&j)|z}| Ft%j*dj-|j/| | j1| | }|St%j*dj-|j/| j1| }|S)NrF)dest_selectabler)excludeno_replacement_traverseTr)getattrrrr|ris_aliased_classr_is_self_referential_anonymous_fromclause_single_table_criterionrrrryrrPtraverse _annotaterTrue__ifnoneexistswhere select_fromcorrelate_except)rk criterionkwargsr` target_mapper to_selectabler single_critrrrrrrCrrtcritjexs r-rz1RelationshipProperty.Comparator._criterion_exists$s'tZ.t}}-KKOO))/?} ==55>N$1$G$G$IM+CC * ,$/)$; $/ #( $ ||$($;$;$=!$(! ++ -"3,   1t}}33::A>&)K$ $I )D 0I  1~!"%*!"dmm.G.GH%"(+33I> $%//.5 syy((33D$JJqMU4[ [y1%%dI6 I JJqMU4[ [&%%d+  Ir.c ~|jjstjd|j|fi|S)asProduce an expression that tests a collection against particular criterion, using EXISTS. An expression like:: session.query(MyClass).filter( MyClass.somereference.any(SomeRelated.x==2) ) Will produce a query like:: SELECT * FROM my_table WHERE EXISTS (SELECT 1 FROM related WHERE related.my_id=my_table.id AND related.x=2) Because :meth:`~.RelationshipProperty.Comparator.any` uses a correlated subquery, its performance is not nearly as good when compared against large target tables as that of using a join. :meth:`~.RelationshipProperty.Comparator.any` is particularly useful for testing for empty collections:: session.query(MyClass).filter( ~MyClass.somereference.any() ) will produce:: SELECT * FROM my_table WHERE NOT (EXISTS (SELECT 1 FROM related WHERE related.my_id=my_table.id)) :meth:`~.RelationshipProperty.Comparator.any` is only valid for collections, i.e. a :func:`_orm.relationship` that has ``uselist=True``. For scalar references, use :meth:`~.RelationshipProperty.Comparator.has`. z9'any()' not implemented for scalar attributes. Use has().rrArJrrrkrrs r-anyz#RelationshipProperty.Comparator.any}sDR==((00- *4)))>v> >r.c ~|jjrtjd|j|fi|S)aProduce an expression that tests a scalar reference against particular criterion, using EXISTS. An expression like:: session.query(MyClass).filter( MyClass.somereference.has(SomeRelated.x==2) ) Will produce a query like:: SELECT * FROM my_table WHERE EXISTS (SELECT 1 FROM related WHERE related.id==my_table.related_id AND related.x=2) Because :meth:`~.RelationshipProperty.Comparator.has` uses a correlated subquery, its performance is not nearly as good when compared against large target tables as that of using a join. :meth:`~.RelationshipProperty.Comparator.has` is only valid for scalar references, i.e. a :func:`_orm.relationship` that has ``uselist=False``. For collection references, use :meth:`~.RelationshipProperty.Comparator.any`. z4'has()' not implemented for collections. Use any().rrs r-hasz#RelationshipProperty.Comparator.hassA8}}$$00M*4)))>v> >r.c |jjstjd|jj ||j }|jj |j||_|S)a Return a simple expression that tests a collection for containment of a particular item. :meth:`~.RelationshipProperty.Comparator.contains` is only valid for a collection, i.e. a :func:`_orm.relationship` that implements one-to-many or many-to-many with ``uselist=True``. When used in a simple one-to-many context, an expression like:: MyClass.contains(other) Produces a clause like:: mytable.id == Where ```` is the value of the foreign key attribute on ``other`` which refers to the primary key of its parent object. From this it follows that :meth:`~.RelationshipProperty.Comparator.contains` is very useful when used with simple one-to-many operations. For many-to-many operations, the behavior of :meth:`~.RelationshipProperty.Comparator.contains` has more caveats. The association table will be rendered in the statement, producing an "implicit" join, that is, includes multiple tables in the FROM clause which are equated in the WHERE clause:: query(MyClass).filter(MyClass.contains(other)) Produces a query like:: SELECT * FROM my_table, my_association_table AS my_association_table_1 WHERE my_table.id = my_association_table_1.parent_id AND my_association_table_1.child_id = Where ```` would be the primary key of ``other``. From the above, it is clear that :meth:`~.RelationshipProperty.Comparator.contains` will **not** work with many-to-many collections when used in queries that move beyond simple AND conjunctions, such as multiple :meth:`~.RelationshipProperty.Comparator.contains` expressions joined by OR. In such cases subqueries or explicit "outer joins" will need to be used instead. See :meth:`~.RelationshipProperty.Comparator.any` for a less-performant alternative using EXISTS, or refer to :meth:`_query.Query.outerjoin` as well as :ref:`orm_queryguide_joins` for more details on constructing outer joins. kwargs may be ignored by this operator but are required for API conformance. z9'contains' not implemented for scalar attributes. Use ==r) rrArJrrrrE'_Comparator__negated_contains_or_equalsnegation_clause)rkrrclauses r-containsz(RelationshipProperty.Comparator.containss}v==((00*]]55DLL6F}}**6)-)J)J*&Mr.cjjtk(rtj|}fd}fd}jj rmt jjjDcgc];\}}t j|||||||k7||dk(=c}}St jtjjjjjj|Dcgc] \}}||k( c}}}j|Scc}}wcc}}w)Nc |j}tj|j|jdj j j j|||S)NT)type_unique callable_)dictr bindparamrztyper_get_attr_w_warn_on_noner|) local_colstate remote_coldict_rks r-state_bindparamzURelationshipProperty.Comparator.__negated_contains_or_equals..state_bindparamsS!JJE==! 'nn#"&--"H"H MM00% # r.cBjrj|S|Sr)rcolrks r-adaptzKRelationshipProperty.Comparator.__negated_contains_or_equals..adapt*s||#||C00" r.)rrGr rinstance_state_use_getrrrYor_zipr| primary_keyprimary_key_from_instancer)rkrrrrxyrs` r-__negated_contains_or_equalsz This will typically produce a clause such as:: mytable.related_id != Where ```` is the primary key of the given object. The ``!=`` operator provides partial functionality for non- many-to-one comparisons: * Comparisons against collections are not supported. Use :meth:`~.RelationshipProperty.Comparator.contains` in conjunction with :func:`_expression.not_`. * Compared to a scalar one-to-many, will produce a clause that compares the target columns in the parent to the given target. * Compared to a scalar many-to-many, an alias of the association table will be rendered as well, forming a natural join that is part of the main body of the query. This will not work for queries that go beyond simple AND conjunctions of comparisons, such as those which use OR. Use explicit joins, outerjoins, or :meth:`~.RelationshipProperty.Comparator.has` in conjunction with :func:`_expression.not_` for more comprehensive non-many-to-one scalar membership tests. * Comparisons against ``None`` given in a one-to-many or many-to-many context produce an EXISTS clause. Nrr)rrrrrrrGr rrrrrArJrrrs r-__ne__z&RelationshipProperty.Comparator.__ne__HsN%$--!AB==**i7(99 t||: 1133&&009 %T%F%Fu%MNNr.cb|jjj|jSr)rr_check_configurers r-rz(RelationshipProperty.Comparator.propertys" II   - - /99 r.)NNr=r)__name__ __module__ __qualname____doc__rrr@rrmemoized_propertyrr|rrrrrr__hash__rrrrrrrrr=r.r-r\rGs ( !  2&     ,  ,&    (  (    (  ( I  4   8 tW r/ ?b ?DI V+ 6Z8 Ot      r.r\c|Jd}|-t|}|jr|jj}|j |d||S)NT)value_is_parentrr)rr_adapter adapt_clauser)rkinstancer from_entityrinsps r- _with_parentz!RelationshipProperty._with_parents_###  ";'D$$#}}99 &&  %+ '  r.c 3 t tddstjdz| }j ||S|s.j jj jc}n-j jj jc}|r j n j tjj  fd}j 4|r2t#j j%j'|}t)j*|id|i}|r||}|S#tj$rdY`wxYw)N is_instanceFzMapped instance expected for relationship comparison to object. Classes, queries and other SQL elements are not accepted in this context; for comparison with a subquery, use %s.has(**criteria).rcp|jvr'j|j|_yyr)_identifying_keyrcallable)r bind_to_colrr|rkrs r-visit_bindparamz@RelationshipProperty._optimized_compare..visit_bindparams@))[8%)%B%B : :; & "9r.r)rrJNoInspectionAvailablerrK_lazy_none_clause_lazy_strategy _lazywhere _bind_to_col_rev_lazywhere_rev_bind_to_colr|rr instance_dictobjrCr rrrcloned_traverse) rkrrrrreverse_directionrrrrr|s `` @@@r-rz'RelationshipProperty._optimized_compares   }GE=%$H**.15 5!0/ =))! * !##..##00 #I{ ##22##44 #I{ [[F[[F((5   >> %/%446hy! ,, rK9  $Y/Iq//  s EE54E5czjjjfd}|S)aKCreate the callable that is used in a many-to-one expression. E.g.:: u1 = s.query(User).get(5) expr = Address.user == u1 Above, the SQL should be "address.user_id = 5". The callable returned by this method produces the value "5" based on the identity of ``u1``. cjjx}}|tju}j j rtj n tjtjz }|tjur'|s`tjddtd|tjur'|s'tjddtd|}|tjdz|S)NpassivezCan't resolve value for column z on object z'; no value has been set for this columnz2; the object is detached and the value was expiredzGot None for value of column %s; this is unsupported for a relationship comparison and will not currently produce an IS comparison (but may in a future release))_last_known_valuesrzrNO_VALUE_get_state_attr_by_column persistent PASSIVE_OFFPASSIVE_NO_FETCHINIT_OK NEVER_SETrJrrPASSIVE_NO_RESULTrrW) last_known to_returnexisting_is_available current_valuecolumnrr|rrs r-_goz:RelationshipProperty._get_attr_w_warn_on_none.._go s%*%=%=dhh%G GJ$.j6I6I$I ! #<<###..00:3E3EE =M 4 44, 44"9U#35 *">">>, 44&,Yu-=? *   47==  r.)get_property_by_column_track_last_known_valuerz)rkr|rrr.r/rs ```` @r-rz-RelationshipProperty._get_attr_w_warn_on_nones<V,,V4 %%dhh/( ( T r.c|s-|jj|jj}}n,|jj|jj}}t ||}|r||}|Sr)rrrrrr)rkrrrrs r-rz&RelationshipProperty._lazy_none_clause7sr ##..##00#I ##22##44#I ,I{C $Y/Ir.ctt|jjjdz|jzS)N.)strrryrrzrs r-__str__zRelationshipProperty.__str__Is+4;;%%../#5@@r.c b|r|jD] } || f|vs yd|jvry|j|vry|jrO|j |j} | j ||} | j r| jrJ |r1|j |jj||tg} | D]]} tj| }tj| }d|||f<|j|||||}|M| j|_|s:tj|||j}| D]}|j!|y|j |jj#||| dty||j} | Htj| }tj| }d|||f<|j|||||}nd}|s|||j<y|j |jj#|||dy)Nr>Tr)load _recursive_resolve_conflict_mapF)_adaptr )rc_cascaderzrAget_implget_collection collectionemptygetrrrr_mergeappendinit_state_collectionappend_without_eventrb)rksession source_state source_dict dest_state dest_dictr8r9r:rimplinstances_iterable dest_listcurrent current_state current_dictrcollcs r-r>zRelationshipProperty.mergeLsU ++  !$ 2  $-- '  88; &  <<((2D!%!4!4\;!O  48??)// LL ##DHH-11 =2I- * * 9 9' B )77@ 48 M401nn! )*? %?$$S) *!77 488#1A--a01##DHH-11 ) 2"$((+G" * 9 9' B )77@ 48 M401nn! )*? %&) $((###DHH-11 3r.cJ|j|j}|j|||}|tjus|gSt |dr8|j ||||Dcgc]}tj||fc}Stj||fgScc}w)zReturn a list of tuples (state, obj) for the given key. returns an empty list if the value is None/empty/PASSIVE_NO_RESULT rr>)managerrLrArr)hasattrr>r)rkrrrzr rLros r-_value_as_iterablez'RelationshipProperty._value_as_iterables}}S!&& HHUE7H 3 ,, , I T+ ,,,UE1g,N**1-q1   ..q1156 6 s'B c #K|dk7s |jrtj}ntj}|dk(r4|j|j j j||}n|j|||j |}|dk(xrd|jv}|D]\} } | |vr | tj| } |r || r.|r | j s=| jj} | j|jjjs=td|j d|jj d| j"d |j%| | | | | fyw) Ndeletez save-updaterzrefresh-expire delete-orphanz Attribute 'z ' on class 'z"' doesn't handle objects of type '')r5rPASSIVE_NO_INITIALIZEr%rUrzrLget_all_pendingrXr<rr|isa class_managerAssertionErrorrryroadd) rkrrrvisited_stateshalt_onr tuples skip_pendingrrSrinstance_mappers r-cascade_iteratorz%RelationshipProperty.cascade_iteratorsq H  4 4 66G ,,G M !]]488,11AA%OF,,udhh-F % % N/*N "( D NA/y &44Q7M7>2N$6$6,44;;O"&&t{{'@'@'G'GH$xx!3!3Q[[B   ~ ._nmC C? DsE=E?c8|jry|jduS)NF)rHrLrs r-_effective_sync_backrefz,RelationshipProperty._effective_sync_backrefs ==$$E1 1r.c|jr(|jrtjd|d|d|jr$|js|jdurd|_yyyy)N Relationship z( cannot specify sync_backref=True since z includes viewonly=True.F)rHrLrJr)rel_arel_bs r-_check_sync_backrefz(RelationshipProperty._check_sync_backrefsc >>e00,,-2E;  NNNN""%/!&E 0# r.c |jj|d}t|tst j d|d|d|j |||j |||jj||jj||jj|js+t jd|d|d|d |j|jttfvrB|j|jk(r(t j|d |d |jd yy) NF)_configure_mappersz back_populates on relationship 'z' refers to attribute 'z{' that is not a relationship. The back_populates parameter should refer to the name of a relationship on the target class.zreverse_property z on relationship z references relationship z", which does not reference mapper z and back-reference z are both of the same direction z<. Did you mean to set remote_side on the many-to-one side ?)r| get_propertyrr2rJrrorcrb common_parentrrKrGr r )rkrzrs r-_add_reverse_propertyz*RelationshipProperty._add_reverse_property s  (((G%!56,,!%)    u-   - ""5) ##D)||))$++6&&eT[[2  NNy)4 4%//1&&$0 2 5r.zsqlalchemy.orm.mappercztjj}t|jtj r!|j |j}nXt|jr7t|jt|jfs|j }n |j}t|tr|j|dS t|}t|dr|Stjd|j dt|d#tj$rYDwxYw)zReturn the target mapped entity, which is an inspect() of the class or aliased class that is referred towards. F configurer|relationship 'z2' expects a class or a mapper argument (received: ))r preloaded orm_mapperrrB string_types_clsregistry_resolve_namerrMapper class_mapperrrVrJrrKrz)rk mapperlibrBrs r-rzRelationshipProperty.entity5sNN-- dmmT%6%6 7Dt55dmmDFH dmm $Z MMD)"2"23. }}H}}H h %))(e)D D X&Fvx( ""xxh )  ++   s D$$D:9D:c.|jjS)zReturn the targeted :class:`_orm.Mapper` for this :class:`.RelationshipProperty`. This is a lazy-initializing static attribute. )rr|rs r-r|zRelationshipProperty.mapperZs{{!!!r.c|j|j|j|j|j |j |j |j|jjtt|3|jd|_y)N))r<r:)_check_conflicts_process_dependent_arguments_setup_registry_dependencies_setup_join_conditions_check_cascade_settingsr< _post_init_generate_backref_join_condition"_warn_for_conflicting_sync_targetsr?r2do_init _get_strategyr)rkros r-rzRelationshipProperty.do_initds  ))+ ))+ ##% $$T]]3    ??A "D13"001FGr.c|jjjj|jjjyr)rr|registry_set_depends_onrrs r-rz1RelationshipProperty._setup_registry_dependenciesps3 ##33 KK   ' ' r.c dD]y}t||}t|tjr't |||j ||dk(Pt |s\t|rht |||{dD]K}t||}|t ||ttjtj||M|j;t|jr&tjd|jd|d |j d ur@|j 4t#d tj$|j D|_tj&d tj(|j*D|_tj&d tj(|j,D|_|j.j0|_y)zConvert incoming configuration arguments to their proper form. Callables are resolved, ORM annotations removed. )rhrDrErCrNrPrC) favor_tables)rDrENargnamezsecondary argument z passed to to relationship() z must be a Table object or other FROM clause; can't send a mapped class directly as rows in 'secondary' are persisted independently of a class that is mapped to that same table.Fc3hK|]*}tjtj|d,yw)rhrNrr)rr*.0rs r- zDRelationshipProperty._process_dependent_arguments..s7"  ,,a"02c3hK|]*}tjtj|d,yw)rlrNrrs r-rzDRelationshipProperty._process_dependent_arguments..s7:    ((!^  : rc3hK|]*}tjtj|d,yw)rPrNrrs r-rzDRelationshipProperty._process_dependent_arguments..s7+    ((!]  + r)rrrr|setattr_clsregistry_resolve_argrrrrr)rr*rCrJrKrhtupleto_list column_set to_column_setrNrPrpersist_selectabletarget)rkattr attr_valuevals r-rz1RelationshipProperty._process_dependent_argumentsus  2D!t,J*d&7&78D11"1D2*%.>z.JdJL1' 2.3 D$%C#!((!44c4  >> %*:4>>*J&& *. ?  == %$--*C!"dmm4 "DM+///: ''(G(GH : + ' ??+ ''(8(89 +  kk44 r.c\tdid|jjd|jjd|jjd|jjd|j d|j d|jd|jjd |jjd |jd |jd |jd |jd|d|j d|jx|_}|j |_|j|_|j"|_|j|_ |j$|_ |j&|_|j(|_|j*|_|j.|_y)Nparent_persist_selectablechild_persist_selectableparent_local_selectablechild_local_selectablerDrCrEparent_equivalentschild_equivalentsconsider_as_foreign_keysrYrPself_referentialr support_synccan_be_synced_fnr=) JoinConditionrrr local_tablerDrCrE_equivalent_columnsr|rNrYrPrrH_columns_are_mappedrrGremote_columns local_columnssynchronize_pairsforeign_key_columns_calculated_foreign_keyssecondary_synchronize_pairs)rkjcs r-rz+RelationshipProperty._setup_join_conditionss$1% &*kk&D&D% %)[[%C%C% %)KK$;$;% $(;;#:#: % (( % nn % ,,%  ${{>>% #kk==% &*%D%D%  $66% ((% "66% % "]]*% "55!%  r$>>--"$"7"7,,--!#!5!5(*(>(>%+-+I+I(r.c |jdS)Nr_clsregistry_resolversrs r-rz-RelationshipProperty._clsregistry_resolve_arg**1--r.c |jdS)Nrrrs r-r}z.RelationshipProperty._clsregistry_resolve_namerr.zsqlalchemy.orm.clsregistryctjjj}||jj |Sr)rrzorm_clsregistry _resolverrry)rkrs r-rz+RelationshipProperty._clsregistry_resolverss0NN22<< ++T22r.c tjj}|jjr|j |jj dj|jsetjd|jd|jj jd|jj jdyy)zOTest that this relationship is legal, warn about inheritance conflicts.Frvz)Attempting to assign a new relationship 'z$' to a non-primary mapper on class 'zm'. New relationships can only be added to the primary mapper, i.e. the very first mapper created for class 'z' N) rrzr{r non_primaryrry has_propertyrzrJrKr)rkrs r-rz%RelationshipProperty._check_conflictssNN-- ;; " "9+A+A KK  %,B, ,txx ,!&&HHKK&&//KK&&//   ,! "r.c|jS)z\Return the current cascade setting for this :class:`.RelationshipProperty`. )r<rs r-rgzRelationshipProperty.cascade s }}r.c&|j|yr) _set_cascaderkrgs r-rgzRelationshipProperty.cascade s '"r.cnt|}|jrZt|jtj}|r0t j ddjt|zd|jvr|j|||_ |jr||j_ yy)NzsCascade settings "%s" apply to persistence operations and should not be combined with a viewonly=True relationship., r|)rrHrb difference_viewonly_cascadesrJrKjoinsorted__dict__rr<_dependency_processorrg)rkrg non_viewonlys r-rz!RelationshipProperty._set_cascade s ) ==w<2211L**$'+yy 1E'FH t}} $  ( ( 1  % %18D & & . &r.cx|jr|js|jtus|jturot j d||jturdnd|jjj|jjjdzd|jdk(r d|vsd |vrt j d |z|jrT|jjjj|j|jjfyy) NaFor %(direction)s relationship %(rel)s, delete-orphan cascade is normally configured only on the "one" side of a one-to-many relationship, and not on the "many" side of a many-to-one or many-to-many relationship. To force this relationship to allow a particular "%(relatedcls)s" object to be referred towards by only a single "%(clsname)s" object at a time via the %(rel)s relationship, which would allow delete-orphan cascade to take place in this direction, set the single_parent=True flag.z many-to-onez many-to-many)relrGclsname relatedclsbbf0codeallrZr[z^On %s, can't set passive_deletes='all' in conjunction with 'delete' or 'delete-orphan' cascade) delete_orphanrMrGr r rJrKrryrr|r5primary_mapper_delete_orphansrCrzrs r-rz,RelationshipProperty._check_cascade_settings( s  ! !&&:-91L&& / ~~2"/'#{{11::"&++"4"4"="= *- 2   5 (  ?g#=&&;=AB   KK & & ( 8 8 ? ?4;;--.  !r.cl|j|jvxr|j|j|uS)zaReturn True if this property will persist values on behalf of the given mapper. )rz relationshipsr{s r- _persists_forz"RelationshipProperty._persists_forT s7 HH,, , 7$$TXX.$6 r.c$|D]}|j&|jjj|r5|jjjj|re|j jj|ryy)zReturn True if all columns in the given collection are mapped by the tables referenced by this :class:`.Relationship`. FT)rCrScontains_columnrrr)rkcolsrSs r-rz(RelationshipProperty._columns_are_mapped_ sw  A*NN$$44Q7;;1133CCkkmm33A6 r.c |jjry|jx|jskt |jt j r|ji}}n|j\}}|jj}|jsvt|jj|j}|D]?}|j|s|jr"tj d|d|d|d|j"M|j%d|j&j(}|j%d|j&j*}nO|j%d|j&j,}|j%dd}|rtj.d|j%d |j0}|jj} |j3d |j4|j3d |j6|j3d |j8|j3d |j:||_t=| |j"||f||j>d|} |jA|| |jr|jC|jyy)zlInterpret the 'backref' instruction to create a :func:`_orm.relationship` complementary to this one.NzError creating backref 'z' on relationship 'z+': property of that name exists on mapper 'r\rDrEzOCan't assign 'secondaryjoin' on a backref against a non-secondary relationship.rlrHrFr6rL)rlri)"rrrjrirrr|r|rconcreterbiterate_to_rootunionself_and_descendantsrrJrKrCpoprsecondaryjoin_minus_localprimaryjoin_minus_localprimaryjoin_reverse_remoterrN setdefaultrHrFr6rLr2rz_configure_propertyrt) rk backref_keyrr|checkmrrrlrr3s r-rz&RelationshipProperty._generate_backrefp sp ;; " "  << #D,?,?$,,(9(9:&*llBV &*ll# V[[//1F??F2245;;//A~~k21::$22 +D!5~~)ZZ!((BBZZ#((@@ ZZ!((CCZZ6 44@ ":: ? ?L[[//1F   j$-- 8   mT-=-= >   /1E1E F   nd.?.? @"-D /  *#xx L  & &{L A     & &t':': ; r.zsqlalchemy.orm.dependencyctjj}|j|jt u|_|j s!|jj||_ yyr) rrzorm_dependencyrArGr rHDependencyProcessorfrom_relationshipr)rk dependencys r-rzRelationshipProperty._post_init sV^^22 << >>:DL}}..@@0  &r.c2|j}|jS)zPmemoize the 'use_get' attribute of this RelationshipLoader's lazyloader.)ruse_get)rkstrategys r-rzRelationshipProperty._use_get s &&r.cL|jj|jSr)r|rsrrs r-rz)RelationshipProperty._is_self_referential s{{((55r.cd}|r|jd}|.|r,|jjr|jj}|r|j}||j }d}n |j}|O|j j }|jjrd}|jrE|C|j}d}n0||jjus|jjrd}|j} |xs,|duxr&||jjuxs |j}|jj|||| |\} } } } }||jj}||j j}| | ||| | fS)NFT)rCrwith_polymorphicrr|rrrrr _is_subqueryr join_targetsr)rkrrrrrraliased dest_mapperrrDrErCrs r-rz"RelationshipProperty._create_joins s t~~9G  $!dkk&B&B$(KK$L$L! (//K&"0";";++K  ""kk44O{{++((->-F"1"G"G"I 4;;#K#K K{{++G!99  T ) !{{??@2$11   - -              $ $ 7 7   ""kk55O         r.)TN)FNT)FNr)FNNNFr=)7rrrrstrategy_wildcard_key inherit_cache_links_to_entityrrrrr@rIr}r r\r rrrr6r>rr%rXrhrrj staticmethodrortrrpreload_modulerr|rrrrrr}rrrgsetterrrrrrrrrr __classcell__)ros@r-r2r2]s +M !  )*;<)*;<+,?@ ()9:*+=>  ',Iq#f$ ~^~@  " BH\|$A\~*4)?)?7,<@6Dp22  ' ''R T01! 2! F "" H P5dJ:.... T56373 T012(  ^^##9**X  "K.clone# s@ dJ33 4>>+"2"2"45D 5) r.r=)elementrr s `@r-r(r(" s# . E Nr.c eZdZddddddddddddf dZdZdZdZed Zed Z e jd Z d Z e jd Ze jdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZ d Z!d!Z"e#jHZ%d"Z&e jd#Z'e jd$Z(e jd%Z)d&Z*d'Z+ d*d(Z,d+d)Z-y),rNFTcy)NTr=)rSs r-zJoinCondition.A sr.c||_||_||_||_||_| |_||_||_||_| |_ | |_ | |_ ||_ | |_ ||_||_|j!|j#|j%|j'|j)|j+|j-|j/|j d|j|j/|jd|j1|j3|j5yNTF)rrrrrrrDrErCrrn _remote_siderrrr_determine_joins_sanitize_joins _annotate_fks_annotate_remote_annotate_local_annotate_parentmapper _setup_pairs_check_foreign_cols_determine_direction_check_remote_side _log_joins)rkrrrrrDrCrErrrrYrPrrrrs r-r@zJoinCondition.__init__0 s1&*C&'>$(@%&<#"4!2&*"(@%#5 ' 0( 0      ##%    !1!148    )  $ $T%7%7 ? !!# ! r.c |jy|jj}|jd|j|j|jd|j|j|jd|jdj d|j D|jd|jdj d|jxsgD|jd|jdj d |jD|jd |jdj d |jD|jd |jdj d |jD|jd|j|jy)Nz%s setup primary join %sz%s setup secondary join %sz%s synchronize pairs [%s],c34K|]\}}d|d|dyw(z => ryNr=rlrKs r-rz+JoinCondition._log_joins..j s*01a1%z#%s secondary synchronize pairs [%s]c34K|]\}}d|d|dywr(r=r*s r-rz+JoinCondition._log_joins..q s!Q!"1%r,z%s local/remote pairs [%s]c34K|]\}}d|d|dyw)r)z / ryNr=r*s r-rz+JoinCondition._log_joins..y s)/!Qq!$r,z%s remote columns [%s]c3&K|] }d|z ywz%sNr=rrs r-rz+JoinCondition._log_joins.. s?CTCZ?z%s local columns [%s]c3&K|] }d|z ywr0r=r1s r-rz+JoinCondition._log_joins.. s>CTCZ>r2z%s relationship direction %s) rloggerr`rDrErrrrYrrrG)rkrs r-r$zJoinCondition._log_joinsa s 99  ii+TYY8H8HI-tyy$:L:LM ' II HH484J4J    1 II HH">>D"    ( II HH373J3J    $ II HH?4+>+>? ?  # II HH>4+=+=> > /DNNKr.ct|jd|_|jt|jd|_yy)abremove the parententity annotation from our join conditions which can leak in here based on some declarative patterns and maybe others. We'd want to remove "parentmapper" also, but apparently there's an exotic use case in _join_fixture_inh_selfref_w_entity that relies upon it being present, see :ticket:`3364`. )rw proxy_keyvaluesN)rrDrErs r-rzJoinCondition._sanitize_joins sI,   %B     )!1""+H"D  *r.c |j.|j"tjd|jz |j xsd}|j}|j2t |j|j|j||_|jst |j|j|j||_ y|j3t |j|j|j||_ yyy#tj$r}|jFtjtjd|jd|jd|n AE J   4// ~~) 44 99dnn 6   44E))$   ! s,BD>DI*)B F<<I*B I%%I*c0t|jdSNlocalr&r7)rrDrs r-rz%JoinCondition.primaryjoin_minus_local s 0 09LMMr.c0t|jdSrB)rrErs r-rz'JoinCondition.secondaryjoin_minus_local s 2 2;NOOr.c|jr$d}tj|ji|S|jrt |jdSt |jS)a(Return the primaryjoin condition suitable for the "reverse" direction. If the primaryjoin was delivered here with pre-existing "remote" annotations, the local/remote annotations are reversed. Otherwise, the local/remote annotations are removed. cd|jvr.t|j}|d=d|d<|j|Sd|jvr.t|j}|d=d|d<|j|Sy)Nr&TrD) _annotationsr_with_annotations)rrus r-replacez9JoinCondition.primaryjoin_reverse_remote..replace sw333W112A( !%AgJ"44Q77 4 44W112A' "&AhK"44Q77 5r.rCr7)_has_remote_annotationsrreplacement_traverserD_has_foreign_annotationsr)rkrJs r-rz(JoinCondition.primaryjoin_reverse_remote sd  ' ' 8001A1A2wO O,,'$$-@((8(899r.cZtj|iD]}||jvsyyr)riteraterHrkr annotationrs r-_has_annotationzJoinCondition._has_annotation/ s4##FB/ CS--- r.c:|j|jdSNr0rRrDrs r-rMz&JoinCondition._has_foreign_annotations6 s##D$4$4i@@r.c:|j|jdSNr&rUrs r-rKz%JoinCondition._has_remote_annotations: s##D$4$4h??r.cx|jry|jr|jy|jy)zAnnotate the primaryjoin and secondaryjoin structures with 'foreign' annotations marking columns considered as foreign. N)rMr_annotate_from_fk_list_annotate_present_fksrs r-rzJoinCondition._annotate_fks> s1  ( (   ( (  ' ' )  & & (r.cfd}tjji|_j'tjji|_yy)NcH|jvr|jddiSyNr0T)rrrs r-check_fkz6JoinCondition._annotate_from_fk_list..check_fkM s*d333}}i%6774r.rrLrDrE)rkr^s` r-rYz$JoinCondition._annotate_from_fk_listL s] 8$88   b(     )!)!>!>""B"D  *r.cV|j*tj|jjn t fdfd}t j |jid|i|_|j)t j |jid|i|_yy)Nct|tjr@t|tjr&|j|r|S|j|r|Sr|vr|vr|S|vr|vr|Syyyr)rrColumn references)ab secondarycolss r- is_foreignz7JoinCondition._annotate_present_fks..is_foreign_ sw!V]]+ 1fmm0L<<?H\\!_H %!=*@H-'A],BH-C'r.c4t|jtjr$t|jtjsyd|jj vrd|jj vr|j|j}|}|j |jr#|jjddi|_y|j |jr#|jjddi|_yyyyyr])rleftr ColumnElementrightrHcomparer)binaryrrgs r- visit_binaryz9JoinCondition._annotate_present_fks..visit_binaryl s S.. c.?.?@!9!99V\\%>%>> fll;?{{6;;/&,kk&;&;Y> % OODNN,<,<=MEM  &$33   b8\":     )!)!9!9""B<(@"D  *r.c|j|jdgfd}tj|jid|idS)zvReturn True if the join condition contains column comparisons where both columns are in both tables. Fc|j|j}}t|tjrt|tjrvj |j rZj |j r>j |j r"j |j rdd<yyyyyyy)NTr)rirkrrris_derived_fromtable)rmrSfmtptresults r-rnz;JoinCondition._refers_to_parent_table..visit_binary s;; qA1j556q*"9"9:&&qww/&&qww/&&qww/&&qww/ q 0000;7r.rmr)rrrrrD)rkrnrtrurvs @@@r-_refers_to_parent_tablez%JoinCondition._refers_to_parent_table sP  + +  * * ! $**B<0HIayr.cBt|j|jS)z5Return True if parent/child tables have some overlap.)r"rrrs r-_tables_overlapzJoinCondition._tables_overlap s"#  * *D,I,I  r.cT|jry|j|jy|js |jr|j y|j r|jddy|jr|jy|jy)zAnnotate the primaryjoin and secondaryjoin structures with 'remote' annotations marking columns considered as part of the 'remote' side. Ncd|jvSrT)rH)rs r-rz0JoinCondition._annotate_remote.. sI)9)99r.F) rKrC_annotate_remote_secondaryrnr_annotate_remote_from_argsrw_annotate_selfrefry_annotate_remote_with_overlap%_annotate_remote_distinct_selectablesrs r-rzJoinCondition._annotate_remote s  ' '  >> %  + + -  % %):):  + + -  ) ) +  " "95  ! ! #  . . 0  6 6 8r.cfd}tjji|_tjji|_y)z^annotate 'remote' in primaryjoin, secondaryjoin when 'secondary' is present. cvjjj|r|jddiSyNr&T)rCrSrrrrks r-replz6JoinCondition._annotate_remote_secondary..repl s6~~//8(((D)9::9r.Nr_rkrs` r-r|z(JoinCondition._annotate_remote_secondary sL  ;$88   b$ &::   D r.chfd}tjjid|i_y)zxannotate 'remote' in primaryjoin, secondaryjoin when the relationship is detected as self-referential. c|jj|j}t|jtj rt|jtj rm|jr"|jj ddi|_|jr&|s#|jj ddi|_yyysjyyr)rirlrkrrrr_warn_non_column_elements)rmequatedfnremote_side_givenrks r-rnz5JoinCondition._annotate_selfref..visit_binary skk))&,,7G&++z'>'>?J j55Efkk?"(++"7"748H"IFKfll#G#)<<#9#98T:J#KFL-4#&..0'r.rmN)rrrD)rkrrrns``` r-r~zJoinCondition._annotate_selfref s/ 1$33   b8\": r.cf|jrA|jrtjd|jDcgc]\}}| c}}n |j|j r|j fddyfd}t j|ji||_ycc}}w)zannotate 'remote' in primaryjoin, secondaryjoin when the 'remote_side' or '_local_remote_pairs' arguments are used. zTremote_side argument is redundant against more detailed _local_remote_side argument.c |vSrr=)rrPs r-rz:JoinCondition._annotate_remote_from_args.. s sk/Ar.TcF|tvr|jddiSyr)rbr)rrPs r-rz6JoinCondition._annotate_remote_from_args..repl s-c+..",,h-=>>/r.N) rnrrJrKrwr~rrLrD)rkr+rKrrPs @r-r}z(JoinCondition._annotate_remote_from_args s  # #  **  ,0+C+CD!Q1DK++K  ' ' )  " "#A4 H ? (<<  "d D Es B-cfd}jduxr,jjjjufdtjj id|i_y)zannotate 'remote' in primaryjoin, secondaryjoin when the parent/child tables have some set of tables in common, though is not a fully self-referential relationship. c|j|j\|_|_|j|j\|_|_yr)rirk)rmproc_left_rights r-rnzAJoinCondition._annotate_remote_with_overlap..visit_binary sE(7 V\\) %FK)8 fkk) %FL&+r.Nc~t|tjr{t|tjrajjj |r8j jj |r|jddi}||fSrH|jjdjjur|jddi}||fSrH|jjdjjur|jddi}||fSj||fS)Nr&Tr) rrrrrSrrrrHrArr|r)rirkcheck_entitiesrks r-rzDJoinCondition._annotate_remote_with_overlap..proc_left_right s#$ 7 78Zz..>0022BB4466FFtL!OOXt,<=E; &&**>:dii>N>NN4(89; %%)).9TYY=M=MM~~x&67; ..0; r.rm)rr|rrrrD)rkrnrrs` @@r-rz+JoinCondition._annotate_remote_with_overlap se  IIT ! Ndii&6&6dii>N>N&N  .$33   b8\": r.c\fd}tjji|_y)z}annotate 'remote' in primaryjoin, secondaryjoin when the parent/child tables are entirely separate. c jjj|r^jjj|r%jjj|r|j ddiSyyr)rrSrrrrrs r-rzAJoinCondition._annotate_remote_distinct_selectables..repl: ss,,..>>wG0022BB7K..00@@I(((D)9::JHr.N)rrLrDrs` r-rz3JoinCondition._annotate_remote_distinct_selectables3 s* ;$88   b$ r.cHtjd|jzy)NzNon-simple column elements in primary join condition for property %s - consider using remote() annotations to mark the remote side.)rrWrrs r-rz'JoinCondition._warn_non_column_elementsE s   <>Bii H r.cr|j|jdry|jr3tj|jDcgc]\}}| c}}n)tj|j j fd}tj|ji||_ycc}}w)aCAnnotate the primaryjoin and secondaryjoin structures with 'local' annotations. This annotates all column elements found simultaneously in the parent table and the join condition that don't have a 'remote' annotation set up from _annotate_remote() or user-defined. rDNcRd|jvr|vr|jddiSyy)Nr&rDT)rHr)r local_sides r-locals_z.JoinCondition._annotate_local..locals_a s4t000TZ5G~~wo666H0r.) rRrDrnrrrrSrrL)rkr+rKrrs @r-rzJoinCondition._annotate_localL s    0 0' :   # #!%!9!9:v1:J)G)G)I)IJJ 7$88   b' ;s B3 cvjyfd}tjji|_y)Ncd|jvr'|jdjjiSd|jvr'|jdjjiSy)Nr&rrD)rHrrr|r)rrks r-parentmappers_z.parentmappers_m s`4,,,~~~tyy7G7G&HIID---~~~tyy7G7G&HII.r.)rrrLrD)rkrs` r-rz$JoinCondition._annotate_parentmapperi s8 99   J $88   b. r.c^|js#tjd|jdt j |j jj|jj}|jD]#\}}||vs t jd|d%y)Nrla could not determine any unambiguous local/remote column pairs based on join condition and remote_side arguments. Consider using the remote() annotation to accurately mark those elements of the join condition that are on the remote side of the relationship.z Expression z is marked as 'remote', but these column(s) are local to the local side. The remote() annotation is needed only for a self-referential relationship where both sides of the relationship refer to the same tables.) rYrJrKrrrrrSrrrW)rk not_target_rmts r-r#z JoinCondition._check_remote_sidew s&&&&(,yy3  ..00j66889 11 3*$II  ! r.cd}|j|d}t|}|rt|j}nt|j}|jr|s|js|ry|jr<|r:|s8d|xrdxsdd|d|j d }|d z }t j|d |xrdxsdd|d|j d }|d z }t j|) zHCheck the foreign key columns collected and emit error messages.Fr0NzbCould not locate any simple equality expressions involving locally mapped foreign key columns for primaryrCz join condition 'z' on relationship r4a Ensure that referencing columns are associated with a ForeignKey or ForeignKeyConstraint, or are annotated in the join condition with the foreign() annotation. To allow comparison operators other than '==', the relationship can be marked as viewonly=True.z6Could not locate any relevant foreign key columns for z Ensure that referencing columns are associated with a ForeignKey or ForeignKeyConstraint, or are annotated in the join condition with the foreign() annotation.)_gather_columns_with_annotationboolrrrrrJrK)rkr!rcan_sync foreign_cols has_foreignerrs r-r!z!JoinCondition._check_foreign_cols s;; I <( D223HD<<=H   %%+    X) 8[8"II  I C&&s+ + ) 8[8"II    C &&s+ +r.c|j t|_ytj|j j }tj|jj }|j|j}|j|j}|r|r|j|jdd}t|j|jdDcgc]}d|jvr|c}}|rI|rG|jj|j}|j!|}|j!|}|r|s t"|_y|r|s t$|_yt'j(d|j*z|r t"|_y|r t$|_yt'j(d|j*zcc}w)z[Determine if this relationship is one to many, many to one, many to many. Nr&r0aDCan't determine relationship direction for relationship '%s' - foreign key columns within the join condition are present in both the parent and the child's mapped tables. Ensure that only those columns referring to a parent column are marked as foreign, either via the foreign() annotation or via the foreign_keys argument.zCan't determine relationship direction for relationship '%s' - foreign key columns are present in neither the parent nor the child's mapped tables)rEr rGrrrrSr intersectionrrrDrbrHrrrr r rJrKr) rk parentcols targetcols onetomany_fk manytoone_fkonetomany_localrSmanytoone_local self_equateds r-r"z"JoinCondition._determine_direction s    )'DN)G)G)I)IJJ)F)F)H)HIJ&2243K3KLL&2243K3KLL #'"F"F$$h # #&"&!E!E ,,i"$1>>9 ###'#6#6#C#C**$L'6&@&@&NO&5&@&@&NO #?%.DN$_%.DN ..9<@99E  !*!***47;ii@Ws%Gct|Dcgc]%\}}|j|jf'c}}Scc}}w)zprovide deannotation for the various lists of pairs, so that using them in hashes doesn't incur high-overhead __eq__() comparisons against original columns mapped. ) _deannotate)rkr?rrs r-_deannotate_pairszJoinCondition._deannotate_pairs* s/@JJtq!!--/2JJJs*4c*g}tjgg}fd}j|fj|ffD]\}}| |||j _j |_j |_y)Nc.fd}t||y)Ncd|jvr3d|jvr%j|rj||fn@d|jvr2d|jvr$j|rj||f|jtj urXj||rEd|jvrj ||fyd|jvrj ||fyyyy)Nr&r0)rHrrboperatorreqrC)rmrirkr?lrprks r-rnz.go..visit_binary9 s 2 22 (9(99--d3GGT5M* 1 11 (:(::--e4GGUDM*??ill2t7L7L%8!E$6$66"))4-8"d&7&77"))5$-88 82r.r#)joincondr?rnrrks ` r-goz&JoinCondition._setup_pairs..go8 s 9* !x 8r.)r OrderedSetrDrErrYrr)rk sync_pairssecondary_sync_pairsrrr?rs` @r-r zJoinCondition._setup_pairs3 s oob!! 92  z *   !5 6%  % Hj x $  %#'"8"8"=!%!7!7 !C+/+A+A , (r.cj|jsy|jDcgc] \}}||f c}}|jDcgc] \}}||f c}}zD]\}|jvr/t j |j |i|j<Dg}|j}|jD]\}}|jjr||j jvs7|j|j jvsZ|j j|jvs}d|j jvsd|jvs|j jj|jr|j jj|jr|j jj|jr7|j jj|jrh|j j|jk7s1|j jj|jr|j!||f|r~t#j$d|j d|dddj't)fd|Ddd j't)d |Dd |j d d ||j|j <ycc}}wcc}}w)Nz__*rxz' will copy column z to column z(, which conflicts with relationship(s): rc3<K|]\}}d|d|ddyw)r\z ' (copies z to ryNr=)rprfr_to_s r-rzCJoinCondition._warn_for_conflicting_sync_targets.. s&'"(1SACC$M'"sa. If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="r&c3:K|]\}}|jywr)rz)rrfrs r-rzCJoinCondition._warn_for_conflicting_sync_targets.. s+Mvr2BFF+Msz "' to the 'z' relationship.qzyxr)rrr_track_overlapping_sync_targetsweakrefWeakKeyDictionaryrrqr|_dispose_calledrcrzrfr is_siblingrsrCrrWrr)rkr;r other_props prop_to_fromrrs ` r-rz0JoinCondition._warn_for_conflicting_sync_targets` s  .2-C-C )eSUCL .2-M-M )eSUCL  L MJE3$>>>--tyy%.@A44! #CCCH +1136GBII55dii&A&AAFF$))*=*== IIMM=")<)<<!5 $ 0 0 ; ;BII F $ 0 0 ; ;BII F $ 0 0 ; ;BII F $ 0 0 ; ;BII F IIMMRVV3#'99#3#3#A#A"))#L$**B95164II!II! II &'"5@'"!"  HHV+M+M%MN II14$7:HM44S9$))DYL M  s L)L/c$|jdSrW_gather_join_annotationsrs r-rzJoinCondition.remote_columns s,,X66r.c$|jdS)NrDrrs r-rzJoinCondition.local_columns s,,W55r.c$|jdSrTrrs r-rz!JoinCondition.foreign_key_columns s,,Y77r.ct|j|j|}|j+|j |j|j||Dchc]}|j c}Scc}wr)rbrrDrEupdater)rkrQsrs r-rz&JoinCondition._gather_join_annotations sq   0 01A1A: N     ) HH44&&   *++A +++s!A;ct|}ttj|iDcgc]}|j|jr|!c}Scc}wr)rbrrOissubsetrHrPs r-rz-JoinCondition._gather_columns_with_annotation sV_ $++FB7 &&s'7'78    s$Act|ddi}|j|j|j}}}| |||z}n||z}|r-||t j |z}n|t j |z}|r||j d}t|td} t||jj| } |:t|tdjt||j} | j|}nUt|td|j} |0| jt|td |jd} | j|}| xs| } d| _ nd} |||| |fS) a7Given a source and destination selectable, create a join between them. This takes into account aliasing the join clause to reference the appropriate corresponding columns in the target objects, as well as the extra child criterion, equivalent column sets, etc. rTN)flatrD) exclude_fn) equivalents)rrr&)rrDrErCrrrr _ColInAnnotationsrchainrrr) rkrrrrrrDrErCprimary_aliasizersecondary_aliasizerrs r-rzJoinCondition.join_targets s*, 7>        NN%.]   "( - ; )K7 ( -.0I I )CHHn,EE $%;;;F $1*;G*D%!'4#1G1G'%)*$%0(5!.?.H)e%-(,(?(?&!4 < <] K $1#09 $ 6 6%! %0%++%-'8'B(,(?(?'+#+44[AK0E4EN(,N %!N        r.c tj tj}|jdu rItjt  |j D] \}} |j||f|||<"n5s|j D] \}}|||< n|j D] \}}|||<  fd}|j}|jstj|i|}|j;|j}rtj|i|}tj||} Dcic]} |j|} }|| |fScc}w)Ncsd|jvsrEr|vss=d|jvr/|vr&tjdd|jd|<|Sy)NrDr&T)rr)rHrrr)rbinds has_secondarylookuprs r- col_to_bindz5JoinCondition.create_lazy_clause..col_to_bindLsi'7c6F6F+F$"sf})h#:J:J.Je#!$d#((4"E#JSz!r.)r column_dictrE collections defaultdictlistrYrCrDrrLrrrz) rkrequated_columnsr+rKr lazywhererErrrrrs ` @@@r-create_lazy_clausez JoinCondition.create_lazy_clause:sw  "**,**$6  ,,T2F// '1q   !Q(%&" '#// '1%&" '// '1%&" ' "$$    %-> 552{I    ) ..M ( = =!2{! M:I6;rs' ""!!&+!  '(.$%*+&(A' .A' A' HN ~7F~7B" + +r.