Файловый менеджер - Редактировать - /opt/imh-python/lib/python3.9/site-packages/sqlalchemy/orm/__pycache__/query.cpython-39.pyc
Ðазад
a _�h�� � @ sF d Z ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlm Z dd lm Z dd l m Z dd l m Z dd l mZ dd l mZ ddl mZ ddl mZ ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlm Z ddlmZ ddlm Z ddlm Z ddlm Z dd lm!Z! dd lmZ dd l!m"Z" dd l!mZ# dd l!m$Z$ dd l%m&Z& dd!l'm(Z( dd"l)m*Z* g d#�Z+ej,Z-e j.e j/G d$d%� d%e0���Z1G d&d'� d'e*�Z2G d(d)� d)e0�Z3G d*d+� d+e3�Z4e j.G d,d-� d-e��Z5G d.d/� d/e3�Z6G d0d1� d1e3�Z7G d2d3� d3e0�Z8G d4d5� d5ej9�Z:d6S )7a The Query class and support. Defines the :class:`_query.Query` class, the central construct used by the ORM to construct database queries. The :class:`_query.Query` class should not be confused with the :class:`_expression.Select` class, which defines database SELECT operations at the SQL (non-ORM) level. ``Query`` differs from ``Select`` in that it returns ORM-mapped objects and interacts with an ORM session, whereas the ``Select`` construct interacts directly with the database to return iterable result sets. � )�chain� )� attributes)�exc)� interfaces)�loading)� persistence)� properties��_entity_descriptor)� _generative)�_is_aliased_class)�_is_mapped_class�� _orm_columns)�InspectionAttr)� PathRegistry)�_entity_corresponds_to)�aliased)� AliasedClass)�join)� object_mapper)� ORMAdapter)� with_parent� )�inspect)� inspection)�log)�sql)�util)� expression)�visitors)�ColumnCollection)�_interpret_as_from)� ForUpdateArg)�Query� QueryContextr c @ s� e Zd ZdZdZdZdZdZdZdZ dZ dZ dZ dZ dZdZdZdZdZdZe� ZdZdZdZdZdZdZdZ dZ dZ dZ i Z dZ!dZ"e#�$� Z%Z&e#�$� Z'e#�$� Z(e#�$� Z)dZ*dZ+dZ,dZ-dZ.e/Z0dZ1dZ2dZ3�ddd�Z4�ddd �Z5d d � Z6d d � Z7dd� Z8dd� Z9dd� Z:dd� Z;e<� dd� �Z=e<� dd� �Z>dd� Z?d d � Z@d d � ZAd d!� ZBeCd"d#� �ZDd$d%� ZEd&d'� ZFd(d)� ZG�dd*d+�ZHd,d-� ZId.d/� ZJd0d1� ZK�dd2d3�ZL�dd4d5�ZMd6d7� ZNd8d9� ZOd:d;� ZP�dd<d=�ZQd>d?� ZReCd@dA� �ZS�ddBdC�ZT�ddDdE�ZUdFdG� ZVdHdI� ZWeCdJdK� �ZXdLdM� ZYe<� dNdO� �ZZeCdPdQ� �Z[e<� dRdS� �Z\dTdU� Z]e<� dVdW� �Z^e<� dXdY� �Z_eCdZd[� �Z`e<� d\d]� �Zae<eN��dd^d_��Zbe<� d`da� �Zcdbdc� Zddeejfdfddde�Zg�ddfdg�Zhe<� dhdi� �Zie<� djdk� �Zje<� dldm� �Zke<� dndo� �Zl�d dpdq�Zme<� �d drds��Zne<� dtdu� �Zodvdw� Zpe<� dxdy� �Zqe<� dzd{� �Zrd|d}� ZsesZtd~d� Zue<� d�d�� �Zve<� d�d�� �Zwe#�xd�d�d�d�d�� �Zyd�d�� Zzd�d�� Z{e<� d�d�� �Z|d�d�� Z}e<� �d d�d���Z~�d d�d��Zd�d�� Z�e<� d�d�� �Z�e<� e#��d�d��d�d�� ��Z�e<� �d d�d���Z�e<� d�d�� �Z�e<eOeP�d�d�� �Z�d�d�� Z�e<eOeP�d�d�� �Z�e<eOeP�d�d�� �Z�e<eOeP�d�d�� �Z�d�d�� Z�d�d�� Z�d�d�� Z�d�d�� Z�d�d�� Z�d�d�� Z�d�d�� Z�d�d�� Z�d�d�� Z�d�d�� Z�e<eOeP�d�d�� �Z�d�d Z�d�dĄ Z�d�dƄ Z�d�dȄ Z�d�dʄ Z�e<eO�d�d̄ �Z�e<eN�d�d΄ �Z�e<eN�d�dЄ �Z�d�d҄ Z�e<eO�d�dԄ �Z�e<eO�d�dք �Z�e<eO�d�d �Z�e<eO�d�dڄ �Z�e<� d�d܄ �Z�e<� d�dބ �Z�d�d� Z�e<eN�d�d� �Z�d�d� Z�d�d� Z�d�d� Z�d�d� Z�d�d� Z�d�d� Z�d�d� Z�d�d� Z�d�d� Z�d�d�� Z�eCd�d�� �Z��d!d�d��Z��d"d�d��Z�eCd�d�� �Z�eCd��d � �Z��d�d� Z��d�d� Z��d#�d�d�Z��d$�d�d �Z��d%�d �d �Z��d �d � Z��d�d� Z��d�d� Z�dS (& r% ax ORM-level SQL construction object. :class:`_query.Query` is the source of all SELECT statements generated by the ORM, both those formulated by end-user query operations as well as by high level internal operations such as related collection loading. It features a generative interface whereby successive calls return a new :class:`_query.Query` object, a copy of the former with additional criteria and options associated with it. :class:`_query.Query` objects are normally initially generated using the :meth:`~.Session.query` method of :class:`.Session`, and in less common cases by instantiating the :class:`_query.Query` directly and associating with a :class:`.Session` using the :meth:`_query.Query.with_session` method. For a full walkthrough of :class:`_query.Query` usage, see the :ref:`ormtutorial_toplevel`. FTN� c C s || _ i | _| �|� dS )a� Construct a :class:`_query.Query` directly. E.g.:: q = Query([User, Address], session=some_session) The above is equivalent to:: q = some_session.query(User, Address) :param entities: a sequence of entities and/or SQL expressions. :param session: a :class:`.Session` with which the :class:`_query.Query` will be associated. Optional; a :class:`_query.Query` can be associated with a :class:`.Session` generatively via the :meth:`_query.Query.with_session` method as well. .. seealso:: :meth:`.Session.query` :meth:`_query.Query.with_session` N)�session�_polymorphic_adapters� _set_entities)�self�entitiesr( r' r' ��/root/rpmbuild/BUILDROOT/imh-python39-modules-3.9.7-92.el8.x86_64/opt/imh-python/lib/python3.9/site-packages/sqlalchemy/orm/query.py�__init__� s zQuery.__init__c C sP |d u r t }g | _d | _d| _|dkrLt�|�D ]}|| |� q0| �| j� d S )NFr' )� _QueryEntity� _entities�_primary_entity�_has_mapper_entitiesr �to_list�_set_entity_selectables)r+ r, �entity_wrapper�entr' r' r- r* � s zQuery._set_entitiesc C s� | j �� | _ }|D ]�}|jD ]~}||vr�t|�}|jsp|jjrp|jj| jvrj| � |jt � |j |jj �� d }n|jr~|j}nd }||f||< |j|| � q qd S �N)�_mapper_adapter_map�copyr, r �is_aliased_class�mapper�with_polymorphic�persist_selectabler) �"_mapper_loads_polymorphically_with�sql_util� ColumnAdapter� selectable�_equivalent_columns�_adapter� setup_entity)r+ r, �dr6 �entity�ext_info�aliased_adapterr' r' r- r4 � s4 ������ z Query._set_entity_selectablesc C s: |j p |gD ](}|| j|< |�� D ]}|| j|j< q"q d S r7 )�_with_polymorphic_mappersr) �iterate_to_root� local_table)r+ r; �adapter�m2�mr' r' r- r> s z(Query._mapper_loads_polymorphically_withc C s g }d }|D ]�}t |�}t|d�rV|js.|jrV|| _|rH|jsHt�d��|�|j� q |j sht�d��q t |t j �r||� � }|r�|}|�|� q t|�| _|r�t| j�dkr�t |t j�r�| �� }t�| jd |�| _n2|�rt| j�dk�rt|d��r|j�r|j| _d S )Nr; zPA selectable (FromClause) instance is expected when the base alias is being set.zJargument is not a mapped class, mapper, aliased(), or FromClause instance.r r )r �hasattr� is_mapperr: �_select_from_entity�sa_exc� ArgumentError�appendrA � is_selectable� isinstancer � SelectBase�alias�tuple� _from_obj�len�Alias�_Query__all_equivsr? r@ �_from_obj_aliasrC )r+ �objZset_base_alias�faZselect_from_alias�from_obj�info�equivsr' r' r- �_set_select_from sX �� �� � � � �� ���zQuery._set_select_fromc C s< |j D ]0}| j�|d � |�� D ]}| j�|jd � q qd S r7 )rI r) �poprJ rK )r+ r; rM rN r' r' r- �_reset_polymorphic_adapter7 s z Query._reset_polymorphic_adapterc C sx d|j v r0|j d }| j�|d �}|r0|�|�S t|tj�rB|}nt|d�rT|j}nd S | j�|d �}|rt|�|�S d S )N� parententity�table) � _annotationsr) �getZ adapt_clauserV r � FromClauserO rh )r+ �element�searchrX r' r' r- �_adapt_polymorphic_element= s z Query._adapt_polymorphic_elementc s � fdd�|D �S )Nc s g | ]}� � t�|�d d ��qS )T)� _adapt_clauser Z_literal_as_label_reference��.0�o�r+ r' r- � <listcomp>P s � �z)Query._adapt_col_list.<locals>.<listcomp>r' )r+ �colsr' rs r- �_adapt_col_listO s �zQuery._adapt_col_listc C s || _ d S r7 )�lazy_loaded_from)r+ �stater' r' r- �_set_lazyload_fromW s zQuery._set_lazyload_fromc C s d| _ d S �NF)�_orm_only_adaptrs r' r' r- �_adapt_all_clauses[ s zQuery._adapt_all_clausesc s� g � | j sd}|r4| jr4| jD ]}� �||jf� q | jrV� �| jrH|nd| jjf� | jrl� �|| jf� � st|S � fdd�}t� |i |�S )z\Adapt incoming clauses to transformations which have been applied within this query.Fc sF d| j v pd| j v }� D ](\}}|r(|r|| �}|d ur| S qd S )NZ _orm_adaptrg �ri )�elemZ is_orm_adaptZ _orm_onlyrL �e��adaptersr' r- �replace s � z$Query._adapt_clause.<locals>.replace) r{ �_filter_aliasesrT r� r^ �_orm_only_from_obj_aliasr) rn r! Zreplacement_traverse)r+ �clauseZ as_filterZorm_onlyr` r� r' r� r- ro _ s$ �� zQuery._adapt_clausec C s | j d S )z Return the first QueryEntity.r �r0 rs r' r' r- �_query_entity_zero� s zQuery._query_entity_zeroc C s | j d jS )z8Return the Mapper associated with the first QueryEntity.r )r0 r; rs r' r' r- � _mapper_zero� s zQuery._mapper_zeroc C s | j dur| j S | �� jS )z�Return the 'entity' (mapper or AliasedClass) associated with the first QueryEntity, or alternatively the 'select from' entity if specified.N)rQ r� � entity_zerors r' r' r- � _entity_zero� s ��zQuery._entity_zeroc c s | j D ]}t|t�r|V qd S r7 )r0 rV � _MapperEntity)r+ r6 r' r' r- �_mapper_entities� s zQuery._mapper_entitiesc C s | j �d| �� �S )N�_joinpoint_entity)� _joinpointrj r� rs r' r' r- �_joinpoint_zero� s zQuery._joinpoint_zeroc C s( | � � }|d ur$t|�}|js$|jS d S r7 )r� r �is_clause_elementr; )r+ �ezero�inspr' r' r- � _bind_mapper� s zQuery._bind_mapperc C s$ | j | jgkr t�d| ��| jjS )Nz4%s() can only be used against a single mapped class.)r0 r1 rR �InvalidRequestErrorr� )r+ Zmethnamer' r' r- �_only_full_mapper_zero� s ��z Query._only_full_mapper_zeroc C s$ t | j�dkr t�|pd��| �� S )Nr z8This operation requires a Query against a single mapper.)r[ r0 rR r� r� )r+ Z rationaler' r' r- �_only_entity_zero� s �zQuery._only_entity_zeroc C s" i }| j D ]}|�|jj� q |S r7 )r� �updater; rB )r+ rc r6 r' r' r- Z __all_equivs� s zQuery.__all_equivsc C s | j dddd�S �Nrj F)�order_by�distinct)�_no_criterion_conditionrs r' r' r- �_get_condition� s �zQuery._get_conditionc C s | j dddd� d S r� )�_no_criterion_assertionrs r' r' r- �_get_existing_condition� s z Query._get_existing_conditionc C sd | j s d S | jd usR| jd usR| jsR| jd usR| jd usR| jsR|rH| jsR|r`| jr`t � d| ��d S �Nz<Query.%s() being called on a Query with existing criterion. ) �_enable_assertions� _criterion� _statementrZ �_limit�_offset� _group_by� _order_by� _distinctrR r� �r+ �methr� r� r' r' r- r� � s6 ���������� ��z Query._no_criterion_assertionc C s6 | � |||� d| _d | _| _d | _ | _| _d S )Nr' F)r� rZ r� r� r� r� r� r� r' r' r- r� � s z Query._no_criterion_conditionc C s, | j s d S | jr t�d| ��| �|� d S r� )r� r� rR r� r� �r+ r� r' r' r- �_no_clauseelement_condition� s ��z!Query._no_clauseelement_conditionc C s& | j s d S | jd ur"t�d| ��d S )Nz[Query.%s() being called on a Query with an existing full statement - can't apply criterion.)r� r� rR r� r� r' r' r- �_no_statement_condition� s ��z Query._no_statement_conditionc C s4 | j s d S | jd us | jd ur0t�d||f ��d S )Nz�Query.%s() being called on a Query which already has LIMIT or OFFSET applied. To modify the row-limited results of a Query, call from_self() first. Otherwise, call %s() before limit() or offset() are applied.)r� r� r� rR r� r� r' r' r- �_no_limit_offset� s ��zQuery._no_limit_offsetc C s: |r || _ |r|| _|r || _|r,t|�| _|r6|| _| S r7 )�_populate_existing�_version_check�_refresh_state�set�_only_load_props�_refresh_identity_token)r+ �populate_existing� version_check�only_load_props� refresh_state�identity_tokenr' r' r- � _get_options s zQuery._get_optionsc C s | j }|�|�}| j�� |_|S r7 �� __class__�__new__�__dict__r9 )r+ �cls�qr' r' r- �_clone s z Query._clonec C s& | j | jd�j}| jr"|�| j�}|S )z�The full SELECT statement represented by this Query. The statement by default will not have disambiguating labels applied to the construct unless with_labels(True) is called first. )�labels)�_compile_context� _with_labels� statement�_params�params)r+ �stmtr' r' r- r� % s zQuery.statementc C s4 | � d�}|r|�� }|j}|r(|�� }|j|d�S )a� Return the full SELECT statement represented by this :class:`_query.Query`, embedded within an :class:`_expression.Alias`. Eager JOIN generation within the query is disabled. :param name: string name to be assigned as the alias; this is passed through to :meth:`_expression.FromClause.alias`. If ``None``, a name will be deterministically generated at compile time. :param with_labels: if True, :meth:`.with_labels` will be called on the :class:`_query.Query` first to apply table-qualified labels to all columns. :param reduce_columns: if True, :meth:`_expression.Select.reduce_columns` will be called on the resulting :func:`_expression.select` construct, to remove same-named columns where one also refers to the other via foreign key or WHERE clause equivalence. F)�name)�enable_eagerloads� with_labelsr� �reduce_columnsrX )r+ r� r� r� r� r' r' r- �subquery5 s zQuery.subqueryc C s | � d�jj||d�S )aF Return the full SELECT statement represented by this :class:`_query.Query` represented as a common table expression (CTE). Parameters and usage are the same as those of the :meth:`_expression.SelectBase.cte` method; see that method for further details. Here is the `PostgreSQL WITH RECURSIVE example <http://www.postgresql.org/docs/8.4/static/queries-with.html>`_. Note that, in this example, the ``included_parts`` cte and the ``incl_alias`` alias of it are Core selectables, which means the columns are accessed via the ``.c.`` attribute. The ``parts_alias`` object is an :func:`_orm.aliased` instance of the ``Part`` entity, so column-mapped attributes are available directly:: from sqlalchemy.orm import aliased class Part(Base): __tablename__ = 'part' part = Column(String, primary_key=True) sub_part = Column(String, primary_key=True) quantity = Column(Integer) included_parts = session.query( Part.sub_part, Part.part, Part.quantity).\ filter(Part.part=="our part").\ cte(name="included_parts", recursive=True) incl_alias = aliased(included_parts, name="pr") parts_alias = aliased(Part, name="p") included_parts = included_parts.union_all( session.query( parts_alias.sub_part, parts_alias.part, parts_alias.quantity).\ filter(parts_alias.part==incl_alias.c.sub_part) ) q = session.query( included_parts.c.sub_part, func.sum(included_parts.c.quantity). label('total_quantity') ).\ group_by(included_parts.c.sub_part) .. seealso:: :meth:`_expression.HasCTE.cte` F)r� � recursive)r� r� �cte)r+ r� r� r' r' r- r� U s 7 �z Query.ctec C s | � d�j�|�S )z�Return the full SELECT statement represented by this :class:`_query.Query`, converted to a scalar subquery with a label of the given name. Analogous to :meth:`_expression.SelectBase.label`. F)r� r� �label)r+ r� r' r' r- r� � s z Query.labelc C s | � d�j�� S )z�Return the full SELECT statement represented by this :class:`_query.Query`, converted to a scalar subquery. Analogous to :meth:`_expression.SelectBase.as_scalar`. F)r� r� � as_scalarrs r' r' r- r� � s zQuery.as_scalarc C s | � � S )z�Return the :class:`_expression.Select` object emitted by this :class:`_query.Query`. Used for :func:`_sa.inspect` compatibility, this is equivalent to:: query.enable_eagerloads(False).with_labels().statement )�__clause_element__rs r' r' r- rA � s zQuery.selectablec C s | � d��� jS rz )r� r� r� rs r' r' r- r� � s zQuery.__clause_element__c C s || _ dS )z�When set to True, the query results will always be a tuple. This is specifically for single element queries. The default is False. .. versionadded:: 1.2.5 .. seealso:: :meth:`_query.Query.is_single_entity` N)�_only_return_tuples�r+ �valuer' r' r- �only_return_tuples� s zQuery.only_return_tuplesc C s" | j o t| j�dko | jd jS )a� Indicates if this :class:`_query.Query` returns tuples or single entities. Returns True if this query returns a single entity for each instance in its result list, and False if this query returns a tuple of entities for each result. .. versionadded:: 1.3.11 .. seealso:: :meth:`_query.Query.only_return_tuples` r r )r� r[ r0 �supports_single_entityrs r' r' r- �is_single_entity� s � �zQuery.is_single_entityc C s || _ dS )a Control whether or not eager joins and subqueries are rendered. When set to False, the returned Query will not render eager joins regardless of :func:`~sqlalchemy.orm.joinedload`, :func:`~sqlalchemy.orm.subqueryload` options or mapper-level ``lazy='joined'``/``lazy='subquery'`` configurations. This is used primarily when nesting the Query's statement into a subquery or other selectable, or when using :meth:`_query.Query.yield_per`. N)�_enable_eagerloadsr� r' r' r- r� � s zQuery.enable_eagerloadsc C s t �d| ��d S )Nz�The yield_per Query option is currently not compatible with %s eager loading. Please specify lazyload('*') or query.enable_eagerloads(False) in order to proceed with query.yield_per().)rR r� )r+ �messager' r' r- � _no_yield_per� s ��zQuery._no_yield_perc C s d| _ dS )a� Apply column labels to the return value of Query.statement. Indicates that this Query's `statement` accessor should return a SELECT statement that applies labels to all columns in the form <tablename>_<columnname>; this is commonly used to disambiguate columns from multiple tables which have the same name. When the `Query` actually issues SQL to load rows, it always uses column labeling. .. note:: The :meth:`_query.Query.with_labels` method *only* applies the output of :attr:`_query.Query.statement`, and *not* to any of the result-row invoking systems of :class:`_query.Query` itself, e.g. :meth:`_query.Query.first`, :meth:`_query.Query.all`, etc. To execute a query using :meth:`_query.Query.with_labels`, invoke the :attr:`_query.Query.statement` using :meth:`.Session.execute`:: result = session.execute(query.with_labels().statement) TN)r� rs r' r' r- r� � s zQuery.with_labelsc C s || _ dS )a Control whether assertions are generated. When set to False, the returned Query will not assert its state before certain operations, including that LIMIT/OFFSET has not been applied when filter() is called, no criterion exists when get() is called, and no "from_statement()" exists when filter()/order_by()/group_by() etc. is called. This more permissive mode is used by custom Query subclasses to specify criterion or other modifiers outside of the usual usage patterns. Care should be taken to ensure that the usage pattern is even possible. A statement applied by from_statement() will override any criterion set by filter() or order_by(), for example. N)r� r� r' r' r- �enable_assertions s zQuery.enable_assertionsc C s | j S )z�A readonly attribute which returns the current WHERE criterion for this Query. This returned value is a SQL expression construct, or ``None`` if no criterion has been established. )r� rs r' r' r- � whereclause% s zQuery.whereclausec C s || _ dS )a Indicate that this query applies to objects loaded within a certain path. Used by deferred loaders (see strategies.py) which transfer query options from an originating query to a newly generated query intended for the deferred load. N)� _current_path)r+ �pathr' r' r- �_with_current_path0 s zQuery._with_current_pathc C sJ | j st�d��| jd �� }|g| jdd� | _|j| |||d� dS )a� Load columns for inheriting classes. :meth:`_query.Query.with_polymorphic` applies transformations to the "main" mapped class represented by this :class:`_query.Query`. The "main" mapped class here means the :class:`_query.Query` object's first argument is a full class, i.e. ``session.query(SomeClass)``. These transformations allow additional tables to be present in the FROM clause so that columns for a joined-inheritance subclass are available in the query, both for the purposes of load-time efficiency as well as the ability to use these columns at query time. See the documentation section :ref:`with_polymorphic` for details on how this method is used. z(No primary mapper set up for this Query.r r N)rA �polymorphic_on)r1 rR r� r0 r� �set_with_polymorphic)r+ �cls_or_mappersrA r� rF r' r' r- r< < s ��zQuery.with_polymorphicc C s || _ | j�d|d��| _dS )a� Yield only ``count`` rows at a time. The purpose of this method is when fetching very large result sets (> 10K rows), to batch results in sub-collections and yield them out partially, so that the Python interpreter doesn't need to declare very large areas of memory which is both time consuming and leads to excessive memory use. The performance from fetching hundreds of thousands of rows can often double when a suitable yield-per setting (e.g. approximately 1000) is used, even with DBAPIs that buffer rows (which are most). The :meth:`_query.Query.yield_per` method **is not compatible subqueryload eager loading or joinedload eager loading when using collections**. It is potentially compatible with "select in" eager loading, **provided the database driver supports multiple, independent cursors** (pysqlite and psycopg2 are known to work, MySQL and SQL Server ODBC drivers do not). Therefore in some cases, it may be helpful to disable eager loads, either unconditionally with :meth:`_query.Query.enable_eagerloads`:: q = sess.query(Object).yield_per(100).enable_eagerloads(False) Or more selectively using :func:`.lazyload`; such as with an asterisk to specify the default loader scheme:: q = sess.query(Object).yield_per(100).\ options(lazyload('*'), joinedload(Object.some_related)) .. warning:: Use this method with caution; if the same instance is present in more than one batch of rows, end-user changes to attributes will be overwritten. In particular, it's usually impossible to use this setting with eagerly loaded collections (i.e. any lazy='joined' or 'subquery') since those collections will be cleared for a new load when encountered in a subsequent result batch. In the case of 'subquery' loading, the full result for all rows is fetched which generally defeats the purpose of :meth:`~sqlalchemy.orm.query.Query.yield_per`. Also note that while :meth:`~sqlalchemy.orm.query.Query.yield_per` will set the ``stream_results`` execution option to True, currently this is only understood by :mod:`~sqlalchemy.dialects.postgresql.psycopg2`, :mod:`~sqlalchemy.dialects.mysql.mysqldb` and :mod:`~sqlalchemy.dialects.mysql.pymysql` dialects which will stream results using server side cursors instead of pre-buffer all rows for this query. Other DBAPIs **pre-buffer all rows** before making them available. The memory use of raw database rows is much less than that of an ORM-mapped object, but should still be taken into consideration when benchmarking. .. seealso:: :meth:`_query.Query.enable_eagerloads` T)Zstream_resultsZmax_row_bufferN)� _yield_per�_execution_options�union)r+ �countr' r' r- � yield_per^ s A�zQuery.yield_perc C s | � |tj�S )aa Return an instance based on the given primary key identifier, or ``None`` if not found. E.g.:: my_user = session.query(User).get(5) some_object = session.query(VersionedFoo).get((5, 10)) some_object = session.query(VersionedFoo).get( {"id": 5, "version_id": 10}) :meth:`_query.Query.get` is special in that it provides direct access to the identity map of the owning :class:`.Session`. If the given primary key identifier is present in the local identity map, the object is returned directly from this collection and no SQL is emitted, unless the object has been marked fully expired. If not present, a SELECT is performed in order to locate the object. :meth:`_query.Query.get` also will perform a check if the object is present in the identity map and marked as expired - a SELECT is emitted to refresh the object as well as to ensure that the row is still present. If not, :class:`~sqlalchemy.orm.exc.ObjectDeletedError` is raised. :meth:`_query.Query.get` is only used to return a single mapped instance, not multiple instances or individual column constructs, and strictly on a single primary key value. The originating :class:`_query.Query` must be constructed in this way, i.e. against a single mapped entity, with no additional filtering criterion. Loading options via :meth:`_query.Query.options` may be applied however, and will be used if the object is not yet locally present. A lazy-loading, many-to-one attribute configured by :func:`_orm.relationship`, using a simple foreign-key-to-primary-key criterion, will also use an operation equivalent to :meth:`_query.Query.get` in order to retrieve the target value from the local identity map before querying the database. See :doc:`/orm/loading_relationships` for further details on relationship loading. :param ident: A scalar, tuple, or dictionary representing the primary key. For a composite (e.g. multiple column) primary key, a tuple or dictionary should be passed. For a single-column primary key, the scalar calling form is typically the most expedient. If the primary key of a row is the value "5", the call looks like:: my_object = query.get(5) The tuple form contains primary key values typically in the order in which they correspond to the mapped :class:`_schema.Table` object's primary key columns, or if the :paramref:`_orm.Mapper.primary_key` configuration parameter were used, in the order used for that parameter. For example, if the primary key of a row is represented by the integer digits "5, 10" the call would look like:: my_object = query.get((5, 10)) The dictionary form should include as keys the mapped attribute names corresponding to each element of the primary key. If the mapped class has the attributes ``id``, ``version_id`` as the attributes which store the object's primary key value, the call would look like:: my_object = query.get({"id": 5, "version_id": 10}) .. versionadded:: 1.3 the :meth:`_query.Query.get` method now optionally accepts a dictionary of attribute names to values in order to indicate a primary key identifier. :return: The object instance, or ``None``. )� _get_implr Zload_on_pk_identity)r+ �identr' r' r- rj � s Vz Query.getc C s |j ||d�}t�| j|||�S )aq Locate an object in the identity map. Given a primary key identity, constructs an identity key and then looks in the session's identity map. If present, the object may be run through unexpiration rules (e.g. load unloaded attributes, check if was deleted). For performance reasons, while the :class:`_query.Query` must be instantiated, it may be instantiated with no entities, and the mapper is passed:: obj = session.query()._identity_lookup(inspect(SomeClass), (1, )) :param mapper: mapper in use :param primary_key_identity: the primary key we are searching for, as a tuple. :param identity_token: identity token that should be used to create the identity key. Used as is, however overriding subclasses can repurpose this in order to interpret the value in a special way, such as if None then look among multiple target tokens. :param passive: passive load flag passed to :func:`.loading.get_from_identity`, which impacts the behavior if the object is found; the object may be validated and/or unexpired if the flag allows for SQL to be emitted. :param lazy_loaded_from: an :class:`.InstanceState` that is specifically asking for this identity as a related identity. Used for sharding schemes where there is a correspondence between an object and a related object being lazy-loaded (or otherwise relationship-loaded). .. versionadded:: 1.2.9 :return: None if the object is not found in the identity map, *or* if the object was unexpired and found to have been deleted. if passive flags disallow SQL and the object is expired, returns PASSIVE_NO_RESULT. In all other cases the instance is returned. .. versionadded:: 1.2.7 �r� )Z identity_key_from_primary_keyr Zget_from_identityr( )r+ r; �primary_key_identityr� Zpassiverw �keyr' r' r- �_identity_lookup� s 1�zQuery._identity_lookupc sJ t � d�r� �� � | �d�}t� t�}|s8tj� dd�� t� �t|j�krjt � dd� dd� |jD �� ��|r�z t � fd d�|j D ��� W nN ty� } z6tjt � d d� d d� |j D �� �|d � W Y d }~n d }~0 0 | j�s@|j�s@| jd u �r@| j|� |d �}|d u�r0| �� t|j|j��s,d S |S |tju �r@d S || � �S )N�__composite_values__rj r7 )�defaultzmIncorrect number of values in identifier to formulate primary key for query.get(); primary key columns are %s�,c s s | ]}d | V qdS �z'%s'Nr' �rq �cr' r' r- � <genexpr>C � z"Query._get_impl.<locals>.<genexpr>c 3 s | ]}� |j V qd S r7 �r� �rq �prop�r� r' r- r� H s �ztIncorrect names of values in identifier to formulate primary key for query.get(); primary key attribute names are %sc s s | ]}d |j V qdS r� r� r� r' r' r- r� S s ��Zreplace_contextr� )rO r� r� rV �dictr r3 r[ Z primary_keyrR r� r �listZ_identity_key_props�KeyError�raise_r� Zalways_refresh�_for_update_argr� r� � issubclassr� �class_r ZPASSIVE_CLASS_MISMATCH)r+ r� Z db_load_fnr� r; Zis_dict�err�instancer' r� r- r� 2 s^ ��� � ��� � ���� zQuery._get_implc G s@ |D ]6}|du r"| j �dg�| _ q| j �t�t|���| _ qdS )a@ Return a :class:`.Query` construct which will correlate the given FROM clauses to that of an enclosing :class:`.Query` or :func:`~.expression.select`. The method here accepts mapped classes, :func:`.aliased` constructs, and :func:`.mapper` constructs as arguments, which are resolved into expression constructs, in addition to appropriate expression constructs. The correlation arguments are ultimately passed to :meth:`_expression.Select.correlate` after coercion to expression constructs. The correlation arguments take effect in such cases as when :meth:`_query.Query.from_self` is used, or when a subquery as returned by :meth:`_query.Query.subquery` is embedded in another :func:`_expression.select` construct. N)� _correlater� r? Zsurface_selectablesr# )r+ �args�sr' r' r- � correlateq s �zQuery.correlatec C s || _ dS )a% Return a Query with a specific 'autoflush' setting. Note that a Session with autoflush=False will not autoflush, even if this flag is set to True at the Query level. Therefore this flag is usually used only to disable autoflush for a specific Query. N)� _autoflush)r+ Zsettingr' r' r- � autoflush� s zQuery.autoflushc C s d| _ dS )aj Return a :class:`_query.Query` that will expire and refresh all instances as they are loaded, or reused from the current :class:`.Session`. :meth:`.populate_existing` does not improve behavior when the ORM is used normally - the :class:`.Session` object's usual behavior of maintaining a transaction and expiring all attributes after rollback or commit handles object state automatically. This method is not intended for general use. .. seealso:: :ref:`session_expire` - in the ORM :class:`_orm.Session` documentation TN)r� rs r' r' r- r� � s zQuery.populate_existingc C s || _ dS )z�Set the 'invoke all eagers' flag which causes joined- and subquery loaders to traverse into already-loaded related objects and collections. Default is that of :attr:`_query.Query._invoke_all_eagers`. N)�_invoke_all_eagersr� r' r' r- �_with_invoke_all_eagers� s z Query._with_invoke_all_eagersc C s� |rt |�}n| �� }|du rnt|�}|jD ]$}t|tj�r,|j|ju r,|} qnq,t� d|jj j |j j f ��| � t|||j��S )a4 Add filtering criterion that relates the given instance to a child object or collection, using its attribute state as well as an established :func:`_orm.relationship()` configuration. The method uses the :func:`.with_parent` function to generate the clause, the result of which is passed to :meth:`_query.Query.filter`. Parameters are the same as :func:`.with_parent`, with the exception that the given property can be None, in which case a search is performed against this :class:`_query.Query` object's target mapper. :param instance: An instance which has some :func:`_orm.relationship`. :param property: String property name, or class-bound attribute, which indicates what relationship from the instance should be used to reconcile the parent/child relationship. :param from_entity: Entity in which to consider as the left side. This defaults to the "zero" entity of the :class:`_query.Query` itself. Nz\Could not locate a property which relates instances of class '%s' to instances of class '%s')r r� r Ziterate_propertiesrV r ZRelationshipPropertyr; rR r� r �__name__r� �filterr rF )r+ r �propertyZ from_entityr� r; r� r' r' r- r � s( � ���� zQuery.with_parentc C s8 |durt ||�}t| j�| _t| |�}| �|g� dS )zIadd a mapped entity to the list of result columns to be returned.N)r r� r0 r� r4 )r+ rF rX rN r' r' r- � add_entity� s zQuery.add_entityc C s || _ dS )a Return a :class:`_query.Query` that will use the given :class:`.Session`. While the :class:`_query.Query` object is normally instantiated using the :meth:`.Session.query` method, it is legal to build the :class:`_query.Query` directly without necessarily using a :class:`.Session`. Such a :class:`_query.Query` object, or any :class:`_query.Query` already associated with a different :class:`.Session`, can produce a new :class:`_query.Query` object associated with a target session using this method:: from sqlalchemy.orm import Query query = Query([MyClass]).filter(MyClass.id == 5) result = query.with_session(my_session).one() N)r( )r+ r( r' r' r- � with_session� s zQuery.with_sessionc G sB | � � �d�j�d�}| �|�}d|_| �� |_|r>|�|� |S )aS return a Query that selects from this Query's SELECT statement. :meth:`_query.Query.from_self` essentially turns the SELECT statement into a SELECT of itself. Given a query such as:: q = session.query(User).filter(User.name.like('e%')) Given the :meth:`_query.Query.from_self` version:: q = session.query(User).filter(User.name.like('e%')).from_self() This query renders as: .. sourcecode:: sql SELECT anon_1.user_id AS anon_1_user_id, anon_1.user_name AS anon_1_user_name FROM (SELECT "user".id AS user_id, "user".name AS user_name FROM "user" WHERE "user".name LIKE :name_1) AS anon_1 There are lots of cases where :meth:`_query.Query.from_self` may be useful. A simple one is where above, we may want to apply a row LIMIT to the set of user objects we query against, and then apply additional joins against that row-limited set:: q = session.query(User).filter(User.name.like('e%')).\ limit(5).from_self().\ join(User.addresses).filter(Address.email.like('q%')) The above query joins to the ``Address`` entity but only against the first five results of the ``User`` query: .. sourcecode:: sql SELECT anon_1.user_id AS anon_1_user_id, anon_1.user_name AS anon_1_user_name FROM (SELECT "user".id AS user_id, "user".name AS user_name FROM "user" WHERE "user".name LIKE :name_1 LIMIT :param_1) AS anon_1 JOIN address ON anon_1.user_id = address.user_id WHERE address.email LIKE :email_1 **Automatic Aliasing** Another key behavior of :meth:`_query.Query.from_self` is that it applies **automatic aliasing** to the entities inside the subquery, when they are referenced on the outside. Above, if we continue to refer to the ``User`` entity without any additional aliasing applied to it, those references wil be in terms of the subquery:: q = session.query(User).filter(User.name.like('e%')).\ limit(5).from_self().\ join(User.addresses).filter(Address.email.like('q%')).\ order_by(User.name) The ORDER BY against ``User.name`` is aliased to be in terms of the inner subquery: .. sourcecode:: sql SELECT anon_1.user_id AS anon_1_user_id, anon_1.user_name AS anon_1_user_name FROM (SELECT "user".id AS user_id, "user".name AS user_name FROM "user" WHERE "user".name LIKE :name_1 LIMIT :param_1) AS anon_1 JOIN address ON anon_1.user_id = address.user_id WHERE address.email LIKE :email_1 ORDER BY anon_1.user_name The automatic aliasing feature only works in a **limited** way, for simple filters and orderings. More ambitious constructions such as referring to the entity in joins should prefer to use explicit subquery objects, typically making use of the :meth:`_query.Query.subquery` method to produce an explicit subquery object. Always test the structure of queries by viewing the SQL to ensure a particular structure does what's expected! **Changing the Entities** :meth:`_query.Query.from_self` also includes the ability to modify what columns are being queried. In our example, we want ``User.id`` to be queried by the inner query, so that we can join to the ``Address`` entity on the outside, but we only wanted the outer query to return the ``Address.email`` column:: q = session.query(User).filter(User.name.like('e%')).\ limit(5).from_self(Address.email).\ join(User.addresses).filter(Address.email.like('q%')) yielding: .. sourcecode:: sql SELECT address.email AS address_email FROM (SELECT "user".id AS user_id, "user".name AS user_name FROM "user" WHERE "user".name LIKE :name_1 LIMIT :param_1) AS anon_1 JOIN address ON anon_1.user_id = address.user_id WHERE address.email LIKE :email_1 **Looking out for Inner / Outer Columns** Keep in mind that when referring to columns that originate from inside the subquery, we need to ensure they are present in the columns clause of the subquery itself; this is an ordinary aspect of SQL. For example, if we wanted to load from a joined entity inside the subquery using :func:`.contains_eager`, we need to add those columns. Below illustrates a join of ``Address`` to ``User``, then a subquery, and then we'd like :func:`.contains_eager` to access the ``User`` columns:: q = session.query(Address).join(Address.user).\ filter(User.name.like('e%')) q = q.add_entity(User).from_self().\ options(contains_eager(Address.user)) We use :meth:`_query.Query.add_entity` above **before** we call :meth:`_query.Query.from_self` so that the ``User`` columns are present in the inner subquery, so that they are available to the :func:`.contains_eager` modifier we are using on the outside, producing: .. sourcecode:: sql SELECT anon_1.address_id AS anon_1_address_id, anon_1.address_email AS anon_1_address_email, anon_1.address_user_id AS anon_1_address_user_id, anon_1.user_id AS anon_1_user_id, anon_1.user_name AS anon_1_user_name FROM ( SELECT address.id AS address_id, address.email AS address_email, address.user_id AS address_user_id, "user".id AS user_id, "user".name AS user_name FROM address JOIN "user" ON "user".id = address.user_id WHERE "user".name LIKE :name_1) AS anon_1 If we didn't call ``add_entity(User)``, but still asked :func:`.contains_eager` to load the ``User`` entity, it would be forced to add the table on the outside without the correct join criteria - note the ``anon1, "user"`` phrase at the end: .. sourcecode:: sql -- incorrect query SELECT anon_1.address_id AS anon_1_address_id, anon_1.address_email AS anon_1_address_email, anon_1.address_user_id AS anon_1_address_user_id, "user".id AS user_id, "user".name AS user_name FROM ( SELECT address.id AS address_id, address.email AS address_email, address.user_id AS address_user_id FROM address JOIN "user" ON "user".id = address.user_id WHERE "user".name LIKE :name_1) AS anon_1, "user" :param \*entities: optional list of entities which will replace those being selected. FN) r� r� r� r �_from_selectable�_enable_single_critr� rQ r* )r+ r, � fromclauser� r' r' r- � from_self s 1��� zQuery.from_selfc C s || _ d S r7 )r )r+ �valr' r' r- �_set_enable_single_crit� s z Query._set_enable_single_critc C sX dD ]}| j �|d � q| �|gd� d| _| j}g | _|D ]}|�| | jd � q<d S )N) r� r� r� r� r� r� � _joinpathr� r� �_having� _prefixes� _suffixesTFr )r� re rd r� r0 �adapt_to_selectablerZ )r+ r �attrZ old_entitiesr r' r' r- r � s zQuery._from_selectablec G s6 |s t d�S | �� }|j|td� |js.d|_t |�S )zgReturn an iterator yielding result tuples corresponding to the given list of columns. r' )r5 � )�iterr� r* � _ColumnEntityr� )r+ �columnsr� r' r' r- �values� s z Query.valuesc C s. zt | �|��d W S ty( Y dS 0 dS )zVReturn a scalar result corresponding to the given column expression. r N)�nextr! � StopIteration�r+ �columnr' r' r- r� s z Query.valuec G s | � |� dS )a7 Return a new :class:`_query.Query` replacing the SELECT list with the given entities. e.g.:: # Users, filtered on some arbitrary criterion # and then ordered by related email address q = session.query(User).\ join(User.address).\ filter(User.name.like('%ed%')).\ order_by(Address.email) # given *only* User.id==5, Address.email, and 'q', what # would the *next* User in the result be ? subq = q.with_entities(Address.email).\ order_by(None).\ filter(User.id==5).\ subquery() q = q.join((subq, subq.c.email < Address.email)).\ limit(1) N)r* )r+ r, r' r' r- � with_entities s zQuery.with_entitiesc G sB t | j�| _t| j�}|D ]}t| |� q| �| j|d� � dS )zXAdd one or more column expressions to the list of result columns to be returned.N)r� r0 r[ r r4 )r+ r% �lr� r' r' r- � add_columns' s zQuery.add_columnsz0.7z9:meth:`.add_column` is superseded by :meth:`.add_columns`c C s | � |�S )z�Add a column expression to the list of result columns to be returned. Pending deprecation: :meth:`.add_column` will be superseded by :meth:`.add_columns`. )r( r$ r' r' r- � add_column4 s zQuery.add_columnc G s | j dg|�R � S )aL Return a new :class:`_query.Query` object, applying the given list of mapper options. Most supplied options regard changing how column- and relationship-mapped attributes are loaded. .. seealso:: :ref:`deferred_options` :ref:`relationship_loader_options` F��_options�r+ r r' r' r- �optionsC s z Query.optionsc G s | j dg|�R � S �NTr* r, r' r' r- �_conditional_optionsU s zQuery._conditional_optionsc G sn | j �� | _ d| j vr"t� | j d< tt�|��}| j| | _|rV|D ]}|�| � qDn|D ]}|�| � qZd S )NZ_unbound_load_dedupes) � _attributesr9 r� rY r Zflatten_iterator� _with_optionsZprocess_query_conditionally� process_query)r+ Z conditionalr �opts�optr' r' r- r+ X s zQuery._optionsc C s || �S )a� Return a new :class:`_query.Query` object transformed by the given function. E.g.:: def filter_something(criterion): def transform(q): return q.filter(criterion) return transform q = q.with_transformation(filter_something(x==5)) This allows ad-hoc recipes to be created for :class:`_query.Query` objects. See the example at :ref:`hybrid_transformers`. r' )r+ �fnr' r' r- �with_transformationh s zQuery.with_transformation�*c C s, |durt |�j}| j|||ff7 _dS )a� Add an indexing or other executional context hint for the given entity or selectable to this :class:`_query.Query`. Functionality is passed straight through to :meth:`_expression.Select.with_hint`, with the addition that ``selectable`` can be a :class:`_schema.Table`, :class:`_expression.Alias`, or ORM entity / mapped class /etc. .. seealso:: :meth:`_query.Query.with_statement_hint` :meth:`.Query.prefix_with` - generic SELECT prefixing which also can suit some database-specific HINT syntaxes such as MySQL optimizer hints N)r rA � _with_hints)r+ rA �text� dialect_namer' r' r- � with_hint{ s zQuery.with_hintc C s | � d||�S )a� Add a statement hint to this :class:`_expression.Select`. This method is similar to :meth:`_expression.Select.with_hint` except that it does not require an individual table, and instead applies to the statement as a whole. This feature calls down into :meth:`_expression.Select.with_statement_hint`. .. versionadded:: 1.0.0 .. seealso:: :meth:`_query.Query.with_hint` N)r; )r+ r9 r: r' r' r- �with_statement_hint� s zQuery.with_statement_hintc C s | j S )z�Get the non-SQL options which will take effect during execution. .. versionadded:: 1.3 .. seealso:: :meth:`_query.Query.execution_options` )r� rs r' r' r- �get_execution_options� s zQuery.get_execution_optionsc K s | j �|�| _ dS )a� Set non-SQL options which take effect during execution. The options are the same as those accepted by :meth:`_engine.Connection.execution_options`. Note that the ``stream_results`` execution option is enabled automatically if the :meth:`~sqlalchemy.orm.query.Query.yield_per()` method is used. .. seealso:: :meth:`_query.Query.get_execution_options` N)r� r� �r+ �kwargsr' r' r- �execution_options� s zQuery.execution_optionsz0.9z�The :meth:`_query.Query.with_lockmode` method is deprecated and will be removed in a future release. Please refer to :meth:`_query.Query.with_for_update`. c C s t �|�| _dS )a" Return a new :class:`_query.Query` object with the specified "locking mode", which essentially refers to the ``FOR UPDATE`` clause. :param mode: a string representing the desired locking mode. Valid values are: * ``None`` - translates to no lockmode * ``'update'`` - translates to ``FOR UPDATE`` (standard SQL, supported by most dialects) * ``'update_nowait'`` - translates to ``FOR UPDATE NOWAIT`` (supported by Oracle, PostgreSQL 8.1 upwards) * ``'read'`` - translates to ``LOCK IN SHARE MODE`` (for MySQL), and ``FOR SHARE`` (for PostgreSQL) .. seealso:: :meth:`_query.Query.with_for_update` - improved API for specifying the ``FOR UPDATE`` clause. N)� LockmodeArg�parse_legacy_queryr� )r+ �moder' r' r- � with_lockmode� s !zQuery.with_lockmodec C s t |||||d�| _dS )a� return a new :class:`_query.Query` with the specified options for the ``FOR UPDATE`` clause. The behavior of this method is identical to that of :meth:`_expression.GenerativeSelect.with_for_update`. When called with no arguments, the resulting ``SELECT`` statement will have a ``FOR UPDATE`` clause appended. When additional arguments are specified, backend-specific options such as ``FOR UPDATE NOWAIT`` or ``LOCK IN SHARE MODE`` can take effect. E.g.:: q = sess.query(User).populate_existing().with_for_update(nowait=True, of=User) The above query on a PostgreSQL backend will render like:: SELECT users.id AS users_id FROM users FOR UPDATE OF users NOWAIT .. versionadded:: 0.9.0 :meth:`_query.Query.with_for_update` supersedes the :meth:`_query.Query.with_lockmode` method. .. note:: It is generally a good idea to combine the use of the :meth:`_orm.Query.populate_existing` method when using the :meth:`_orm.Query.with_for_update` method. The purpose of :meth:`_orm.Query.populate_existing` is to force all the data read from the SELECT to be populated into the ORM objects returned, even if these objects are already in the :term:`identity map`. .. seealso:: :meth:`_expression.GenerativeSelect.with_for_update` - Core level method with full argument and behavioral description. :meth:`_orm.Query.populate_existing` - overwrites attributes of objects already loaded in the identity map. )�read�nowait�of� skip_locked� key_shareN)rA r� )r+ rE rF rG rH rI r' r' r- �with_for_update� s 3�zQuery.with_for_updatec O sN t |�dkr |�|d � nt |�dkr2t�d��| j�� | _| j�|� dS )a� Add values for bind parameters which may have been specified in filter(). Parameters may be specified using \**kwargs, or optionally a single dictionary as the first positional argument. The reason for both is that \**kwargs is convenient, however some parameter dictionaries contain unicode keys in which case \**kwargs cannot be used. r r zFparams() takes zero or one positional argument, which is a dictionary.N)r[ r� rR rS r� r9 )r+ r r? r' r' r- r� & s � z Query.paramsc G sH t |�D ]:}t�|�}| �|dd�}| jdur<| j|@ | _q|| _qdS )a! Apply the given filtering criterion to a copy of this :class:`_query.Query`, using SQL expressions. e.g.:: session.query(MyClass).filter(MyClass.name == 'some name') Multiple criteria may be specified as comma separated; the effect is that they will be joined together using the :func:`.and_` function:: session.query(MyClass).\ filter(MyClass.name == 'some name', MyClass.id > 5) The criterion is any SQL expression object applicable to the WHERE clause of a select. String expressions are coerced into SQL expression constructs via the :func:`_expression.text` construct. .. seealso:: :meth:`_query.Query.filter_by` - filter on keyword expressions. TN)r� r �_expression_literal_as_textro r� �r+ � criterionr' r' r- r ; s z Query.filterc sB | � � � � du r"t�d| �� ��� fdd�|�� D �}| j|� S )a� Apply the given filtering criterion to a copy of this :class:`_query.Query`, using keyword expressions. e.g.:: session.query(MyClass).filter_by(name = 'some name') Multiple criteria may be specified as comma separated; the effect is that they will be joined together using the :func:`.and_` function:: session.query(MyClass).\ filter_by(name = 'some name', id = 5) The keyword expressions are extracted from the primary entity of the query, or the last entity that was the target of a call to :meth:`_query.Query.join`. .. seealso:: :meth:`_query.Query.filter` - filter on SQL expressions. Nz�Can't use filter_by when the first entity '%s' of a query is not a mapped class. Please use the filter method instead, or change the order of the entities in the queryc s g | ]\}}t � |�|k�qS r' r )rq r� r� ��zeror' r- rt � s �z#Query.filter_by.<locals>.<listcomp>)r� rR r� r� �itemsr )r+ r? �clausesr' rN r- � filter_by_ s �� �zQuery.filter_byc G sx t |�dkrB|d du r,d| jv r(d| _dS |d du rBd| _dS | �|�}| jdu s`| jdu rh|| _n | j| | _dS )ag Apply one or more ORDER BY criterion to the query and return the newly resulting :class:`_query.Query`. All existing ORDER BY settings can be suppressed by passing ``None`` - this will suppress any ordering configured on the :func:`.mapper` object using the deprecated :paramref:`.mapper.order_by` parameter. r r Fr� N)r[ r� r� rv rL r' r' r- r� � s zQuery.order_byc G sd t |�dkr"|d du r"d| _dS ttdd� |D �� �}| �|�}| jdu rT|| _n | j| | _dS )a� Apply one or more GROUP BY criterion to the query and return the newly resulting :class:`_query.Query`. All existing GROUP BY settings can be suppressed by passing ``None`` - this will suppress any GROUP BY configured on mappers as well. .. versionadded:: 1.1 GROUP BY can be cancelled by passing ``None``, in the same way as ORDER BY. r r NFc S s g | ] }t |��qS r' r r� r' r' r- rt � r� z"Query.group_by.<locals>.<listcomp>)r[ r� r� r rv rL r' r' r- �group_by� s zQuery.group_byc C sX t �|�}|dur(t|tj�s(t�d��| �|dd�}| jdurN| j|@ | _n|| _dS )a Apply a HAVING criterion to the query and return the newly resulting :class:`_query.Query`. :meth:`_query.Query.having` is used in conjunction with :meth:`_query.Query.group_by`. HAVING criterion makes it possible to use filters on aggregate functions like COUNT, SUM, AVG, MAX, and MIN, eg.:: q = session.query(User.id).\ join(User.addresses).\ group_by(User.id).\ having(func.count(Address.id) > 2) NzHhaving() argument must be of type sqlalchemy.sql.ClauseElement or stringT) r rK rV r � ClauseElementrR rS ro r rL r' r' r- �having� s �� z Query.havingc G s | � || gt|� � ��d�S rz )r r� r )r+ Zexpr_fnr� r' r' r- �_set_op� s ��z Query._set_opc G s | j tjg|�R � S )a� Produce a UNION of this Query against one or more queries. e.g.:: q1 = sess.query(SomeClass).filter(SomeClass.foo=='bar') q2 = sess.query(SomeClass).filter(SomeClass.bar=='foo') q3 = q1.union(q2) The method accepts multiple Query objects so as to control the level of nesting. A series of ``union()`` calls such as:: x.union(y).union(z).all() will nest on each ``union()``, and produces:: SELECT * FROM (SELECT * FROM (SELECT * FROM X UNION SELECT * FROM y) UNION SELECT * FROM Z) Whereas:: x.union(y, z).all() produces:: SELECT * FROM (SELECT * FROM X UNION SELECT * FROM y UNION SELECT * FROM Z) Note that many database backends do not allow ORDER BY to be rendered on a query called within UNION, EXCEPT, etc. To disable all ORDER BY clauses including those configured on mappers, issue ``query.order_by(None)`` - the resulting :class:`_query.Query` object will not render ORDER BY within its SELECT statement. )rV r r� �r+ r� r' r' r- r� � s %z Query.unionc G s | j tjg|�R � S )z�Produce a UNION ALL of this Query against one or more queries. Works the same way as :meth:`~sqlalchemy.orm.query.Query.union`. See that method for usage examples. )rV r � union_allrW r' r' r- rX s zQuery.union_allc G s | j tjg|�R � S )z�Produce an INTERSECT of this Query against one or more queries. Works the same way as :meth:`~sqlalchemy.orm.query.Query.union`. See that method for usage examples. )rV r � intersectrW r' r' r- rY s zQuery.intersectc G s | j tjg|�R � S )z�Produce an INTERSECT ALL of this Query against one or more queries. Works the same way as :meth:`~sqlalchemy.orm.query.Query.union`. See that method for usage examples. )rV r � intersect_allrW r' r' r- rZ s zQuery.intersect_allc G s | j tjg|�R � S )z�Produce an EXCEPT of this Query against one or more queries. Works the same way as :meth:`~sqlalchemy.orm.query.Query.union`. See that method for usage examples. )rV r �except_rW r' r' r- r[ ( s z Query.except_c G s | j tjg|�R � S )z�Produce an EXCEPT ALL of this Query against one or more queries. Works the same way as :meth:`~sqlalchemy.orm.query.Query.union`. See that method for usage examples. )rV r � except_allrW r' r' r- r\ 1 s zQuery.except_allc O sb |� dd�|� dd�|� dd�|� dd�f\}}}}|rNtdd�t|�� ��| j|||||d�S ) aO- Create a SQL JOIN against this :class:`_query.Query` object's criterion and apply generatively, returning the newly resulting :class:`_query.Query`. **Simple Relationship Joins** Consider a mapping between two classes ``User`` and ``Address``, with a relationship ``User.addresses`` representing a collection of ``Address`` objects associated with each ``User``. The most common usage of :meth:`_query.Query.join` is to create a JOIN along this relationship, using the ``User.addresses`` attribute as an indicator for how this should occur:: q = session.query(User).join(User.addresses) Where above, the call to :meth:`_query.Query.join` along ``User.addresses`` will result in SQL approximately equivalent to:: SELECT user.id, user.name FROM user JOIN address ON user.id = address.user_id In the above example we refer to ``User.addresses`` as passed to :meth:`_query.Query.join` as the "on clause", that is, it indicates how the "ON" portion of the JOIN should be constructed. To construct a chain of joins, multiple :meth:`_query.Query.join` calls may be used. The relationship-bound attribute implies both the left and right side of the join at once:: q = session.query(User).\ join(User.orders).\ join(Order.items).\ join(Item.keywords) .. note:: as seen in the above example, **the order in which each call to the join() method occurs is important**. Query would not, for example, know how to join correctly if we were to specify ``User``, then ``Item``, then ``Order``, in our chain of joins; in such a case, depending on the arguments passed, it may raise an error that it doesn't know how to join, or it may produce invalid SQL in which case the database will raise an error. In correct practice, the :meth:`_query.Query.join` method is invoked in such a way that lines up with how we would want the JOIN clauses in SQL to be rendered, and each call should represent a clear link from what precedes it. **Joins to a Target Entity or Selectable** A second form of :meth:`_query.Query.join` allows any mapped entity or core selectable construct as a target. In this usage, :meth:`_query.Query.join` will attempt to create a JOIN along the natural foreign key relationship between two entities:: q = session.query(User).join(Address) In the above calling form, :meth:`_query.Query.join` is called upon to create the "on clause" automatically for us. This calling form will ultimately raise an error if either there are no foreign keys between the two entities, or if there are multiple foreign key linkages between the target entity and the entity or entities already present on the left side such that creating a join requires more information. Note that when indicating a join to a target without any ON clause, ORM configured relationships are not taken into account. **Joins to a Target with an ON Clause** The third calling form allows both the target entity as well as the ON clause to be passed explicitly. A example that includes a SQL expression as the ON clause is as follows:: q = session.query(User).join(Address, User.id==Address.user_id) The above form may also use a relationship-bound attribute as the ON clause as well:: q = session.query(User).join(Address, User.addresses) The above syntax can be useful for the case where we wish to join to an alias of a particular target entity. If we wanted to join to ``Address`` twice, it could be achieved using two aliases set up using the :func:`~sqlalchemy.orm.aliased` function:: a1 = aliased(Address) a2 = aliased(Address) q = session.query(User).\ join(a1, User.addresses).\ join(a2, User.addresses).\ filter(a1.email_address=='ed@foo.com').\ filter(a2.email_address=='ed@bar.com') The relationship-bound calling form can also specify a target entity using the :meth:`_orm.PropComparator.of_type` method; a query equivalent to the one above would be:: a1 = aliased(Address) a2 = aliased(Address) q = session.query(User).\ join(User.addresses.of_type(a1)).\ join(User.addresses.of_type(a2)).\ filter(a1.email_address == 'ed@foo.com').\ filter(a2.email_address == 'ed@bar.com') **Joining to Tables and Subqueries** The target of a join may also be any table or SELECT statement, which may be related to a target entity or not. Use the appropriate ``.subquery()`` method in order to make a subquery out of a query:: subq = session.query(Address).\ filter(Address.email_address == 'ed@foo.com').\ subquery() q = session.query(User).join( subq, User.id == subq.c.user_id ) Joining to a subquery in terms of a specific relationship and/or target entity may be achieved by linking the subquery to the entity using :func:`_orm.aliased`:: subq = session.query(Address).\ filter(Address.email_address == 'ed@foo.com').\ subquery() address_subq = aliased(Address, subq) q = session.query(User).join( User.addresses.of_type(address_subq) ) **Controlling what to Join From** In cases where the left side of the current state of :class:`_query.Query` is not in line with what we want to join from, the :meth:`_query.Query.select_from` method may be used:: q = session.query(Address).select_from(User).\ join(User.addresses).\ filter(User.name == 'ed') Which will produce SQL similar to:: SELECT address.* FROM user JOIN address ON user.id=address.user_id WHERE user.name = :name_1 **Legacy Features of Query.join()** The :meth:`_query.Query.join` method currently supports several usage patterns and arguments that are considered to be legacy as of SQLAlchemy 1.3. A deprecation path will follow in the 1.4 series for the following features: * Joining on relationship names rather than attributes:: session.query(User).join("addresses") **Why it's legacy**: the string name does not provide enough context for :meth:`_query.Query.join` to always know what is desired, notably in that there is no indication of what the left side of the join should be. This gives rise to flags like ``from_joinpoint`` as well as the ability to place several join clauses in a single :meth:`_query.Query.join` call which don't solve the problem fully while also adding new calling styles that are unnecessary and expensive to accommodate internally. **Modern calling pattern**: Use the actual relationship, e.g. ``User.addresses`` in the above case:: session.query(User).join(User.addresses) * Automatic aliasing with the ``aliased=True`` flag:: session.query(Node).join(Node.children, aliased=True).\ filter(Node.name == 'some name') **Why it's legacy**: the automatic aliasing feature of :class:`_query.Query` is intensely complicated, both in its internal implementation as well as in its observed behavior, and is almost never used. It is difficult to know upon inspection where and when its aliasing of a target entity, ``Node`` in the above case, will be applied and when it won't, and additionally the feature has to use very elaborate heuristics to achieve this implicit behavior. **Modern calling pattern**: Use the :func:`_orm.aliased` construct explicitly:: from sqlalchemy.orm import aliased n1 = aliased(Node) session.query(Node).join(Node.children.of_type(n1)).\ filter(n1.name == 'some name') * Multiple joins in one call:: session.query(User).join("orders", "items") session.query(User).join(User.orders, Order.items) session.query(User).join( (Order, User.orders), (Item, Item.order_id == Order.id) ) # ... and several more forms actually **Why it's legacy**: being able to chain multiple ON clauses in one call to :meth:`_query.Query.join` is yet another attempt to solve the problem of being able to specify what entity to join from, and is the source of a large variety of potential calling patterns that are internally expensive and complicated to parse and accommodate. **Modern calling pattern**: Use relationship-bound attributes or SQL-oriented ON clauses within separate calls, so that each call to :meth:`_query.Query.join` knows what the left side should be:: session.query(User).join(User.orders).join( Item, Item.order_id == Order.id) :param \*props: Incoming arguments for :meth:`_query.Query.join`, the props collection in modern use should be considered to be a one or two argument form, either as a single "target" entity or ORM attribute-bound relationship, or as a target entity plus an "on clause" which may be a SQL expression or ORM attribute-bound relationship. :param isouter=False: If True, the join used will be a left outer join, just as if the :meth:`_query.Query.outerjoin` method were called. :param full=False: render FULL OUTER JOIN; implies ``isouter``. .. versionadded:: 1.1 :param from_joinpoint=False: When using ``aliased=True``, a setting of True here will cause the join to be from the most recent joined target, rather than starting back from the original FROM clauses of the query. .. note:: This flag is considered legacy. :param aliased=False: If True, indicate that the JOIN target should be anonymously aliased. Subsequent calls to :meth:`_query.Query.filter` and similar will adapt the incoming criterion to the target alias, until :meth:`_query.Query.reset_joinpoint` is called. .. note:: This flag is considered legacy. .. seealso:: :ref:`ormtutorial_joins` in the ORM tutorial. :ref:`inheritance_toplevel` for details on how :meth:`_query.Query.join` is used for inheritance relationships. :func:`_orm.join` - a standalone ORM-level join function, used internally by :meth:`_query.Query.join`, which in previous SQLAlchemy versions was the primary ORM-level joining interface. r F�from_joinpoint�isouter�full�unknown arguments: %s�, �� outerjoinr_ �create_aliasesr] �re � TypeErrorr �sorted�_join)r+ �propsr? r r] r^ r_ r' r' r- r : s$ � ��z Query.joinc O sV |� dd�|� dd�|� dd� }}}|rBtdd�t|�� ��| j|d|||d�S ) z�Create a left outer join against this :class:`_query.Query` object's criterion and apply generatively, returning the newly resulting :class:`_query.Query`. Usage is the same as the :meth:`_query.Query.join` method. r Fr] r_ r` ra Trb re )r+ ri r? r r] r_ r' r' r- rc _ s � ��zQuery.outerjoinc C sJ || _ d|v r@|d \}}|�� }|�� ||< ||f|d< |}q|| _d S )N�prev)r� r9 r )r+ �jp�frj r' r' r- �_update_joinpointx s zQuery._update_joinpointc C s� |s | � � t|�dkrLt|d tjttf�rLt|d ttjt j f�rL|f}t � |�}t |�D �]B\}}t|t�r||\}} nd} t|t j t jf�r�| | } } n || } } | du r�t| �} | js�t| d�s�t�d��t| t j �r�t| dd�} nd} t| t j��rt| �� | �} nD|�rRt| t j ��rR| �� }t|�}t|dd�| ju �rRt|| j�} t| t j ��r�| du �r�| �rv| } nP| j} z | j} W n> t �y� } z$t j t�d| �|d � W Y d}~n d}~0 0 | j}| j � |d�}t|t ��r|j!�"|��r|j#}t|| j�} | j}t| t$j%��s |} |�s�|| |jf}|| j&v �r�| j&| �'� }|| j&f|d < | �(|� |t|�d kr^t �)d | � q^nd }}| �*|| | ||||� q^dS ) z�Consumes arguments from :meth:`_query.Query.join` or :meth:`_query.Query.outerjoin`, places them into a consistent format with which to form the actual JOIN constructs. r r r Nr; z9Expected mapped entity or selectable/table as join targetZ_of_typez0Join target %s does not refer to a mapped entityr� rj z:Pathed join target %s has already been joined to; skipping)+�_reset_joinpointr[ rV r rk �typer �strrT r �PropComparatorr r3 � enumeraterY � string_typesr rU rO rR rS �getattrr r� � _parententityr� r rF �AttributeErrorr� r) rj r r; ZisaZ aliased_classr �QueryableAttributer� r9 rm �warn�_join_left_to_right)r+ �keysrc r_ rd r] Zkeylist�idxZarg1Zarg2�right�onclause�r_infoZof_typeZjp0rb r �leftrX r� �edgerk r' r' r- rh � s� ��� �� � � � ��� ���z Query._joinc C s | j �� | _ |du r6|du s J �| �|||�\}}} n|dusBJ �| �|�\}} ||u rn|snt�d||f ��| �|||||�\} }}|dur�| j| } | jd|� t| ||||d�f | j|d d� | _n6| dur�| j | j } n|} | jt| ||||d�f | _dS )z�Given raw "left", "right", "onclause" parameters consumed from a particular key within _join(), add a real ORMJoin object to our _from_obj list (or augment an existing one) Nz>Can't construct a join from %s to %s, they are the same entity)r^ r_ r ) r) r9 �"_join_determine_implicit_left_side� _join_place_explicit_left_siderR r� � _join_check_and_adapt_right_siderZ �orm_joinr0 rA ) r+ r r| r} r� rd rc r_ �replace_from_obj_index�use_entity_indexr~ Z left_clauser' r' r- ry s\ �� � �� � ��� �� ��zQuery._join_left_to_rightc C s\ t |�}d }}| jrrt�| j|j|�}t|�dkrH|d }| j| }n(t|�dkr`t�d��nt�d|f ��n�| j�rHi }t | j�D ]R\} } | j } | du r�q�t | �} | |u r�q�t | t �r�| | f|| j< q�d| f|| j< q�t |�� �} t�| |j|�}t|�dk�r || |d \}}n*t|�dk�r6t�d��nt�d|f ��n t�d��|||fS )z�When join conditions don't express the left side explicitly, determine if an existing FROM or entity in this query can serve as the left hand side. Nr r a Can't determine which FROM clause to join from, there are multiple FROMS which can join to this entity. Please use the .select_from() method to establish an explicit left side, as well as providing an explcit ON clause if not present already to help resolve the ambiguity.z�Don't know how to join to %r. Please use the .select_from() method to establish an explicit left side, as well as providing an explcit ON clause if not present already to help resolve the ambiguity.zgNo entities to join from; please use select_from() to establish the left entity/selectable of this join)r rZ r? Z find_left_clause_to_join_fromrA r[ rR r� r0 rr �entity_zero_or_selectablerV r� r� rz )r+ r r| r} r~ r� r� �indexesZ potentialZ entity_indexr6 rF Zent_infoZ all_clausesr' r' r- r� l sb � � �� �� ���z(Query._join_determine_implicit_left_sidec C s� d }}t |�}| jrHt�| j|j�}t|�dkr<t�d��|rH|d }|du r�| jr�t |d�r�t | j�D ]$\}}t |t �rj|� |�rj|} q�qj||fS )z�When join conditions express a left side explicitly, determine where in our existing list of FROM clauses we should join towards, or if we need to make a new join, and if so is it from one of our existing entities. Nr zrCan't identify which entity in which to assign the left side of this join. Please use a more specific ON clause.r r; )r rZ r? Z#find_left_clause_that_matches_givenrA r[ rR r� r0 rO rr rV r� �corresponds_to)r+ r r� r� �l_infor� r{ r6 r' r' r- r� � s. � � ���z$Query._join_place_explicit_left_sidec C sv t |�}t |�}d}|stt|dd�} | rt| js<t| jtj�rt| jpH|jgD ](} t � |j| �rJt � | |j�rJd} qtqJ|s||s�|j|ju r�t � d|j ��t|dd�|jt|dd� } } } | r�|r�| � |j�s�t � d||f ��t|d�r�| j|f7 _d} |j�r�|�r|j} | j�r*| �|dd�}nb|�r|| �| j��sVt � d| j| jjf ��t| tj��rp| �� } d} t| | �}n|�r�t � d ��| �o�| �o�| j�r�t| jtj��p�|}| �s�|�s�|�r�t|dd �}d} | �r| �s�J �t|| j d �}|f| j | _ |�s| � | |� t|tj ��r2| �|dd�}|�s^|�r^| � ||||j!f| j"fd �� n d |i| _"|t |�|fS )z�Transform the "right" side of the join as well as the onclause according to polymorphic mapping translations, aliasing on the query or on the join, special cases where the right and left side have overlapping tables. Fr; NTz*Can't join table/selectable '%s' to itselfr: zIJoin target %s does not correspond to the right side of join condition %sz(Selectable '%s' is not derived from '%s'zpThe aliased=True parameter on query.join() only works with an ORM entity, not a plain selectable, as the target.)Zflat)Z equivalents)r� rj r� )#r rt r< rV r= r ZJoinrZ rA r? Zselectables_overlaprR r� � common_parentr; rO �_join_entitiesr� Z _is_lateralro Zis_derived_from� descriptionrW rX r Z _with_polymorphic_selectabler\ r rB r� r> rT rm r� r� )r+ r r| r} r� rd r� r~ ZoverlapZ right_mapperra Zright_selectableZright_is_aliasedZ need_adapterZaliased_entityrL r' r' r- r� s� � ������ ��� � �� ��� ���� ����� � �� z&Query._join_check_and_adapt_right_sidec C s | j | _d| _d S )Nr' )r r� r� rs r' r' r- rn � s zQuery._reset_joinpointc C s | � � dS )ac Return a new :class:`_query.Query`, where the "join point" has been reset back to the base FROM entities of the query. This method is usually used in conjunction with the ``aliased=True`` feature of the :meth:`_query.Query.join` method. See the example in :meth:`_query.Query.join` for how this is used. N)rn rs r' r' r- �reset_joinpoint� s zQuery.reset_joinpointc G s | � |d� dS )a� Set the FROM clause of this :class:`_query.Query` explicitly. :meth:`_query.Query.select_from` is often used in conjunction with :meth:`_query.Query.join` in order to control which entity is selected from on the "left" side of the join. The entity or selectable object here effectively replaces the "left edge" of any calls to :meth:`_query.Query.join`, when no joinpoint is otherwise established - usually, the default "join point" is the leftmost entity in the :class:`_query.Query` object's list of entities to be selected. A typical example:: q = session.query(Address).select_from(User).\ join(User.addresses).\ filter(User.name == 'ed') Which produces SQL equivalent to:: SELECT address.* FROM user JOIN address ON user.id=address.user_id WHERE user.name = :name_1 :param \*from_obj: collection of one or more entities to apply to the FROM clause. Entities can be mapped classes, :class:`.AliasedClass` objects, :class:`_orm.Mapper` objects as well as core :class:`_expression.FromClause` elements like subqueries. .. versionchanged:: 0.9 This method no longer applies the given FROM object to be the selectable from which matching entities select from; the :meth:`.select_entity_from` method now accomplishes this. See that method for a description of this behavior. .. seealso:: :meth:`_query.Query.join` :meth:`_query.Query.select_entity_from` FN�rd �r+ ra r' r' r- � select_from� s /zQuery.select_fromc C s | � |gd� dS )a� Set the FROM clause of this :class:`_query.Query` to a core selectable, applying it as a replacement FROM clause for corresponding mapped entities. The :meth:`_query.Query.select_entity_from` method supplies an alternative approach to the use case of applying an :func:`.aliased` construct explicitly throughout a query. Instead of referring to the :func:`.aliased` construct explicitly, :meth:`_query.Query.select_entity_from` automatically *adapts* all occurrences of the entity to the target selectable. Given a case for :func:`.aliased` such as selecting ``User`` objects from a SELECT statement:: select_stmt = select([User]).where(User.id == 7) user_alias = aliased(User, select_stmt) q = session.query(user_alias).\ filter(user_alias.name == 'ed') Above, we apply the ``user_alias`` object explicitly throughout the query. When it's not feasible for ``user_alias`` to be referenced explicitly in many places, :meth:`_query.Query.select_entity_from` may be used at the start of the query to adapt the existing ``User`` entity:: q = session.query(User).\ select_entity_from(select_stmt).\ filter(User.name == 'ed') Above, the generated SQL will show that the ``User`` entity is adapted to our statement, even in the case of the WHERE clause: .. sourcecode:: sql SELECT anon_1.id AS anon_1_id, anon_1.name AS anon_1_name FROM (SELECT "user".id AS id, "user".name AS name FROM "user" WHERE "user".id = :id_1) AS anon_1 WHERE anon_1.name = :name_1 The :meth:`_query.Query.select_entity_from` method is similar to the :meth:`_query.Query.select_from` method, in that it sets the FROM clause of the query. The difference is that it additionally applies adaptation to the other parts of the query that refer to the primary entity. If above we had used :meth:`_query.Query.select_from` instead, the SQL generated would have been: .. sourcecode:: sql -- uses plain select_from(), not select_entity_from() SELECT "user".id AS user_id, "user".name AS user_name FROM "user", (SELECT "user".id AS id, "user".name AS name FROM "user" WHERE "user".id = :id_1) AS anon_1 WHERE "user".name = :name_1 To supply textual SQL to the :meth:`_query.Query.select_entity_from` method, we can make use of the :func:`_expression.text` construct. However, the :func:`_expression.text` construct needs to be aligned with the columns of our entity, which is achieved by making use of the :meth:`_expression.TextClause.columns` method:: text_stmt = text("select id, name from user").columns( User.id, User.name) q = session.query(User).select_entity_from(text_stmt) :meth:`_query.Query.select_entity_from` itself accepts an :func:`.aliased` object, so that the special options of :func:`.aliased` such as :paramref:`.aliased.adapt_on_names` may be used within the scope of the :meth:`_query.Query.select_entity_from` method's adaptation services. Suppose a view ``user_view`` also returns rows from ``user``. If we reflect this view into a :class:`_schema.Table`, this view has no relationship to the :class:`_schema.Table` to which we are mapped, however we can use name matching to select from it:: user_view = Table('user_view', metadata, autoload_with=engine) user_view_alias = aliased( User, user_view, adapt_on_names=True) q = session.query(User).\ select_entity_from(user_view_alias).\ order_by(User.name) .. versionchanged:: 1.1.7 The :meth:`_query.Query.select_entity_from` method now accepts an :func:`.aliased` object as an alternative to a :class:`_expression.FromClause` object. :param from_obj: a :class:`_expression.FromClause` object that will replace the FROM clause of this :class:`_query.Query`. It also may be an instance of :func:`.aliased`. .. seealso:: :meth:`_query.Query.select_from` TNr� r� r' r' r- �select_entity_from� s qzQuery.select_entity_fromc C s� t |t�r�t�|�\}}}t |t�r>t |t�r>|| dkr>g S t |t�rP|dk sbt |t�rn|dk rnt| �| S | �||�}|d ur�t|�d d |j� S t|�S n,|dkr�t| �d S t| ||d � �d S d S )Nr ���r )rV �slicer Z decode_slice�intr� �step)r+ �item�start�stopr� �resr' r' r- � __getitem__m s, �� ��� zQuery.__getitem__c C s� |durH|durH| j dur | j nd| _ |dkr<| j |7 _ || | _nT|du r`|dur`|| _n<|dur�|du r�| j dur�| j nd| _ |dkr�| j |7 _ t| j t�r�| j dkr�d| _ dS )a Computes the "slice" of the :class:`_query.Query` represented by the given indices and returns the resulting :class:`_query.Query`. The start and stop indices behave like the argument to Python's built-in :func:`range` function. This method provides an alternative to using ``LIMIT``/``OFFSET`` to get a slice of the query. For example, :: session.query(User).order_by(User.id).slice(1, 3) renders as .. sourcecode:: sql SELECT users.id AS users_id, users.name AS users_name FROM users ORDER BY users.id LIMIT ? OFFSET ? (2, 1) .. seealso:: :meth:`_query.Query.limit` :meth:`_query.Query.offset` Nr )r� r� rV r� )r+ r� r� r' r' r- r� � s z Query.slicec C s || _ dS )zfApply a ``LIMIT`` to the query and return the newly resulting :class:`_query.Query`. N)r� )r+ �limitr' r' r- r� � s z Query.limitc C s || _ dS )zhApply an ``OFFSET`` to the query and return the newly resulting :class:`_query.Query`. N)r� )r+ �offsetr' r' r- r� � s z Query.offsetc G s< |s d| _ n,| �|�}t| j t�r2| j |7 _ n|| _ dS )a� Apply a ``DISTINCT`` to the query and return the newly resulting :class:`_query.Query`. .. note:: The :meth:`.distinct` call includes logic that will automatically add columns from the ORDER BY of the query to the columns clause of the SELECT statement, to satisfy the common need of the database backend that ORDER BY columns be part of the SELECT list when DISTINCT is used. These columns *are not* added to the list of columns actually fetched by the :class:`_query.Query`, however, so would not affect results. The columns are passed through when using the :attr:`_query.Query.statement` accessor, however. :param \*expr: optional column expressions. When present, the PostgreSQL dialect will render a ``DISTINCT ON (<expressions>)`` construct. TN)r� rv rV r� )r+ �exprr' r' r- r� � s zQuery.distinctc G s | j r| j |7 _ n|| _ dS )a� Apply the prefixes to the query and return the newly resulting :class:`_query.Query`. :param \*prefixes: optional prefixes, typically strings, not using any commas. In particular is useful for MySQL keywords and optimizer hints: e.g.:: query = sess.query(User.name).\ prefix_with('HIGH_PRIORITY').\ prefix_with('SQL_SMALL_RESULT', 'ALL').\ prefix_with('/*+ BKA(user) */') Would render:: SELECT HIGH_PRIORITY SQL_SMALL_RESULT ALL /*+ BKA(user) */ users.name AS users_name FROM users .. seealso:: :meth:`_expression.HasPrefixes.prefix_with` N)r )r+ �prefixesr' r' r- � prefix_with� s zQuery.prefix_withc G s | j r| j |7 _ n|| _ dS )ad Apply the suffix to the query and return the newly resulting :class:`_query.Query`. :param \*suffixes: optional suffixes, typically strings, not using any commas. .. versionadded:: 1.0.0 .. seealso:: :meth:`_query.Query.prefix_with` :meth:`_expression.HasSuffixes.suffix_with` N)r )r+ �suffixesr' r' r- � suffix_with s zQuery.suffix_withc C s t | �S )a� Return the results represented by this :class:`_query.Query` as a list. This results in an execution of the underlying SQL statement. .. warning:: The :class:`_query.Query` object, when asked to return either a sequence or iterator that consists of full ORM-mapped entities, will **deduplicate entries based on primary key**. See the FAQ for more details. .. seealso:: :ref:`faq_query_deduplicating` )r� rs r' r' r- �all s z Query.allc C s0 t �|�}t|t jt jf�s&t�d��|| _dS )a1 Execute the given SELECT statement and return results. This method bypasses all internal statement compilation, and the statement is executed without modification. The statement is typically either a :func:`_expression.text` or :func:`_expression.select` construct, and should return the set of columns appropriate to the entity class represented by this :class:`_query.Query`. .. seealso:: :ref:`orm_tutorial_literal_sql` - usage examples in the ORM tutorial zBfrom_statement accepts text(), select(), and union() objects only.N)r rK rV Z TextClauserW rR rS r� )r+ r� r' r' r- �from_statement/ s ��zQuery.from_statementc C sH | j dur t| �dd� }nt| dd� �}t|�dkr@|d S dS dS )a7 Return the first result of this ``Query`` or None if the result doesn't contain any row. first() applies a limit of one within the generated SQL, so that only one primary entity row is generated on the server side (note this may consist of multiple result rows if join-loaded collections are present). Calling :meth:`_query.Query.first` results in an execution of the underlying query. .. seealso:: :meth:`_query.Query.one` :meth:`_query.Query.one_or_none` Nr r )r� r� r[ �r+ �retr' r' r- �firstN s z Query.firstc C s: t | �}t|�}|dkr |d S |dkr,dS t�d��dS )a� Return at most one result or raise an exception. Returns ``None`` if the query selects no rows. Raises ``sqlalchemy.orm.exc.MultipleResultsFound`` if multiple object identities are returned, or if multiple rows are returned for a query that returns only scalar values as opposed to full identity-mapped entities. Calling :meth:`_query.Query.one_or_none` results in an execution of the underlying query. .. versionadded:: 1.0.9 Added :meth:`_query.Query.one_or_none` .. seealso:: :meth:`_query.Query.first` :meth:`_query.Query.one` r r Nz*Multiple rows were found for one_or_none())r� r[ �orm_exc�MultipleResultsFound)r+ r� r' r' r' r- � one_or_nonek s �zQuery.one_or_nonec C sb z | � � }W n: tjyF } z tjt�d�|d� W Y d}~n d}~0 0 |du rZt�d��|S dS )aB Return exactly one result or raise an exception. Raises ``sqlalchemy.orm.exc.NoResultFound`` if the query selects no rows. Raises ``sqlalchemy.orm.exc.MultipleResultsFound`` if multiple object identities are returned, or if multiple rows are returned for a query that returns only scalar values as opposed to full identity-mapped entities. Calling :meth:`.one` results in an execution of the underlying query. .. seealso:: :meth:`_query.Query.first` :meth:`_query.Query.one_or_none` z"Multiple rows were found for one()r� NzNo row was found for one())r� r� r� r r� � NoResultFound)r+ r� r r' r' r- �one� s �� z Query.onec C s> z"| � � }t|t�s|W S |d W S tjy8 Y dS 0 dS )a4 Return the first element of the first result or None if no rows present. If multiple rows are returned, raises MultipleResultsFound. >>> session.query(Item).scalar() <Item> >>> session.query(Item.id).scalar() 1 >>> session.query(Item.id).filter(Item.id < 0).scalar() None >>> session.query(Item.id, Item.name).scalar() 1 >>> session.query(func.count(Parent.id)).scalar() 20 This results in an execution of the underlying query. r N)r� rV rY r� r� r� r' r' r- �scalar� s z Query.scalarc C s0 | � � }d|j_| jr&| js&| j�� | �|�S r. )r� r� � use_labelsr r� r( �_execute_and_instances)r+ �contextr' r' r- �__iter__� s zQuery.__iter__c C sP | � � }z | jr | �|| jj�nd }W n tjy> d }Y n0 t|j�|��S r7 ) r� r( �_get_bind_argsZget_bindrR ZUnboundExecutionErrorrp r� �compile)r+ r� �bindr' r' r- �__str__� s �� z Query.__str__c K s. | j jf i |��}| jr*|jf i | j��}|S r7 )r( � connectionr� r@ )r+ �kw�connr' r' r- �_connection_from_session� s z Query._connection_from_sessionc C s2 | j || jdd�}|�|j| j�}t�|j||�S )NT)�close_with_result)r� r� �executer� r� r � instances�query)r+ � querycontextr� �resultr' r' r- r� � s �z Query._execute_and_instancesc C s | j ||dd�}|�|| j�S )NT)r; r� r� )r� r� r� )r+ r� r; r� r' r' r- � _execute_crud� s �zQuery._execute_crudc K s |f | � � |jd�|��S )N)r; r� )r� r� )r+ r� r5 r� r' r' r- r� � s ��zQuery._get_bind_argsc C s dd� dd� | j D �D �S )a Return metadata about the columns which would be returned by this :class:`_query.Query`. Format is a list of dictionaries:: user_alias = aliased(User, name='user2') q = sess.query(User, User.id, user_alias) # this expression: q.column_descriptions # would return: [ { 'name':'User', 'type':User, 'aliased':False, 'expr':User, 'entity': User }, { 'name':'id', 'type':Integer(), 'aliased':False, 'expr':User.id, 'entity': User }, { 'name':'user2', 'type':User, 'aliased':True, 'expr':user_alias, 'entity': user_alias } ] c S sJ g | ]B\}}|j |jt|d d�|j|jdur>|js>t|dd�ndd��qS )r: FNrF )r� ro r r� rF )� _label_namero rt r� r� r� )rq r6 Zinsp_entr' r' r- rt s � ���z-Query.column_descriptions.<locals>.<listcomp>c S s( g | ] }||j d ur t|j �nd f�qS r7 )r� r )rq Z_entr' r' r- rt * s �� �r� rs r' r' r- �column_descriptions� s ( ��zQuery.column_descriptionsc C s" |}|du rt | �}t�| ||�S )a Given a ResultProxy cursor as returned by connection.execute(), return an ORM result as an iterator. e.g.:: result = engine.execute("select * from users") for u in session.query(User).instances(result): print u N)r& r r� )r+ �cursorZ_Query__contextr� r' r' r- r� 7 s zQuery.instancesc C s t �| ||�S )ak Merge a result into this :class:`_query.Query` object's Session. Given an iterator returned by a :class:`_query.Query` of the same structure as this one, return an identical iterator of results, with all mapped instances merged into the session using :meth:`.Session.merge`. This is an optimized method which will merge all mapped instances, preserving the structure of the result rows and unmapped columns with less method overhead than that of calling :meth:`.Session.merge` explicitly for each value. The structure of the results is determined based on the column list of this :class:`_query.Query` - if these do not correspond, unchecked errors will occur. The 'load' argument is the same as that of :meth:`.Session.merge`. For an example of how :meth:`_query.Query.merge_result` is used, see the source code for the example :ref:`examples_caching`, where :meth:`_query.Query.merge_result` is used to efficiently restore state from a cache back into a target :class:`.Session`. )r � merge_result)r+ �iterator�loadr' r' r- r� G s zQuery.merge_resultc C s& | j | j| j| j| j| jp d | jd�S )N)r� r� r� r� r� rS rU )r� r� r� r r r� r rs r' r' r- � _select_argsc s �zQuery._select_argsc C s: | j }|�d�d up8|�d�d up8|�dd�p8|�dd�S )Nr� r� r� FrS )r� rj r> r' r' r- �_should_nest_selectableo s � � �z Query._should_nest_selectablec C s* t �| �d��t �d���� j�dg��S )a� A convenience method that turns a query into an EXISTS subquery of the form EXISTS (SELECT 1 FROM ... WHERE ...). e.g.:: q = session.query(User).filter(User.name == 'fred') session.query(q.exists()) Producing SQL similar to:: SELECT EXISTS ( SELECT 1 FROM users WHERE users.name = :name_1 ) AS anon_1 The EXISTS construct is usually used in the WHERE clause:: session.query(User.id).filter(q.exists()).scalar() Note that some databases such as SQL Server don't allow an EXISTS expression to be present in the columns clause of a SELECT. To select a simple boolean value based on the exists as a WHERE, use :func:`.literal`:: from sqlalchemy import literal session.query(literal(True)).filter(q.exists()).scalar() F�1r )r �existsr� r( �literal_columnr� r� Zwith_only_columnsrs r' r' r- r� y s # � ��z Query.existsc C s t j�t �d��}| �|��� S )a� Return a count of rows this the SQL formed by this :class:`Query` would return. This generates the SQL for this Query as follows:: SELECT count(1) AS count_1 FROM ( SELECT <rest of query follows...> ) AS anon_1 The above SQL returns a single row, which is the aggregate value of the count function; the :meth:`_query.Query.count` method then returns that single integer value. .. warning:: It is important to note that the value returned by count() is **not the same as the number of ORM objects that this Query would return from a method such as the .all() method**. The :class:`_query.Query` object, when asked to return full entities, will **deduplicate entries based on primary key**, meaning if the same primary key value would appear in the results more than once, only one object of that primary key would be present. This does not apply to a query that is against individual columns. .. seealso:: :ref:`faq_query_deduplicating` :ref:`orm_tutorial_query_returning` For fine grained control over specific columns to count, to skip the usage of a subquery or otherwise control of the FROM clause, or to use other aggregate functions, use :attr:`~sqlalchemy.sql.expression.func` expressions in conjunction with :meth:`~.Session.query`, i.e.:: from sqlalchemy import func # count User records, without # using a subquery. session.query(func.count(User.id)) # return count of user "id" grouped # by "name" session.query(func.count(User.id)).\ group_by(User.name) from sqlalchemy import distinct # count distinct "name" values session.query(func.count(distinct(User.name))) r7 )r �funcr� r� r r� )r+ �colr' r' r- r� � s 7z Query.count�evaluatec C s t j�| |�}|�� |jS )af Perform a bulk delete query. Deletes rows matched by this query from the database. E.g.:: sess.query(User).filter(User.age == 25).\ delete(synchronize_session=False) sess.query(User).filter(User.age == 25).\ delete(synchronize_session='evaluate') .. warning:: The :meth:`_query.Query.delete` method is a "bulk" operation, which bypasses ORM unit-of-work automation in favor of greater performance. **Please read all caveats and warnings below.** :param synchronize_session: chooses the strategy for the removal of matched objects from the session. Valid values are: ``False`` - don't synchronize the session. This option is the most efficient and is reliable once the session is expired, which typically occurs after a commit(), or explicitly using expire_all(). Before the expiration, objects may still remain in the session which were in fact deleted which can lead to confusing results if they are accessed via get() or already loaded collections. ``'fetch'`` - performs a select query before the delete to find objects that are matched by the delete query and need to be removed from the session. Matched objects are removed from the session. ``'evaluate'`` - Evaluate the query's criteria in Python straight on the objects in the session. If evaluation of the criteria isn't implemented, an error is raised. The expression evaluator currently doesn't account for differing string collations between the database and Python. :return: the count of rows matched as returned by the database's "row count" feature. .. warning:: **Additional Caveats for bulk query deletes** * This method does **not work for joined inheritance mappings**, since the **multiple table deletes are not supported by SQL** as well as that the **join condition of an inheritance mapper is not automatically rendered**. Care must be taken in any multiple-table delete to first accommodate via some other means how the related table will be deleted, as well as to explicitly include the joining condition between those tables, even in mappings where this is normally automatic. E.g. if a class ``Engineer`` subclasses ``Employee``, a DELETE against the ``Employee`` table would look like:: session.query(Engineer).\ filter(Engineer.id == Employee.id).\ filter(Employee.name == 'dilbert').\ delete() However the above SQL will not delete from the Engineer table, unless an ON DELETE CASCADE rule is established in the database to handle it. Short story, **do not use this method for joined inheritance mappings unless you have taken the additional steps to make this feasible**. * The polymorphic identity WHERE criteria is **not** included for single- or joined- table updates - this must be added **manually** even for single table inheritance. * The method does **not** offer in-Python cascading of relationships - it is assumed that ON DELETE CASCADE/SET NULL/etc. is configured for any foreign key references which require it, otherwise the database may emit an integrity violation if foreign key references are being enforced. After the DELETE, dependent objects in the :class:`.Session` which were impacted by an ON DELETE may not contain the current state, or may have been deleted. This issue is resolved once the :class:`.Session` is expired, which normally occurs upon :meth:`.Session.commit` or can be forced by using :meth:`.Session.expire_all`. Accessing an expired object whose row has been deleted will invoke a SELECT to locate the row; when the row is not found, an :class:`~sqlalchemy.orm.exc.ObjectDeletedError` is raised. * The ``'fetch'`` strategy results in an additional SELECT statement emitted and will significantly reduce performance. * The ``'evaluate'`` strategy performs a scan of all matching objects within the :class:`.Session`; if the contents of the :class:`.Session` are expired, such as via a proceeding :meth:`.Session.commit` call, **this will result in SELECT queries emitted for every matching object**. * The :meth:`.MapperEvents.before_delete` and :meth:`.MapperEvents.after_delete` events **are not invoked** from this method. Instead, the :meth:`.SessionEvents.after_bulk_delete` method is provided to act upon a mass DELETE of entity rows. .. seealso:: :meth:`_query.Query.update` :ref:`inserts_and_updates` - Core SQL tutorial )r Z BulkDelete�factory�exec_�rowcount)r+ �synchronize_sessionZ delete_opr' r' r- �delete� s xz Query.deletec C s( |pi }t j�| |||�}|�� |jS )a� Perform a bulk update query. Updates rows matched by this query in the database. E.g.:: sess.query(User).filter(User.age == 25).\ update({User.age: User.age - 10}, synchronize_session=False) sess.query(User).filter(User.age == 25).\ update({"age": User.age - 10}, synchronize_session='evaluate') .. warning:: The :meth:`_query.Query.update` method is a "bulk" operation, which bypasses ORM unit-of-work automation in favor of greater performance. **Please read all caveats and warnings below.** :param values: a dictionary with attributes names, or alternatively mapped attributes or SQL expressions, as keys, and literal values or sql expressions as values. If :ref:`parameter-ordered mode <updates_order_parameters>` is desired, the values can be passed as a list of 2-tuples; this requires that the :paramref:`~sqlalchemy.sql.expression.update.preserve_parameter_order` flag is passed to the :paramref:`.Query.update.update_args` dictionary as well. .. versionchanged:: 1.0.0 - string names in the values dictionary are now resolved against the mapped entity; previously, these strings were passed as literal column names with no mapper-level translation. :param synchronize_session: chooses the strategy to update the attributes on objects in the session. Valid values are: ``False`` - don't synchronize the session. This option is the most efficient and is reliable once the session is expired, which typically occurs after a commit(), or explicitly using expire_all(). Before the expiration, updated objects may still remain in the session with stale values on their attributes, which can lead to confusing results. ``'fetch'`` - performs a select query before the update to find objects that are matched by the update query. The updated attributes are expired on matched objects. ``'evaluate'`` - Evaluate the Query's criteria in Python straight on the objects in the session. If evaluation of the criteria isn't implemented, an exception is raised. The expression evaluator currently doesn't account for differing string collations between the database and Python. :param update_args: Optional dictionary, if present will be passed to the underlying :func:`_expression.update` construct as the ``**kw`` for the object. May be used to pass dialect-specific arguments such as ``mysql_limit``, as well as other special arguments such as :paramref:`~sqlalchemy.sql.expression.update.preserve_parameter_order`. .. versionadded:: 1.0.0 :return: the count of rows matched as returned by the database's "row count" feature. .. warning:: **Additional Caveats for bulk query updates** * The method does **not** offer in-Python cascading of relationships - it is assumed that ON UPDATE CASCADE is configured for any foreign key references which require it, otherwise the database may emit an integrity violation if foreign key references are being enforced. After the UPDATE, dependent objects in the :class:`.Session` which were impacted by an ON UPDATE CASCADE may not contain the current state; this issue is resolved once the :class:`.Session` is expired, which normally occurs upon :meth:`.Session.commit` or can be forced by using :meth:`.Session.expire_all`. * The ``'fetch'`` strategy results in an additional SELECT statement emitted and will significantly reduce performance. * The ``'evaluate'`` strategy performs a scan of all matching objects within the :class:`.Session`; if the contents of the :class:`.Session` are expired, such as via a proceeding :meth:`.Session.commit` call, **this will result in SELECT queries emitted for every matching object**. * The method supports multiple table updates, as detailed in :ref:`multi_table_updates`, and this behavior does extend to support updates of joined-inheritance and other multiple table mappings. However, the **join condition of an inheritance mapper is not automatically rendered**. Care must be taken in any multiple-table update to explicitly include the joining condition between those tables, even in mappings where this is normally automatic. E.g. if a class ``Engineer`` subclasses ``Employee``, an UPDATE of the ``Engineer`` local table using criteria against the ``Employee`` local table might look like:: session.query(Engineer).\ filter(Engineer.id == Employee.id).\ filter(Employee.name == 'dilbert').\ update({"engineer_type": "programmer"}) * The polymorphic identity WHERE criteria is **not** included for single- or joined- table updates - this must be added **manually**, even for single table inheritance. * The :meth:`.MapperEvents.before_update` and :meth:`.MapperEvents.after_update` events **are not invoked from this method**. Instead, the :meth:`.SessionEvents.after_bulk_update` method is provided to act upon a mass UPDATE of entity rows. .. seealso:: :meth:`_query.Query.delete` :ref:`inserts_and_updates` - Core SQL tutorial )r Z BulkUpdater� r� r� )r+ r! r� Z update_argsZ update_opr' r' r- r� Y s �z Query.updatec C s | j jr>| j jD ],}|| �}|d ur|| ur|} |jsd| _qt| �}|jd urT|S ||_| j|_| jD ]}|�| |� qh|j D ]$}|d }||g|dd � �R � q�|j r�t |j �|_ | j r�| �|� |js�| jr�t�d��n t�d��|j�r| j�r| �|�|_n | �|�|_|S )NFr r zyNo column-based properties specified for refresh operation. Use session.expire() to reload collections and related items.z4Query contains no columns with which to SELECT from.)�dispatchZbefore_compile�_bake_okr& r� r� r� r0 � setup_context�create_eager_joins� from_clauser� �fromsr � _adjust_for_single_inheritance�primary_columnsr� rR r� �multi_row_eager_loadersr� �_compound_eager_statement�_simple_statement)r+ r� r5 Z new_queryr� rF ZrecZstrategyr' r' r- r� � sB �� zQuery._compile_contextc C s, |j rt�|j|j �}n d |_ g }tj|j| |jf|j|j|j d�| j ��}|j |_ | j D ]}|j |� }q\| j r~|j| j � }|�� }| �� }t�||�|_tj|g|j |jd�}|j d ur�|j jd u r�|j |_ |}|j�� D ]}t�|||j�}q�|�|� |j �r |j|j�|j �� |j|j � |S )N�ra r� r� )r� ) r� r? � expand_column_list_from_order_byr� r �selectr� r� r� r� r� r8 r; r r rX r] r@ rL �secondary_columnsrG � eager_joinsr! Z splice_joinsZstop_onZ append_from�append_order_byZcopy_and_process�eager_order_by) r+ r� Zorder_by_col_expr�inner�hintrc r� r� Z eager_joinr' r' r- r� sX ��� � � � �� � z Query._compound_eager_statementc C s� |j s d |_ | jdu r6|j r6| jt�|j|j �7 _| jt|j�� �7 _t j |j|j |j f|j|j |j d�| j��}|j|_| jD ]}|j|� }q�| jr�|j| j� }|jr�|j|j� |S )NTr� )r� r� r� r? r� r� rY r� r! r r� r� r� r� r� r� r8 r; r r r� r� )r+ r� r� r� r' r' r- r� a s6 �� ��� zQuery._simple_statementc C s� t | j�� �}| jrN| j| jvrNt| j�}|jr8|j}nd}|�| j|fg�}|D ]X\}}|| jv rfqR|j j }|durR|r�|� |�}| � |dd�}t �t j�|j�|�|_qRdS )am Apply single-table-inheritance filtering. For all distinct single-table-inheritance mappers represented in the columns clause of this query, as well as the "select from entity", add criterion to the WHERE clause of the given QueryContext such that only the appropriate subtypes are selected from the total results. NF)r� r8 r! rQ r r: rC r� r� r; Z_single_table_criterion�traversero r �and_ZTrue_Z_ifnoner� )r+ r� rm r� rL rG Z single_critr' r' r- r� s* � � �z$Query._adjust_for_single_inheritance)N)N)N)TT)TT)NNNNN)NFF)NF)NN)N)NN)N)r7 )r7 )FFNFF)N)T)r� )r� N)T)�r � __module__� __qualname__�__doc__r� r� r� r� r� r� r� r� r r� r r r� r� r� r� � frozensetr r� r r� r r� r� r� rZ r� rQ r8 r� r^ r Z immutabledictr r� r� r� r0 r1 r8 r r{ r� �_path_registryr� r2 r� rw r. r* r4 r> rd rf rn rv r ry r| ro r� r� r� r r� r� r� r� r� r] r� r� r� r� r� r� r� r� r� r� r� r� r� r� rA r� r� r� r� r� r� r� r� r� r< r� rj r Z PASSIVE_OFFr� r� r r r� r r r r r r r r! Z_valuesr� r& r( Zpending_deprecationr) r- r/ r+ r6 r; r< r= r@ � deprecatedrD rJ r� r rR r� rS rU rV r� rX rY rZ r[ r\ r rc rm rh ry r� r� r� rn r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r' r' r' r- r% > s� % / - � ; � ! E\� 6 ? 7 < � � � : #( "' ' MhB # 0 r - $ ? * :| 6 I r% c @ s e Zd Zedd� �ZdS )rA c C s\ |dv r d S |dkr d}d}n2|dkr0d }}n |dkrBd}d}nt �d| ��t||d�S ) Nrz rE TFr� Z update_nowaitz"Unknown with_lockmode argument: %r)rE rF )rR rS rA )r+ rC rE rF r' r' r- rB � s �z LockmodeArg.parse_legacy_queryN)r r� r� � classmethodrB r' r' r' r- rA � s rA c @ s e Zd ZdZdd� Zdd� ZdS )r/ z:Represent an entity column returned within a Query result.c O sH | t u r>|d }t|tj�s*t|�r*t} nt|t�r:t} nt} t � | �S )Nr ) r/ rV r rs r r� �Bundle� _BundleEntityr �objectr� )r� r r? rF r' r' r- r� � s � z_QueryEntity.__new__c C s | j �| j �}| j�� |_|S r7 r� rW r' r' r- r� � s z_QueryEntity._cloneN)r r� r� r� r� r� r' r' r' r- r/ � s r/ c @ sx e Zd ZdZdd� ZdZdZdd� Zdd� Ze d d � �Z e d d � �Z d d� Z dd� Z dd� Zdd� Zdd� Zdd� ZdS )r� z mapper/class/AliasedClass entityc C s0 |j s | |_ |j�| � d|_|g| _|| _d S r. )r1 r0 rT r2 r, r� )r+ r� rF r' r' r- r. � s z_MapperEntity.__init__Tc C s` |j | _ || _|j| _|j| _|j| _|j| _|| _|jrF| jj | _ n | j j j | _ | jj | _d S r7 )r; rH rA r: Zwith_polymorphic_mappers�_with_polymorphicr� �_polymorphic_discriminatorr� r� r� r r r� r� �r+ rG rH r' r' r- rD � s z_MapperEntity.setup_entityc C sh | j rtd��|du r&|�| j� dS | j�||�\}}|| _|| _|| _|�| jt � || jj �� dS )z�Receive an update from a call to :meth:`_query.Query.with_polymorphic`. Note the newer style of using a free standing ``with_polymporphic()`` construct doesn't make use of this method. z6Can't use with_polymorphic() against an Aliased objectN) r: �NotImplementedErrorrf r; Z_with_polymorphic_argsr� r� rA r> r? r@ rB )r+ r� r� rA r� Zmappersra r' r' r- r� � s" � ��z"_MapperEntity.set_with_polymorphicc C s | j jS r7 )r; r rs r' r' r- ro s z_MapperEntity.typec C s | j S r7 )r� rs r' r' r- r� s z'_MapperEntity.entity_zero_or_selectablec C s t | j|�S r7 )r r� �r+ rF r' r' r- r� s z _MapperEntity.corresponds_toc C s |j �| � d S r7 )r0 rT )r+ r� �selr' r' r- r s z!_MapperEntity.adapt_to_selectablec C sP d }| j s"|jr(|j�| jd �}n| j}|rF|jr@|�|j�}qL|}n|j}|S r7 )r: r) rj r; rH r^ �wrap)r+ r� r� rL r� r' r' r- �_get_entity_clauses s z!_MapperEntity._get_entity_clausesc C s� | � ||�}|jr$|r$|�|j�}n |s.|j}|sL| jjrLt�| j| jj�}|j | u rd|j }|j }nd }}t j | j||| j|||| jd�}|| jfS )N)r� r� �polymorphic_discriminator)r� rL r� r; Z_requires_row_aliasingr? r@ rA rB r1 r� r� r Z_instance_processorr� r� r� )r+ r� r� r� rL r� r� Z _instancer' r' r- � row_processor0 s0 � � z_MapperEntity.row_processorc C s~ | � ||�}| j| jf7 _|jdu rR| jjrR| jj|_|rR|�t�|j��|_tj || j| | j ||j | j |j | jd� d S )NF)r< r� r� )r� r� rA r� r; Z adapt_listr r3 r Z_setup_entity_queryr� r� r� r� r� )r+ r� r� rL r' r' r- r� S s& ��z_MapperEntity.setup_contextc C s t | j�S r7 )rp r; rs r' r' r- r� n s z_MapperEntity.__str__N)r r� r� r� r. r� �use_id_for_hashrD r� r ro r� r� r r� r� r� r� r' r' r' r- r� � s ! #r� c @ s\ e Zd ZdZdZdZdZdZdd� ZdZ dZ dd� Z dd � Z e d d � �Zd d � Zdd� ZdS )r� aM A grouping of SQL expressions that are returned by a :class:`_query.Query` under one namespace. The :class:`.Bundle` essentially allows nesting of the tuple-based results returned by a column-oriented :class:`_query.Query` object. It also is extensible via simple subclassing, where the primary capability to override is that of how the set of expressions should be returned, allowing post-processing as well as custom return types, without involving ORM identity-mapped classes. .. versionadded:: 0.9.0 .. seealso:: :ref:`bundles` Fc O sJ | | _ | _|| _t� | _| _| j�dd� |D �� |�d| j�| _dS )aQ Construct a new :class:`.Bundle`. e.g.:: bn = Bundle("mybundle", MyClass.x, MyClass.y) for row in session.query(bn).filter( bn.c.x == 5).filter(bn.c.y == 4): print(row.mybundle.x, row.mybundle.y) :param name: name of the bundle. :param \*exprs: columns or SQL expressions comprising the bundle. :param single_entity=False: if True, rows for this :class:`.Bundle` can be returned as a "single entity" outside of any enclosing tuple in the same manner as a mapped entity. c s s | ]}t |d |j�|fV qdS )r� N)rt �_label)rq r� r' r' r- r� � s z"Bundle.__init__.<locals>.<genexpr>� single_entityN) r� r� �exprsr" r� r r� re r )r+ r� r r� r' r' r- r. � s �zBundle.__init__Nc C s | j �| j �}|j�| j� |S r7 )r� r� r� r� )r+ �clonedr' r' r- r� � s z Bundle._clonec C s t j| jddi�S )N�groupF)r Z ClauseListr rs r' r' r- r� � s zBundle.__clause_element__c C s | � � jS r7 )r� rQ rs r' r' r- rQ � s zBundle.clausesc C s | � � }||_|S )z<Provide a copy of this :class:`.Bundle` passing a new label.)r� r� )r+ r� r r' r' r- r� � s z Bundle.labelc s t �d|�� � �fdd�}|S )z�Produce the "row processing" function for this :class:`.Bundle`. May be overridden by subclasses. .. seealso:: :ref:`bundles` - includes an example of subclassing. r� c s �� fdd��D ��S )Nc s g | ] }|� ��qS r' r' )rq �proc��rowr' r- rt � r� z=Bundle.create_row_processor.<locals>.proc.<locals>.<listcomp>r' r �Z keyed_tuple�procsr r- r � s z)Bundle.create_row_processor.<locals>.proc)r Zlightweight_named_tuple)r+ r� r r� r r' r r- �create_row_processor� s zBundle.create_row_processor)r r� r� r� r r� rP r: r. r r� r� r� r rQ r� r r' r' r' r- r� r s r� c @ sr e Zd ZdZddd�Zedd� �Zedd� �Zed d � �Zd d � Z ed d� �Z dd� Z dd� Z dd� Z dd� ZdS )r� FTc C sn |j �| � | | _| _t|�| _|j| _g | _ |r`|jD ]$}t|t �rTt | |� q:t | |� q:| jj | _ d S r7 )r0 rT �bundler� ro r� r� r rV r� r� r r r� )r+ r� r �setup_entitiesr� r' r' r- r. � s z_BundleEntity.__init__c C s | j }|d ur|jS d S d S r7 )r� r; )r+ r� r' r' r- r; � s z_BundleEntity.mapperc C s g }| j D ]}|�|j� q |S r7 )r0 �extendr, )r+ r, r6 r' r' r- r, s z_BundleEntity.entitiesc C s& | j D ]}|j}|d ur| S qd S r7 )r0 r� �r+ r6 r� r' r' r- r� s z_BundleEntity.entity_zeroc C s dS rz r' r� r' r' r- r� s z _BundleEntity.corresponds_toc C s& | j D ]}|j}|d ur| S qd S r7 )r0 r� r r' r' r- r� s z'_BundleEntity.entity_zero_or_selectablec C s, t || jdd�}| jD ]}|�||� qd S )NF)r )r� r r0 r )r+ r� r� r� r6 r' r' r- r % s z!_BundleEntity.adapt_to_selectablec C s | j D ]}|�||� qd S r7 )r0 rD )r+ rG rH r6 r' r' r- rD . s z_BundleEntity.setup_entityc C s | j D ]}|�||� qd S r7 )r0 r� )r+ r� r� r6 r' r' r- r� 2 s z_BundleEntity.setup_contextc s: t � ��fdd�| jD �� \}}| j��||�}|| jfS )Nc s g | ]}|� �� ���qS r' )r� )rq r6 �r� r� r� r' r- rt 8 s �z/_BundleEntity.row_processor.<locals>.<listcomp>)�zipr0 r r r� )r+ r� r� r� r r� r r' r r- r� 6 s ��z_BundleEntity.row_processorN)T)r r� r� r� r. r r; r, r� r� r� r rD r� r� r' r' r' r- r� � s r� c @ sZ e Zd ZdZddd�ZdZedd� �Zdd � Zd d � Z d d � Z dd� Z dd� Z dd� Z dS )r z Column/expression based entity.Nc sB || _ || _d}d}t|tj�rJt�d� t�|�}|j| _ d}d}d }nVt|t j t j f�r�t|dd �}|d urtd}|j| _ |�� }d}t|t�r�t||� d S t|tj�s�t|d�r�|jD ] }||u r� q�t|||d� q�d S t�d|f ��n|�s t|dd �| _ d}|j | _}|j | _|j �sBt|d d��sB|� | j �}|j � | � || _ t!� | _"t#|j$�| _%t!| j%�� |�s�|| _&|�r�|g| _'|j(| _(n g | _'d | _(t!| j'�| _)n�d d � t*j+|dd �D �} t�,d d � | D ��| _'t!� fdd �| D ��| _)| j'�r| j'd | _&| j&j(| _(n(| jd u�r2| j| _&d | _(n d | _&d | _(d S )NTFz�Plain string expression passed to Query() should be explicitly declared using literal_column(); automatic coercion of this value will be removed in SQLAlchemy 1.4ru �_select_iterable)� namespacez<SQL expression, column, or mapped entity expected - got '%r'r� Z is_literalc S s g | ]}d |j v r|�qS �rg r} �rq r~ r' r' r- rt � s �z*_ColumnEntity.__init__.<locals>.<listcomp>)Zinclude_scalar_selectsc S s g | ]}d |j v r|j d �qS r r} r r' r' r- rt � s �c s, g | ]$}d |j v r� �|j�r|j d �qS r )ri � intersection� _from_objectsr �� actual_fromsr' r- rt � s �r )-r� r rV r rs Zwarn_deprecatedr r� r� r� r rw r rq rt r� Z_query_clause_elementr� r� Z ColumnElementrO r r rR r� ro Zhashabler� r� r� r0 rT r% r� r� r� r r r� r, r; Z_from_entitiesr? Zsurface_column_elementsZ unique_list) r+ r� r% r Zsearch_entitiesZ check_columnZ_entityr� �type_Z all_elementsr' r r- r. F s� � � �� ���� �� z_ColumnEntity.__init__Fc C s( | j d ur| j S | jr | jd S d S d S )Nr )r� r rs r' r' r- r� � s z'_ColumnEntity.entity_zero_or_selectablec C s. t ||�| j��}| j|_| j|_| j|_d S r7 )r Zcorresponding_columnr% r� r� r, )r+ r� r� r� r' r' r- r � s z!_ColumnEntity.adapt_to_selectablec C s8 d| j vr|j| _t| j��|jj�r4| j�|j� d S )NrA )r� rA r� r r r r� �addr� r' r' r- rD � s �z_ColumnEntity.setup_entityc C s< | j d u rdS t|�r || j u S t| j � o6|�| j �S d S rz )r� r r� r� r' r' r- r� � s � �z _ColumnEntity.corresponds_toc C sb d| f|j v r |j d| f }n|�| jdd�}|jr<|�� }|jrN|jj| }|�|�}|| jfS )N� fetch_columnFT) r ro r% ri � _deannotaterL r �_getterr� )r+ r� r� r� r% �getterr' r' r- r� � s z_ColumnEntity.row_processorc C sP |� | jdd�}|jr |�� }| jt| j�7 _|j�|� ||jd| f< d S )NFTr ) ro r% ri r r� rY r� rT r )r+ r� r� r% r' r' r- r� � s z_ColumnEntity.setup_contextc C s t | j�S r7 )rp r% rs r' r' r- r� s z_ColumnEntity.__str__)N)r r� r� r� r. r� r r� r rD r� r� r� r� r' r' r' r- r C s x r c @ s e Zd ZdZdd� ZdS )r& ) r� rL r� � for_updater� r( r r� �invoke_all_eagersr� r� r� r� r� r� r� �propagate_optionsr r� r� r� r� r� r� ZrunidZpartialsZpost_load_pathsr� c C s |j d ur@t|j tj�r6|j js6|j js6|j �� | _q^|j | _n d | _|j| _ |j | _ |j | _ d| _d | _d| _d | _|| _|j| _|j| _|j| _|j| _|j| _|j | _ g | _ g | _ g | _ i | _!g | _"t#dd� |j$D ��| _%|j&�'� | _(| j d u�r|j)| _*nd | _*d S )NFr' c s s | ]}|j r|V qd S r7 )Zpropagate_to_loadersrp r' r' r- r� F s z(QueryContext.__init__.<locals>.<genexpr>)+r� rV r rW Z_textualr� Z apply_labelsr� rZ r� r� r� r� r� r� rL r� r r� r( r r r� r� r r r� r� r� r� r� r� r� r� r� r� r1 r r0 r9 r r� r� )r+ r� r' r' r- r. % sH ��� � zQueryContext.__init__N)r r� r� � __slots__r. r' r' r' r- r& s r& c @ s e Zd Zdd� Zdd� ZdS )� AliasOptionc C s || _ dS )a" Return a :class:`.MapperOption` that will indicate to the :class:`_query.Query` that the main table has been aliased. This is a seldom-used option to suit the very rare case that :func:`.contains_eager` is being used in conjunction with a user-defined SELECT statement that aliases the parent table. E.g.:: # define an aliased UNION called 'ulist' ulist = users.select(users.c.user_id==7).\ union(users.select(users.c.user_id>7)).\ alias('ulist') # add on an eager load of "addresses" statement = ulist.outerjoin(addresses).\ select().apply_labels() # create query, indicating "ulist" will be an # alias for the main table, "addresses" # property should be eager loaded query = session.query(User).options( contains_alias(ulist), contains_eager(User.addresses)) # then get results via the statement results = query.from_statement(statement).all() :param alias: is the string name of an alias, or a :class:`_expression.Alias` object representing the alias. N)rX )r+ rX r' r' r- r. Q s !zAliasOption.__init__c C s8 t | jtj�r"|�� j�| j�}n| j}t�|�|_d S r7 ) rV rX r rs r� r= r? r@ r^ )r+ r� rX r' r' r- r2 t s zAliasOption.process_queryN)r r� r� r. r2 r' r' r' r- r" P s #r" N);r� � itertoolsr � r r r� r r r r �baser r r r r r Z path_registryr r r r r r r� r r r rR r r r r r r? r! Zsql.baser" Zsql.expressionr# Zsql.selectabler$ �__all__�rootr� Z_self_inspectsZ class_loggerr� r% rA r/ r� r� r� r r& Z MapperOptionr" r' r' r' r- �<module> s� #yW CK
| ver. 1.1 | |
.
| PHP 8.3.30 | Ð“ÐµÐ½ÐµÑ€Ð°Ñ†Ð¸Ñ Ñтраницы: 0 |
proxy
|
phpinfo
|
ÐаÑтройка