| Server IP : 192.158.238.246 / Your IP : 3.15.27.146 Web Server : LiteSpeed System : Linux uniform.iwebfusion.net 4.18.0-553.27.1.lve.1.el8.x86_64 #1 SMP Wed Nov 20 15:58:00 UTC 2024 x86_64 User : jenniferflocom ( 1321) PHP Version : 8.1.32 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : OFF | Pkexec : OFF Directory : /opt/alt/python37/lib64/python3.7/site-packages/sqlalchemy/orm/__pycache__/ |
Upload File : |
B
��4].� � @ sH 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* d#d$d%gZ+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/d0� d0e3�Z6G d1d2� d2e3�Z7G d3d$� d$e0�Z8G d4d5� d5ej9�Z:d6S )7a� The Query class and support.
Defines the :class:`.Query` class, the central
construct used by the ORM to construct database queries.
The :class:`.Query` class should not be confused with the
:class:`.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/Z0dZ1dZ2�ddd�Z3�ddd �Z4d
d � Z5d d
� Z6dd� Z7dd� Z8dd� Z9dd� Z:e;� dd� �Z<e;� dd� �Z=dd� Z>d d � Z?d d � Z@d d!� ZAeBd"d#� �ZCd$d%� ZDd&d'� ZEd(d)� ZF�dd*d+�ZGd,d-� ZHd.d/� ZId0d1� ZJ�dd2d3�ZK�dd4d5�ZLd6d7� ZMd8d9� ZNd:d;� ZO�dd<d=�ZPd>d?� ZQeBd@dA� �ZR�ddBdC�ZS�ddDdE�ZTdFdG� ZUdHdI� ZVeBdJdK� �ZWdLdM� ZXe;� dNdO� �ZYe;� dPdQ� �ZZdRdS� Z[e;� dTdU� �Z\e;� dVdW� �Z]eBdXdY� �Z^e;� dZd[� �Z_e;eM��dd\d]��Z`e;� d^d_� �Zad`da� Zbdecjddfdbdc�Ze�dddde�Zfe;� dfdg� �Zge;� dhdi� �Zhe;� djdk� �Zie;� dldm� �Zj�ddndo�Zke;� �ddpdq��Zle;� drds� �Zmdtdu� Zne;� dvdw� �Zoe;� dxdy� �Zpdzd{� ZqeqZrd|d}� Zse;� d~d� �Zte;� d�d�� �Zue#�vd�d�d�d�d�� �Zwd�d�� Zxd�d�� Zye;� d�d�� �Zzd�d�� Z{e;� �d d�d���Z|�d d�d��Z}d�d�� Z~e;� d�d�� �Ze;� e#��d�d��d�d�� ��Z�e;� �d d�d���Z�e;� d�d�� �Z�e;eNeO�d�d�� �Z�d�d�� Z�e;eNeO�d�d�� �Z�e;eNeO�d�d�� �Z�e;eNeO�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;eNeO�d�d�� �Z�d�d�� Z�d�d Z�d�dĄ Z�d�dƄ Z�d�dȄ Z�e;eN�d�dʄ �Z�e;eM�d�d̄ �Z�e;eM�d�d΄ �Z�d�dЄ Z�e;eN�d�d҄ �Z�e;eN�d�dԄ �Z�e;eN�d�dք �Z�e;eN�d�d �Z�e;� d�dڄ �Z�e;� d�d܄ �Z�d�dބ Z�e;eM�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�eBd�d�� �Z��d d�d��Z��d d�d��Z�eBd�d�� �Z�eBd�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# aL ORM-level SQL construction object.
:class:`.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` object, a copy of the former with additional
criteria and options associated with it.
:class:`.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` directly and
associating with a :class:`.Session` using the :meth:`.Query.with_session`
method.
For a full walkthrough of :class:`.Query` usage, see the
:ref:`ormtutorial_toplevel`.
FTN� c C s || _ i | _| �|� dS )a� Construct a :class:`.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`
will be associated. Optional; a :class:`.Query` can be associated
with a :class:`.Session` generatively via the
:meth:`.Query.with_session` method as well.
.. seealso::
:meth:`.Session.query`
:meth:`.Query.with_session`
N)�session�_polymorphic_adapters�
_set_entities)�self�entitiesr& r% r% �G/opt/alt/python37/lib64/python3.7/site-packages/sqlalchemy/orm/query.py�__init__� s zQuery.__init__c C sT |d kr t }g | _d | _d| _|dk rPx t�|�D ]}|| |� q2W | �| 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 �� | _ }x�|D ]�}x�|jD ]~}||kr�t|�}|jst|jjrt|jj| jkrn| � |jt
� |j |jj
�� d }n|jr�|j}nd }||f||< |j|| � q"W qW d 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* �dr4 �entity�ext_info�aliased_adapterr% r% r+ r2 � s(
z Query._set_entity_selectablesc C sB x<|j p |gD ],}|| j|< x |�� D ]}|| j|j< q&W qW d S )N)�_with_polymorphic_mappersr' �iterate_to_root� local_table)r) r8 �adapter�m2�mr% r% r+ r; � s
z(Query._mapper_loads_polymorphically_withc C s g }d }x�|D ]�}t |�}t|d�rX|js0|jrX|| _|rJ|jsJt�d��|�|j� q|j sjt�d��qt
|t j �r~|�
� }|r�|}|�|� qW t|�| _|r�t| j�dkr�t
|t j�r�| �� }t�| jd |�| _n2|�r t| j�dk�r t|d��r |j�r |j| _d S )Nr8 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_mapperr7 �_select_from_entity�sa_exc�
ArgumentError�appendr> �
is_selectable�
isinstancer �
SelectBase�alias�tuple� _from_obj�len�Alias�_Query__all_equivsr< r= �_from_obj_aliasr@ )r) �objZset_base_alias�faZselect_from_alias�from_obj�info�equivsr% r% r+ �_set_select_from� s>
zQuery._set_select_fromc C sD x>|j D ]4}| j�|d � x |�� D ]}| j�|jd � q$W qW d S )N)rF r' �poprG rH )r) r8 rJ rK r% r% r+ �_reset_polymorphic_adapter s z Query._reset_polymorphic_adapterc C sx d|j kr0|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_clauserS r �
FromClauserL re )r) �element�searchrU 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>8 s z)Query._adapt_col_list.<locals>.<listcomp>r% )r) �colsr% )r) r+ �_adapt_col_list6 s
zQuery._adapt_col_listc C s
|| _ d S )N)�lazy_loaded_from)r) �stater% r% r+ �_set_lazyload_from> s zQuery._set_lazyload_fromc C s
d| _ d S )NF)�_orm_only_adapt)r) r% r% r+ �_adapt_all_clausesB s zQuery._adapt_all_clausesc s� g � | j sd}|r8| jr8x | jD ]}� �||jf� q W | jrZ� �| jrL|nd| jjf� | jrp� �|| jf� � sx|S � fdd�}t� |i |�S )z\Adapt incoming clauses to transformations which
have been applied within this query.Fc sF d| j kpd| j k}x,� D ]$\}}|r*|r|| �}|d k r|S qW d S )NZ
_orm_adaptrd )rf )�elemZ is_orm_adaptZ _orm_onlyrI �e)�adaptersr% r+ �replacef s
z$Query._adapt_clause.<locals>.replace)
ru �_filter_aliasesrQ rz r[ �_orm_only_from_obj_aliasr' rk r Zreplacement_traverse)r) �clauseZ as_filterZorm_onlyr] rz r% )ry r+ rl F s
zQuery._adapt_clausec C s
| j d S )z Return the first QueryEntity.r )r. )r) r% r% r+ �_query_entity_zeros s zQuery._query_entity_zeroc C s | j d jS )z8return the Mapper associated with the first QueryEntity.r )r. r8 )r) r% r% r+ � _mapper_zerow s zQuery._mapper_zeroc C s | j dk r| j S | �� jS )z�Return the 'entity' (mapper or AliasedClass) associated
with the first QueryEntity, or alternatively the 'select from'
entity if specified.N)rN r~ � entity_zero)r) r% r% r+ � _entity_zero{ s zQuery._entity_zeroc c s$ x | j D ]}t|t�r|V qW d S )N)r. rS �
_MapperEntity)r) r4 r% r% r+ �_mapper_entities� s
zQuery._mapper_entitiesc C s | j �d| �� �S )N�_joinpoint_entity)�
_joinpointrg r� )r) r% r% r+ �_joinpoint_zero� s zQuery._joinpoint_zeroc C s( | � � }|d k r$t|�}|js$|jS d S )N)r� r �is_clause_elementr8 )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.)r. r/ rO �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.)rX r. rO r� r� )r) Z rationaler% r% r+ �_only_entity_zero� s
zQuery._only_entity_zeroc C s& i }x | j D ]}|�|jj� q W |S )N)r� �updater8 r? )r) r` r4 r% r% r+ Z __all_equivs� s zQuery.__all_equivsc C s | j dddd�S )Nrg F)�order_by�distinct)�_no_criterion_condition)r) r% r% r+ �_get_condition� s zQuery._get_conditionc C s | j dddd� d S )Nrg F)r� r� )�_no_criterion_assertion)r) r% r% r+ �_get_existing_condition� s z Query._get_existing_conditionc C sd | j s
d S | jd k sR| jd k sR| jsR| jd k sR| jd k sR| jsR|rH| jsR|r`| jr`t �
d| ��d S )Nz<Query.%s() being called on a Query with existing criterion. ) �_enable_assertions�
_criterion�
_statementrW �_limit�_offset� _group_by� _order_by� _distinctrO r� )r) �methr� r� r% r% r+ r� � s
z Query._no_criterion_assertionc C s6 | � |||� d| _d | _| _d | _ | _| _d S )Nr% F)r� rW r� r� r� 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 )Nz<Query.%s() being called on a Query with existing criterion. )r� r� rO r� r� )r) r� r% r% r+ �_no_clauseelement_condition� s z!Query._no_clauseelement_conditionc C s& | j s
d S | jd k r"t�d| ��d S )Nz[Query.%s() being called on a Query with an existing full statement - can't apply criterion.)r� r� rO r� )r) r� r% r% r+ �_no_statement_condition� s
z Query._no_statement_conditionc C s4 | j s
d S | jd k s | jd k r0t�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� rO r� )r) r� r% r% r+ �_no_limit_offset� s zQuery._no_limit_offsetc C s: |r
|| _ |r|| _|r || _|r,t|�| _|r6|| _| S )N)�_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 )N)� __class__�__new__�__dict__r6 )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 )aM return the full SELECT statement represented by
this :class:`.Query`, embedded within an :class:`.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:`.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` first to apply table-qualified labels
to all columns.
:param reduce_columns: if True, :meth:`.Select.reduce_columns` will
be called on the resulting :func:`.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_columnsrU )r) r� r� r� r� r% r% r+ �subquery s
zQuery.subqueryc C s | � d�jj||d�S )a* Return the full SELECT statement represented by this
:class:`.Query` represented as a common table expression (CTE).
Parameters and usage are the same as those of the
:meth:`.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:`.HasCTE.cte`
F)r� � recursive)r� r� �cte)r) r� r� r% r% r+ r� : s 7 z Query.ctec C s | � d�j�|�S )z�Return the full SELECT statement represented by this
:class:`.Query`, converted
to a scalar subquery with a label of the given name.
Analogous to :meth:`sqlalchemy.sql.expression.SelectBase.label`.
F)r� r� �label)r) r� r% r% r+ r� u s z Query.labelc C s | � d�j�� S )z�Return the full SELECT statement represented by this
:class:`.Query`, converted to a scalar subquery.
Analogous to :meth:`sqlalchemy.sql.expression.SelectBase.as_scalar`.
F)r� r� � as_scalar)r) r% r% r+ r� � s zQuery.as_scalarc C s | � � S )z�Return the :class:`.Select` object emitted by this :class:`.Query`.
Used for :func:`.inspect` compatibility, this is equivalent to::
query.enable_eagerloads(False).with_labels().statement
)�__clause_element__)r) r% r% r+ r> � s zQuery.selectablec C s | � d��� jS )NF)r� r� r� )r) 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,
specifically for single element queries. The default is False.
. .. versionadded:: 1.2.5
N)�_only_return_tuples)r) �valuer% r% r+ �only_return_tuples� s zQuery.only_return_tuplesc 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.yield_per`.
N)�_enable_eagerloads)r) r� 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().)rO 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.with_labels` method *only* applies
the output of :attr:`.Query.statement`, and *not* to any of
the result-row invoking systems of :class:`.Query` itself, e.g.
:meth:`.Query.first`, :meth:`.Query.all`, etc. To execute
a query using :meth:`.Query.with_labels`, invoke the
:attr:`.Query.statement` using :meth:`.Session.execute`::
result = session.execute(query.with_labels().statement)
TN)r� )r) 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% 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� )r) 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_path� s
zQuery._with_current_pathc C sJ | j st�d��| jd �� }|g| jdd� | _|j| |||d� dS )a� Load columns for inheriting classes.
:meth:`.Query.with_polymorphic` applies transformations
to the "main" mapped class represented by this :class:`.Query`.
The "main" mapped class here means the :class:`.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)r> �polymorphic_on)r/ rO r� r. r� �set_with_polymorphic)r) �cls_or_mappersr> r� rC r% r% r+ r9 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.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.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.enable_eagerloads`
T)Zstream_resultsZmax_row_bufferN)�
_yield_per�_execution_options�union)r) �countr% r% r+ � yield_per& s AzQuery.yield_perc C s | � |tj�S )a 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.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.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.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` must be constructed in this way,
i.e. against a single mapped entity,
with no additional filtering criterion. Loading
options via :meth:`~.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:`.relationship`, using a simple
foreign-key-to-primary-key criterion, will also use an
operation equivalent to :meth:`~.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:`.Table`
object's primary key columns, or if the
:paramref:`.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.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+ rg l s Sz Query.getc C s |j ||d�}t�| j||�S )ak 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` 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) r8 �primary_key_identityr� Zpassiverr �keyr% r% r+ �_identity_lookup� s 1
zQuery._identity_lookupc
s t � d�r� �� � | �d�}t� t�}|s4t�� �� t� �t|j�krft �
dd� dd� |jD �� ��|r�y t � fdd�|j
D ��� W n4 tk
r� t �
dd� d d� |j
D �� ��Y nX | j�s|j�s| jd k�r| j|� |d
�}|d k �r| �� t|j|j��sd S |S || � �S ) N�__composite_values__rg zmIncorrect 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% )rm �cr% r% r+ � <genexpr> s z"Query._get_impl.<locals>.<genexpr>c 3 s | ]}� |j V qd S )N)r� )rm �prop)r� r% r+ r� 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 )z'%s'N)r� )rm r� r% r% r+ r� s )r� )rL r� r� rS �dictr r1 rX Z primary_keyrO r� r �listZ_identity_key_props�KeyErrorr� Zalways_refresh�_for_update_argr� r� �
issubclassr� �class_)r) r� Z
db_load_fnr� r8 Zis_dict�instancer% )r� r+ r� � s@
zQuery._get_implc G sD x>|D ]6}|dkr$| j �dg�| _ q| j �t�t|���| _ qW dS )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:`.Select.correlate` after coercion to expression constructs.
The correlation arguments take effect in such cases
as when :meth:`.Query.from_self` is used, or when
a subquery as returned by :meth:`.Query.subquery` is
embedded in another :func:`~.expression.select` construct.
N)�
_correlater� r< Zsurface_selectablesr! )r) �args�sr% r% r+ � correlate/ 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+ � autoflushL s
zQuery.autoflushc C s
d| _ dS )a� Return a :class:`.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.
TN)r� )r) r% r% r+ r� X 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._invoke_all_eagers`.
N)�_invoke_all_eagers)r) r� r% r% r+ �_with_invoke_all_eagersf s z Query._with_invoke_all_eagersc C s� |rt |�}n| �� }|dkrpt|�}xH|jD ]"}t|tj�r.|j|jkr.|}P q.W t� d|jj
j |j j f ��| �
t|||j��S )a Add filtering criterion that relates the given instance
to a child object or collection, using its attribute state
as well as an established :func:`.relationship()`
configuration.
The method uses the :func:`.with_parent` function to generate
the clause, the result of which is passed to :meth:`.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` object's target mapper.
:param instance:
An instance which has some :func:`.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` itself.
Nz\Could not locate a property which relates instances of class '%s' to instances of class '%s')r r� r Ziterate_propertiesrS r ZRelationshipPropertyr8 rO r� r� �__name__r� �filterr rC )r) r� �propertyZ from_entityr� r8 r� r% r% r+ r q s
zQuery.with_parentc C s8 |dk rt ||�}t| j�| _t| |�}| �|g� dS )zIadd a mapped entity to the list of result columns
to be returned.N)r r� r. r� r2 )r) rC rU rK r% r% r+ �
add_entity� s
zQuery.add_entityc C s
|| _ dS )a� Return a :class:`.Query` that will use the given :class:`.Session`.
While the :class:`.Query` object is normally instantiated using the
:meth:`.Session.query` method, it is legal to build the :class:`.Query`
directly without necessarily using a :class:`.Session`. Such a
:class:`.Query` object, or any :class:`.Query` already associated
with a different :class:`.Session`, can produce a new :class:`.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 )a� return a Query that selects from this Query's
SELECT statement.
:meth:`.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.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.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.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.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.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.add_entity` above **before** we call
:meth:`.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� rN r( )r) r* �
fromclauser� r% r% r+ � from_self� s +
zQuery.from_selfc C s
|| _ d S )N)r� )r) �valr% r% r+ �_set_enable_single_crit} s z Query._set_enable_single_critc C s` xdD ]}| j �|d � qW | �|gd� d| _| j}g | _x |D ]}|�| | jd � qBW d S )N) r� r� r� r� r� r� � _joinpathr� r� �_having� _prefixes� _suffixesTFr )r� rb ra r| r. �adapt_to_selectablerW )r) r� �attrZ old_entitiesrx r% r% r+ r� � s
zQuery._from_selectablec G s6 |s t d�S | �� }|j|td� |js.d|_t |�S )z\Return an iterator yielding result tuples corresponding
to the given list of columnsr% )r3 �
)�iterr� r( �
_ColumnEntityr� )r) �columnsr� r% r% r+ �values� s z Query.valuesc C s, yt | �|��d S tk
r& dS X dS )zLReturn 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 )a) Return a new :class:`.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 sF t | j�| _t| j�}x|D ]}t| |� q W | �| j|d� � dS )zXAdd one or more column expressions to the list
of result columns to be returned.N)r� r. rX r r2 )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% r+ �
add_column� s
zQuery.add_columnc G s | j d|�� S )a> Return a new :class:`.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)F)�_options)r) r� r% r% r+ �options� s z
Query.optionsc G s | j d|�� S )NT)T)r
)r) r� r% r% r+ �_conditional_options� s zQuery._conditional_optionsc G sv | j �� | _ d| j kr"t� | j d< tt�|��}| j| | _|rZx0|D ]}|�| � qFW nx|D ]}|�| � q`W d S )NZ_unbound_load_dedupes) � _attributesr6 r� rV r Zflatten_iterator�
_with_optionsZprocess_query_conditionally�
process_query)r) Z conditionalr� �opts�optr% r% r+ r
� s
zQuery._optionsc C s || �S )a� Return a new :class:`.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`
objects. See the example at :ref:`hybrid_transformers`.
r% )r) �fnr% r% r+ �with_transformation s zQuery.with_transformation�*c C s, |dk rt |�j}| j|||ff7 _dS )a~ Add an indexing or other executional context
hint for the given entity or selectable to
this :class:`.Query`.
Functionality is passed straight through to
:meth:`~sqlalchemy.sql.expression.Select.with_hint`,
with the addition that ``selectable`` can be a
:class:`.Table`, :class:`.Alias`, or ORM entity / mapped class
/etc.
.. seealso::
:meth:`.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 r> � _with_hints)r) r> �text� dialect_namer% r% r+ � with_hint s
zQuery.with_hintc C s | � d||�S )a� add a statement hint to this :class:`.Select`.
This method is similar to :meth:`.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:`.Select.with_statement_hint`.
.. versionadded:: 1.0.0
.. seealso::
:meth:`.Query.with_hint`
N)r )r) r r r% r% r+ �with_statement_hint9 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.execution_options`
)r� )r) r% r% r+ �get_execution_optionsK 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:`.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.get_execution_options`
N)r� r� )r) �kwargsr% r% r+ �execution_optionsV s zQuery.execution_optionsz0.9z�The :meth:`.Query.with_lockmode` method is deprecated and will be removed in a future release. Please refer to :meth:`.Query.with_for_update`. c C s t �|�| _dS )a Return a new :class:`.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.with_for_update` - improved API for
specifying the ``FOR UPDATE`` clause.
N)� LockmodeArg�parse_legacy_queryr� )r) �moder% r% r+ �
with_lockmodeh s zQuery.with_lockmodec C s t |||||d�| _dS )a� return a new :class:`.Query` with the specified options for the
``FOR UPDATE`` clause.
The behavior of this method is identical to that of
:meth:`.SelectBase.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).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.with_for_update` supersedes
the :meth:`.Query.with_lockmode` method.
.. seealso::
:meth:`.GenerativeSelect.with_for_update` - Core level method with
full argument and behavioral description.
)�read�nowait�of� skip_locked� key_shareN)r r� )r) r$ r% r& r' r( r% r% r+ �with_for_update� s $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)rX r� rO rP r� r6 )r) r� r r% r% r+ r� � s z Query.paramsc G sL xFt |�D ]:}t�|�}| �|dd�}| jdk r>| j|@ | _q
|| _q
W dS )a apply the given filtering criterion to a copy
of this :class:`.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:`.text` construct.
.. seealso::
:meth:`.Query.filter_by` - filter on keyword expressions.
TN)r� r �_expression_literal_as_textrl r� )r) � criterionr% r% r+ r� � s
z Query.filterc s � fdd�|� � D �}� j|� S )a� apply the given filtering criterion to a copy
of this :class:`.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.join`.
.. seealso::
:meth:`.Query.filter` - filter on SQL expressions.
c s" g | ]\}}t � �� |�|k�qS r% )r
r� )rm r� r� )r) r% r+ ro s z#Query.filter_by.<locals>.<listcomp>)�itemsr� )r) r �clausesr% )r) r+ � filter_by� s
zQuery.filter_byc G sx t |�dkrB|d dkr,d| jkr(d| _dS |d dkrBd| _dS | �|�}| jdks`| jdkrh|| _n | j| | _dS )aZ apply one or more ORDER BY criterion to the query and return
the newly resulting ``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)rX r� r� rq )r) r+ r% r% r+ r� s
zQuery.order_byc G sd t |�dkr"|d dkr"d| _dS ttdd� |D �� �}| �|�}| jdkrT|| _n | j| | _dS )a� apply one or more GROUP BY criterion to the query and return
the newly resulting :class:`.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 )rm r� r% r% r+ ro ; s z"Query.group_by.<locals>.<listcomp>)rX r� r� r rq )r) r+ r% r% r+ �group_by( s
zQuery.group_byc C sX t �|�}|dk r(t|tj�s(t�d��| �|dd�}| jdk rN| j|@ | _n|| _dS )a apply a HAVING criterion to the query and return the
newly resulting :class:`.Query`.
:meth:`~.Query.having` is used in conjunction with
:meth:`~.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 r* rS r �
ClauseElementrO rP rl r� )r) r+ r% r% r+ �havingC s
z Query.havingc G s | � || gt|� � ��d�S )NF)r� r� r� )r) Zexpr_fnr� r% r% r+ �_set_opf s z
Query._set_opc G s | j tjf|�� 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` object will not render ORDER BY within
its SELECT statement.
)r2 r r� )r) r� r% r% r+ r� k s %z Query.unionc G s | j tjf|�� 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.
)r2 r � union_all)r) r� r% r% r+ r3 � s zQuery.union_allc G s | j tjf|�� 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.
)r2 r � intersect)r) r� r% r% r+ r4 � s zQuery.intersectc G s | j tjf|�� 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.
)r2 r �
intersect_all)r) r� r% r% r+ r5 � s zQuery.intersect_allc G s | j tjf|�� 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.
)r2 r �except_)r) r� r% r% r+ r6 � s z
Query.except_c G s | j tjf|�� 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.
)r2 r �
except_all)r) r� r% r% r+ r7 � s zQuery.except_allc O sb |� dd�|� dd�|� dd�|� dd�f\}}}}|rNtdd�t|�� ��| j|||||d�S ) a�* Create a SQL JOIN against this :class:`.Query` object's criterion
and apply generatively, returning the newly resulting :class:`.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.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.join` along ``User.addresses``
will result in SQL equivalent to::
SELECT user.* FROM user JOIN address ON user.id = address.user_id
In the above example we refer to ``User.addresses`` as passed to
:meth:`~.Query.join` as the *on clause*, that is, it indicates
how the "ON" portion of the JOIN should be constructed. For a
single-entity query such as the one above (i.e. we start by selecting
only from ``User`` and nothing else), the relationship can also be
specified by its string name::
q = session.query(User).join("addresses")
:meth:`~.Query.join` can also accommodate multiple
"on clause" arguments to produce a chain of joins, such as below
where a join across four related entities is constructed::
q = session.query(User).join("orders", "items", "keywords")
The above would be shorthand for three separate calls to
:meth:`~.Query.join`, each using an explicit attribute to indicate
the source entity::
q = session.query(User).\
join(User.orders).\
join(Order.items).\
join(Item.keywords)
**Joins to a Target Entity or Selectable**
A second form of :meth:`~.Query.join` allows any mapped entity
or core selectable construct as a target. In this usage,
:meth:`~.Query.join` will attempt
to create a JOIN along the natural foreign key relationship between
two entities::
q = session.query(User).join(Address)
The above calling form of :meth:`~.Query.join` will raise an error if
either there are no foreign keys between the two entities, or if
there are multiple foreign key linkages between them. In the
above calling form, :meth:`~.Query.join` is called upon to
create the "on clause" automatically for us. The target can
be any mapped entity or selectable, such as a :class:`.Table`::
q = session.query(User).join(addresses_table)
**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. Suppose for
example we wanted to join to ``Address`` twice, using
an alias the second time. We use :func:`~sqlalchemy.orm.aliased`
to create a distinct alias of ``Address``, and join
to it using the ``target, onclause`` form, so that the
alias can be specified explicitly as the target along with
the relationship to instruct how the ON clause should proceed::
a_alias = aliased(Address)
q = session.query(User).\
join(User.addresses).\
join(a_alias, User.addresses).\
filter(Address.email_address=='ed@foo.com').\
filter(a_alias.email_address=='ed@bar.com')
Where above, the generated SQL would be similar to::
SELECT user.* FROM user
JOIN address ON user.id = address.user_id
JOIN address AS address_1 ON user.id=address_1.user_id
WHERE address.email_address = :email_address_1
AND address_1.email_address = :email_address_2
The two-argument calling form of :meth:`~.Query.join`
also allows us to construct arbitrary joins with SQL-oriented
"on clause" expressions, not relying upon configured relationships
at all. Any SQL expression can be passed as the ON clause
when using the two-argument form, which should refer to the target
entity in some way as well as an applicable source entity::
q = session.query(User).join(Address, User.id==Address.user_id)
**Advanced Join Targeting and Adaption**
There is a lot of flexibility in what the "target" can be when using
:meth:`~.Query.join`. As noted previously, it also accepts
:class:`.Table` constructs and other selectables such as
:func:`.alias` and :func:`.select` constructs, with either the one
or two-argument forms::
addresses_q = select([Address.user_id]).\
where(Address.email_address.endswith("@bar.com")).\
alias()
q = session.query(User).\
join(addresses_q, addresses_q.c.user_id==User.id)
:meth:`~.Query.join` also features the ability to *adapt* a
:meth:`~sqlalchemy.orm.relationship` -driven ON clause to the target
selectable. Below we construct a JOIN from ``User`` to a subquery
against ``Address``, allowing the relationship denoted by
``User.addresses`` to *adapt* itself to the altered target::
address_subq = session.query(Address).\
filter(Address.email_address == 'ed@foo.com').\
subquery()
q = session.query(User).join(address_subq, User.addresses)
Producing SQL similar to::
SELECT user.* FROM user
JOIN (
SELECT address.id AS id,
address.user_id AS user_id,
address.email_address AS email_address
FROM address
WHERE address.email_address = :email_address_1
) AS anon_1 ON user.id = anon_1.user_id
The above form allows one to fall back onto an explicit ON
clause at any time::
q = session.query(User).\
join(address_subq, User.id==address_subq.c.user_id)
**Controlling what to Join From**
While :meth:`~.Query.join` exclusively deals with the "right"
side of the JOIN, we can also control the "left" side, in those
cases where it's needed, using :meth:`~.Query.select_from`.
Below we construct a query against ``Address`` but can still
make usage of ``User.addresses`` as our ON clause by instructing
the :class:`.Query` to select first from the ``User``
entity::
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
**Constructing Aliases Anonymously**
:meth:`~.Query.join` can construct anonymous aliases
using the ``aliased=True`` flag. This feature is useful
when a query is being joined algorithmically, such as
when querying self-referentially to an arbitrary depth::
q = session.query(Node).\
join("children", "children", aliased=True)
When ``aliased=True`` is used, the actual "alias" construct
is not explicitly available. To work with it, methods such as
:meth:`.Query.filter` will adapt the incoming entity to
the last join point::
q = session.query(Node).\
join("children", "children", aliased=True).\
filter(Node.name == 'grandchild 1')
When using automatic aliasing, the ``from_joinpoint=True``
argument can allow a multi-node join to be broken into
multiple calls to :meth:`~.Query.join`, so that
each path along the way can be further filtered::
q = session.query(Node).\
join("children", aliased=True).\
filter(Node.name='child 1').\
join("children", aliased=True, from_joinpoint=True).\
filter(Node.name == 'grandchild 1')
The filtering aliases above can then be reset back to the
original ``Node`` entity using :meth:`~.Query.reset_joinpoint`::
q = session.query(Node).\
join("children", "children", aliased=True).\
filter(Node.name == 'grandchild 1').\
reset_joinpoint().\
filter(Node.name == 'parent 1)
For an example of ``aliased=True``, see the distribution
example :ref:`examples_xmlpersistence` which illustrates
an XPath-like query system using algorithmic joins.
:param \*props: A collection of one or more join conditions,
each consisting of a relationship-bound attribute or string
relationship name representing an "on clause", or a single
target entity, or a tuple in the form of ``(target, onclause)``.
A special two-argument calling form of the form ``target, onclause``
is also accepted.
:param aliased=False: If True, indicate that the JOIN target should be
anonymously aliased. Subsequent calls to :meth:`~.Query.filter`
and similar will adapt the incoming criterion to the target
alias, until :meth:`~.Query.reset_joinpoint` is called.
:param isouter=False: If True, the join used will be a left outer join,
just as if the :meth:`.Query.outerjoin` method were called. This
flag is here to maintain consistency with the same flag as accepted
by :meth:`.FromClause.join` and other Core constructs.
.. versionadded:: 1.0.0
: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.
.. seealso::
:ref:`ormtutorial_joins` in the ORM tutorial.
:ref:`inheritance_toplevel` for details on how
:meth:`~.Query.join` is used for inheritance relationships.
:func:`.orm.join` - a standalone ORM-level join function,
used internally by :meth:`.Query.join`, which in previous
SQLAlchemy versions was the primary ORM-level joining interface.
r F�from_joinpoint�isouter�fullzunknown arguments: %sz, )� outerjoinr: �create_aliasesr8 )rb � TypeErrorr �sorted�_join)r) �propsr r r8 r9 r: r% r% r+ r � s w
z
Query.joinc O sV |� dd�|� dd�|� dd� }}}|rBtdd�t|�� ��| j|d|||d�S ) z�Create a left outer join against this ``Query`` object's criterion
and apply generatively, returning the newly resulting ``Query``.
Usage is the same as the ``join()`` method.
r Fr8 r: zunknown arguments: %sz, T)r; r: r< r8 )rb r= r r> r? )r) r@ r r r8 r: r% r% r+ r; � s
zQuery.outerjoinc C sJ || _ x8d|kr>|d \}}|�� }|||< ||f|d< |}qW || _d S )N�prev)r� r6 r� )r) �jp�frA r% r% r+ �_update_joinpoint� s
zQuery._update_joinpointc
C sf |s | � � t|�dkrLt|d tjttf�rLt|d ttjt j
f�rL|f}t � |�}�xt
|�D �]�\}}t|t�r�|\}} nd} t|t j
t jf�r�| | }
} n
|| }
} | dkr�t|
�} | js�t| d�s�t�d��t| t j
�r�t| dd�}
nd}
t| t j��rt| �� | �} nD|�rVt| t j
��rV| �� }t|�}t|dd�| jk�rVt|| j�} t| t j
��r@|
dk�r�|
�rz|
}
n| jj}
| j}| j � |d�}t|t ��r�|j � |��r�|j!}t|| j�} | j}t| t"j#��s�|} |�sH||
|jf}|| j$k�rH| j$| �%� }|| j$f|d< | �&|� |t|�d krbt �'d | � qbnd }}| �(||
| ||||� qbW dS )
z�consumes arguments from join() or outerjoin(), places them into a
consistent format with which to form the actual JOIN constructs.
r r r Nr8 z9Expected mapped entity or selectable/table as join targetZ_of_typerA z:Pathed join target %s has already been joined to; skipping))�_reset_joinpointrX rS r rh �typer �strr0 r �PropComparatorr r1 � enumeraterV � string_typesr rR rL rO rP �getattrr
r� �
_parententityr� r� rC r' rg r r8 ZisaZ
aliased_classr �QueryableAttributer� r6 rD �warn�_join_left_to_right)r) �keysr; r: r< r8 Zkeylist�idxZarg1Zarg2�right�onclause�r_infoZof_typeZjp0r_ �leftrU r� ZedgerB r% r% r+ r? � sz
z Query._joinc C s
| j �� | _ |dkr6|dks t�| �|||�\}}} n|dk sBt�| �|�\}} ||krn|snt�d||f ��| �|||||�\}
}}|dk r�| j| } | jd|� t | ||||d�f | j|d d� | _n6| dk r�| 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)r9 r: r ) r' r6 �AssertionError�"_join_determine_implicit_left_side� _join_place_explicit_left_siderO r� � _join_check_and_adapt_right_siderW �orm_joinr. r> ) r) rU rR rS r� r< r; r: �replace_from_obj_index�use_entity_indexrT Z left_clauser% r% r+ rO y s*
8zQuery._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�rLi }x`t | j�D ]R\} }
|
j
} | dkr�q�t | �} | |kr�q�t |
t �r�| | f||
j< q�d| f|| j< q�W t
|�� �}
t�|
|j|�}t|�dk�r ||
|d \}}n*t|�dk�r:t�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 z�Can't determine which FROM clause to join from, there are multiple FROMS which can join to this entity. Try adding an explicit ON clause to help resolve the ambiguity.zjDon't know how to join to %s; please use an ON clause to more clearly establish the left side of this joinzgNo entities to join from; please use select_from() to establish the left entity/selectable of this join)r rW r< Z find_left_clause_to_join_fromr> rX rO r� r. rI �entity_zero_or_selectablerS r� r� rP )r) rU rR rS rT r[ r\ �indexesZ potentialZ entity_indexr4 rC Zent_infoZ all_clausesr% r% r+ rW � sP
z(Query._join_determine_implicit_left_sidec C s� d }}t |�}| jrHt�| j|j�}t|�dkr<t�d��|rH|d }|dkr�| jr�t |d�r�x0t
| j�D ]"\}}t |t �rl|�
|�rl|}P qlW ||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 r8 )r rW r< Z#find_left_clause_that_matches_givenr> rX rO r� r. rL rI rS r� �corresponds_to)r) rU r[ r\ �l_infor^ rQ r4 r% r% r+ rX &
s$
z$Query._join_place_explicit_left_sidec C sx t |�}t |�}d}|svt|dd�} | rv| js<t| jtj�rvx8| jpJ|jgD ]&}
t �
|j|
�rLt �
|
|j�rLd}P qLW |s~|s�|j|jkr�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��sXt � d| j| jjf ��t| tj��rr| �� } d}
t| | �}n|�r�t � d ��| �o�| �o�| j�r�t| jtj��p�|}|
�s�|�s�|�r�t|dd
�}d}
|
�r| �s�t�t || j d �}|f| j | _ |�s| � | |� t|tj ��r4| �|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.
Fr8 NTz*Can't join table/selectable '%s' to itselfr7 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� rA r� )$r rK r9 rS r: r ZJoinrW r> r< Zselectables_overlaprO r� �
common_parentr8 rL �_join_entitiesr� Z _is_lateralrl Zis_derived_from� descriptionrT rU r Z _with_polymorphic_selectablerY rV r r? r{ r; r0 rD r� r� )r) rU rR rS r� r< r` rT �overlapZ right_mapperr^ Zright_selectableZright_is_aliasedZ need_adapterZaliased_entityrI r% r% r+ rY h
s�
z&Query._join_check_and_adapt_right_sidec C s | j | _d| _d S )Nr% )r� r� r{ )r) r% r% r+ rE s zQuery._reset_joinpointc C s | � � dS )aS Return a new :class:`.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.join`
method. See the example in :meth:`~.Query.join` for how
this is used.
N)rE )r) r% r% r+ �reset_joinpoint s zQuery.reset_joinpointc G s | � |d� dS )aP Set the FROM clause of this :class:`.Query` explicitly.
:meth:`.Query.select_from` is often used in conjunction with
:meth:`.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.join`, when no
joinpoint is otherwise established - usually, the default "join
point" is the leftmost entity in the :class:`~.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:`.Mapper` objects
as well as core :class:`.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.join`
:meth:`.Query.select_entity_from`
FN)ra )r) r^ r% r% r+ � select_from s .zQuery.select_fromc C s | � |gd� dS )a� Set the FROM clause of this :class:`.Query` to a
core selectable, applying it as a replacement FROM clause
for corresponding mapped entities.
The :meth:`.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.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.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.select_entity_from` method is similar to the
:meth:`.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.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.select_entity_from` method,
we can make use of the :func:`.text` construct. However, the
:func:`.text` construct needs to be aligned with the columns of our
entity, which is achieved by making use of the
:meth:`.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.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.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:`.Table`, this view has no
relationship to the :class:`.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.select_entity_from`
method now accepts an :func:`.aliased` object as an alternative
to a :class:`.FromClause` object.
:param from_obj: a :class:`.FromClause` object that will replace
the FROM clause of this :class:`.Query`. It also may be an instance
of :func:`.aliased`.
.. seealso::
:meth:`.Query.select_from`
TN)ra )r) r^ r% r% r+ �select_entity_fromL s fzQuery.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 k r�t|�d d |j� S t|�S n,|dkr�t| �d S t| ||d � �d S d S )Nr ���r )rS �slicer Z decode_slice�intr� �step)r) �item�start�stoprk �resr% r% r+ � __getitem__� s
zQuery.__getitem__c C sx |dk r,|dk r,| j pd| | _ || | _n8|dkrD|dk rD|| _n |dk rd|dkrd| j p\d| | _ | j dkrtd| _ dS )a� Computes the "slice" of the :class:`.Query` represented by
the given indices and returns the resulting :class:`.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.limit`
:meth:`.Query.offset`
Nr )r� r� )r) rm rn r% r% r+ ri � s
z Query.slicec C s
|| _ dS )zZApply a ``LIMIT`` to the query and return the newly resulting
``Query``.
N)r� )r) �limitr% r% r+ rq � s z Query.limitc C s
|| _ dS )z\Apply an ``OFFSET`` to the query and return the newly resulting
``Query``.
N)r� )r) �offsetr% r% r+ rr 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
``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`, however, so would not affect results.
The columns are passed through when using the
:attr:`.Query.statement` accessor, however.
:param \*expr: optional column expressions. When present,
the PostgreSQL dialect will render a ``DISTINCT ON (<expressions>)``
construct.
TN)r� rq rS 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
``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:`.HasPrefixes.prefix_with`
N)r� )r) �prefixesr% r% r+ � prefix_with+ s zQuery.prefix_withc G s | j r| j |7 _ n|| _ dS )aG Apply the suffix to the query and return the newly resulting
``Query``.
:param \*suffixes: optional suffixes, typically strings,
not using any commas.
.. versionadded:: 1.0.0
.. seealso::
:meth:`.Query.prefix_with`
:meth:`.HasSuffixes.suffix_with`
N)r� )r) �suffixesr% r% r+ � suffix_withJ s zQuery.suffix_withc C s t | �S )z�Return the results represented by this ``Query`` as a list.
This results in an execution of the underlying query.
)r� )r) r% r% r+ �all` s z Query.allc C s0 t �|�}t|t jt jf�s&t�d��|| _dS )a% 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`.
.. seealso::
:ref:`orm_tutorial_literal_sql` - usage examples in the
ORM tutorial
zBfrom_statement accepts text(), select(), and union() objects only.N)r r* rS Z
TextClauserT rO rP r� )r) r� r% r% r+ �from_statementh s
zQuery.from_statementc C sH | j dk r t| �dd� }nt| dd� �}t|�dkr@|d S dS dS )a 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.first` results in an execution of the underlying
query.
.. seealso::
:meth:`.Query.one`
:meth:`.Query.one_or_none`
Nr r )r� r� rX )r) �retr% r% r+ �first� s
z Query.firstc C s: t | �}t|�}|dkr |d S |dkr,dS t�d��dS )ax 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.one_or_none` results in an execution of the
underlying query.
.. versionadded:: 1.0.9
Added :meth:`.Query.one_or_none`
.. seealso::
:meth:`.Query.first`
:meth:`.Query.one`
r r Nz*Multiple rows were found for one_or_none())r� rX �orm_exc�MultipleResultsFound)r) rz r
r% r% r+ � one_or_none� s zQuery.one_or_nonec C sH y | � � }W n tjk
r, t�d��Y nX |dkr@t�d��|S dS )a6 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.first`
:meth:`.Query.one_or_none`
z"Multiple rows were found for one()NzNo row was found for one())r~ r| r} �
NoResultFound)r) rz r% r% r+ �one� s
z Query.onec C s: y | � � }t|t�s|S |d S tjk
r4 dS X 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� rS rV r| r )r) rz r% r% r+ �scalar� s
z Query.scalarc C s0 | � � }d|j_| jr&| js&| j�� | �|�S )NT)r� r� �
use_labelsr� r� r& �_execute_and_instances)r) �contextr% r% r+ �__iter__� s
zQuery.__iter__c C sR | � � }y | jr | �|| jj�nd }W n tjk
r@ d }Y nX t|j�|��S )N) r� r& �_get_bind_argsZget_bindrO ZUnboundExecutionErrorrG r� �compile)r) r� �bindr% r% r+ �__str__
s
z
Query.__str__c K s& | j jf |�}| jr"|jf | j�}|S )N)r& Z
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)r8 r} r� )r� r� r� )r) r� r8 r� r% r% r+ �
_execute_crud
s zQuery._execute_crudc K s |f | � � |jd�|��S )N)r8 r} )r� r� )r) r� r 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`.
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|jdk r>|js>t|dd�ndd��qS )r7 FNrC )r� rF r rs rC )� _label_namerF rK rs r� r� )rm r4 Zinsp_entr% r% r+ ro S
s
z-Query.column_descriptions.<locals>.<listcomp>c S s( g | ] }||j d k r t|j �nd f�qS )N)r� r )rm Z_entr% r% r+ ro ^
s )r. )r) r% r% r+ �column_descriptions*
s ) zQuery.column_descriptionsc C s" |}|dkrt | �}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) ZcursorZ_Query__contextr� r% r% r+ r� j
s
zQuery.instancesc C s t �| ||�S )a? Merge a result into this :class:`.Query` object's Session.
Given an iterator returned by a :class:`.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` - 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.merge_result` is used, see
the source code for the example :ref:`examples_caching`, where
:meth:`~.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� z
s zQuery.merge_resultc C s& | j | j| j| j| j| jp d | jd�S )N)rq rr r� rt rv r/ r1 )r� r� r� r� r� r� r� )r) r% r% r+ � _select_args�
s zQuery._select_argsc C s. | j }|�d�d k p,|�d�d k p,|�dd�S )Nrq rr r� F)r� rg )r) r r% r% r+ �_should_nest_selectable�
s z Query._should_nest_selectablec C s$ t �| �d��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 r� r� Zwith_only_columns)r) r% r% r+ r� �
s #
z Query.existsc C s t j�t �d��}| �|��� S )a Return a count of rows this 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
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)))
r )r �funcr� �literal_columnr� r� )r) �colr% r% r+ r� �
s "z Query.count�evaluatec C s t j�| |�}|�� |jS )aO 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.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.update`
:ref:`inserts_and_updates` - Core SQL tutorial
)r Z
BulkDelete�factory�exec_�rowcount)r) �synchronize_sessionZ delete_opr% r% r+ �delete�
s wz Query.deletec C s( |pi }t j�| |||�}|�� |jS )au 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.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:`.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.delete`
:ref:`inserts_and_updates` - Core SQL tutorial
)r Z
BulkUpdater� r� r� )r) r r� Z update_argsZ update_opr% r% r+ r� s s z Query.updatec C s | j jr.x$| j jD ]}|| �}|d k r|} qW t| �}|jd k rD|S ||_| j|_x| jD ]}|�| |� qZW x&|jD ] }|d }||dd � � qvW |j r�t
|j �|_ | j r�| �
|� |js�| jr�t�d��n
t�d��|jr�| jr�| �|�|_n | �|�|_|S )Nr 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_compiler$ r� r� r� r. �
setup_context�create_eager_joins� from_clauser� �fromsr� � _adjust_for_single_inheritance�primary_columnsr� rO r� �multi_row_eager_loadersr� �_compound_eager_statement�_simple_statement)r) r� r Z new_queryr� rC ZrecZstrategyr% r% r+ r� � s:
zQuery._compile_contextc C s4 |j rt�|j|j �}n
d |_ g }tj|j| |jf|j|j|j d�| j ��}|j
|_
x| j D ]}|j |� }q^W | j
r�|j| j
� }|�� }| �� }t�||�|_tj|g|j |jd�}|j
d k r�|j
jd kr�|j
|_
|}x"|j�� D ]}t�|||j�}q�W |�|� |j �r$|j|j�|j �� |j|j � |S )N)r^ r� r� )r� ) r� r< � expand_column_list_from_order_byr� r �selectr� r� r� r� r� r r r� r� rU rZ r= rI �secondary_columnsr& � eager_joinsr Z splice_joinsZstop_onZ append_from�append_order_byZcopy_and_process�eager_order_by) r) r� Zorder_by_col_expr�inner�hintr` r� r� Z
eager_joinr% r% r+ r� . sF
z Query._compound_eager_statementc C s� |j s d |_ | jdkr6|j r6| jt�|j|j �7 _| jt|j�� �7 _t j
|j|j |j f|j|j
|j d�| j��}|j|_x| jD ]}|j|� }q�W | jr�|j| j� }|jr�|j|j� |S )NT)r^ r� r� )r� r� r� r< r� r� rV r� r r r� r� r� r� r� r� r r r� r� r� r� )r) r� r� r� r% r% r+ r� w s,
zQuery._simple_statementc C s� t | j�� �}| jrN| j| jkrNt| j�}|jr8|j}nd}|�| j|fg�}x`|D ]X\}}|| jkrhqT|j j
}|dk rT|r�|� |�}| � |dd�}t
�t
j�|j�|�|_qTW dS )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� r5 r rN r r7 r@ r� rb r8 Z_single_table_criterionZtraverserl r �and_ZTrue_Z_ifnoner� )r) r� rj r� rI rD 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)r )r )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� rW rb rN r5 r{ r[ r Z
immutabledictr� r� r� r� r r r r� ru r| �_path_registryr� r0 rr r, r( r2 r; ra rc rk rq r rt rv rl r~ r r� r� r� r� r� r� r� rZ r� r� r� r� r� r� r� r� r� r� r� r� r� r� r> r� r� r� r� r� r� r� r� r9 r� rg 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
r r r r r Z
deprecatedr# r) r� r� r. r� r/ r1 r2 r� r3 r4 r5 r6 r7 r r; rD r? rO rW rX rY rE re rf rg rp ri rq rr r� ru rw rx ry 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� /-
;
FY 0 8 6 6
%# #' M`B $
0h * # @
* %{ 4 I c @ s e Zd Zedd� �ZdS )r c C s\ |dkr d S |dkr d}d}n2|dkr0d }}n |dkrBd}d}nt �d| ��t||d�S ) N)NFr$ TFr� Z
update_nowaitz"Unknown with_lockmode argument: %r)r$ r% )rO rP r )r) r" r$ r% r% r% r+ r! � s
z LockmodeArg.parse_legacy_queryN)r� r� r� � classmethodr! r% r% r% r+ r � s r c @ s e Zd ZdZdd� Zdd� ZdS )r- z:represent an entity column returned within a Query result.c O sH | t kr>|d }t|tj�s*t|�r*t} nt|t�r:t} nt} t �
| �S )Nr ) r- rS r rJ r
r� �Bundle�
_BundleEntityr �objectr� )r� r� r rC r% r% r+ r� � s
z_QueryEntity.__new__c C s | j �| j �}| j�� |_|S )N)r� r� r� r6 )r) r� 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 )NT)r/ r. rQ r0 r* rs )r) r� rC 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 )N)r8 rE r> r7 Zwith_polymorphic_mappers�_with_polymorphicr� �_polymorphic_discriminatorr� r� r� r� r� r� r� )r) rD rE r% r% r+ rA � s z_MapperEntity.setup_entityc C sh | j rtd��|dkr&|�| j� dS | j�||�\}}|| _|| _|| _|�| jt �
|| jj �� dS )z�Receive an update from a call to 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) r7 �NotImplementedErrorrc r8 Z_with_polymorphic_argsr� r� r> r; r< r= r? )r) r� r� r> r� Zmappersr^ r% r% r+ r� s
z"_MapperEntity.set_with_polymorphicc C s | j jS )N)r8 r� )r) r% r% r+ rF # s z_MapperEntity.typec C s | j S )N)r� )r) r% r% r+ r] ' s z'_MapperEntity.entity_zero_or_selectablec C s t | j|�S )N)r r� )r) rC r% r% r+ r_ + s z _MapperEntity.corresponds_toc C s |j �| � d S )N)r. rQ )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 )N)r7 r' rg r8 rE r[ �wrap)r) r� r� rI rz r% r% r+ �_get_entity_clauses1 s z!_MapperEntity._get_entity_clausesc
C s� | � ||�}|jr$|r$|�|j�}n
|s.|j}|sL| jjrLt�| j| jj�}|j | krd|j
}|j }nd }}t j
| j||| j|||| jd�}|| jfS )N)r� r� �polymorphic_discriminator)r� rI r� r8 Z_requires_row_aliasingr< r= r> r? r/ r� r� r Z_instance_processorr� r� r� )r) r� r� r� rI r� r� Z _instancer% r% r+ �
row_processorE s,
z_MapperEntity.row_processorc C s~ | � ||�}| j| jf7 _|jdkrR| jjrR| jj|_|rR|�t�|j��|_tj || j| | j
||j | j |j
| jd� d S )NF)r9 r� r� )r� r� r> r� r8 Z
adapt_listr r1 r Z_setup_entity_queryr� r� r� r� r� )r) r� r� rI r% r% r+ r� h s"
z_MapperEntity.setup_contextc C s
t | j�S )N)rG r8 )r) r% r% r+ r� � s z_MapperEntity.__str__N)r� r� r� r� r, �supports_single_entity�use_id_for_hashrA r� r� rF 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� a> A grouping of SQL expressions that are returned by a :class:`.Query`
under one namespace.
The :class:`.Bundle` essentially allows nesting of the tuple-based
results returned by a column-oriented :class:`.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)rK �_label)rm r� r% r% r+ r� � s z"Bundle.__init__.<locals>.<genexpr>�
single_entityN) r� r� �exprsr r� r r� rb r� )r) r� r� r� r% r% r+ r, � s zBundle.__init__Nc C s | j �| j �}|j�| j� |S )N)r� r� r� r� )r) �clonedr% r% r+ r� � s z
Bundle._clonec C s t j| jddi�S )N�groupF)r Z
ClauseListr� )r) r% r% r+ r� � s zBundle.__clause_element__c C s
| � � jS )N)r� r- )r) r% r% r+ r- � 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% )rm �proc)�rowr% r+ ro � s z=Bundle.create_row_processor.<locals>.proc.<locals>.<listcomp>r% )r� )� keyed_tuple�procs)r� r+ r� � s z)Bundle.create_row_processor.<locals>.proc)r Zlightweight_named_tuple)r) r� r� r� r� r% )r� r� r+ �create_row_processor� s
zBundle.create_row_processor)r� r� r� r� r� r� rM r7 r, r r� r� r� r� 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 sr |j �| � | | _| _t|�| _|j| _g | _ |rdx.|jD ]$}t|t �rVt
| |� q<t | |� q<W | jj | _
d S )N)r. rQ �bundlers rF r� r� r� rS r� r� r r� r� )r) r� r� �setup_entitiesrs r% r% r+ r, s
z_BundleEntity.__init__c C s | j }|d k r|jS d S d S )N)r� r8 )r) r� r% r% r+ r8 s z_BundleEntity.mapperc C s$ g }x| j D ]}|�|j� q W |S )N)r. �extendr* )r) r* r4 r% r% r+ r* s z_BundleEntity.entitiesc C s* x$| j D ]}|j}|d k r|S qW d S d S )N)r. r� )r) r4 r� r% r% r+ r� " s
z_BundleEntity.entity_zeroc C s dS )NFr% )r) rC r% r% r+ r_ + s z _BundleEntity.corresponds_toc C s* x$| j D ]}|j}|d k r|S qW d S d S )N)r. r] )r) r4 r� r% r% r+ r] 0 s
z'_BundleEntity.entity_zero_or_selectablec C s0 t || jdd�}x| jD ]}|�||� qW d S )NF)r� )r� r� r. r� )r) r� r� r� r4 r% r% r+ r� 9 s z!_BundleEntity.adapt_to_selectablec C s x| j D ]}|�||� qW d S )N)r. rA )r) rD rE r4 r% r% r+ rA B s z_BundleEntity.setup_entityc C s x| j D ]}|�||� qW d S )N)r. r� )r) r� r� r4 r% r% r+ r� F s z_BundleEntity.setup_contextc s: t � ��fdd�| jD �� \}}| j��||�}|| jfS )Nc s g | ]}|� �� ���qS r% )r� )rm r4 )r� r� r� r% r+ ro M s z/_BundleEntity.row_processor.<locals>.<listcomp>)�zipr. r� r� r� )r) r� r� r� r� r� r� r% )r� r� r� r+ r� J s
z_BundleEntity.row_processorN)T)r� r� r� r� r, r� r8 r* r� r_ r] r� rA 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
s4 || _ || _d}d}t|tj�r@t�|�}|j| _d}d}d }nVt|t j
t j f�r�t
|dd �}|d k rjd}|j| _|�� }d}t|t�r�t||� d S t|tj�s�t|d�r�x*|jD ] }||kr�P t|||d� q�W d S t�d|f ��n|�st
|dd �| _d}|j | _}|j | _|j�s:t
|dd��s:|� | j�}|j � | � || _ t � | _!t |j"� | _#� |�s�|| _$|�r�|g| _%|j&| _&n g | _%d | _&t | j%�| _'n�d d
� t(j)|dd �D �} t�*d d
� | D ��| _%t � fd
d
�| D ��| _'| j%�r| j%d | _$| j$j&| _&n(| jd k �r$| j| _$d | _&n d | _$d | _&d S )NTFrL �_select_iterable)� namespacez<SQL expression, column, or mapped entity expected - got '%r'r� Z
is_literalc S s g | ]}d |j kr|�qS )rd )rf )rm rw r% r% r+ ro � s z*_ColumnEntity.__init__.<locals>.<listcomp>)Zinclude_scalar_selectsc S s g | ]}d |j kr|j d �qS )rd )rf )rm rw r% r% r+ ro � s c s, g | ]$}d |j kr� �|j�r|j d �qS )rd )rf � intersection�
_from_objects)rm rw )� actual_fromsr% r+ ro � s
r )+rs r� rS r rJ r r� r� r� r rM r rH rK r� Z_query_clause_elementr� r� Z
ColumnElementrL r� r rO r� rF Zhashabler� r� r� r. rQ r r� r� r� r� r� r* r8 Z_from_entitiesr< Zsurface_column_elementsZ unique_list)
r) r� r r� Zsearch_entitiesZ check_columnZ_entityr� �type_Z all_elementsr% )r� r+ r, Z s�
z_ColumnEntity.__init__Fc C s, | j d k r| j S | jr$t| j�d S d S d S )Nr )r� r� r� )r) r% r% r+ r] � s
z'_ColumnEntity.entity_zero_or_selectablec C s. t ||�| j��}| j|_| j|_| j|_d S )N)r Zcorresponding_columnr r� r� r* )r) r� r� r� r% r% r+ r� � s z!_ColumnEntity.adapt_to_selectablec C s4 d| j kr|j| _| j�|jj�r0| j�|j� d S )Nr> )r� r> r� r� r� r� �add)r) rD rE r% r% r+ rA � s
z_ColumnEntity.setup_entityc C s< | j d krdS t|�r || j kS t| j � o6|�| j �S d S )NF)r� r ra )r) rC r% r% r+ r_ � s
z _ColumnEntity.corresponds_toc C sb d| f|j kr |j d| f }n|�| jdd�}|jr<|�� }|jrN|jj| }|�|�}|| jfS )N� fetch_columnFT) r rl r rf � _deannotaterI r Z_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� ) rl r rf r� r� rV r� rQ r )r) r� r� r r% r% r+ r� � s z_ColumnEntity.setup_contextc C s
t | j�S )N)rG r )r) r% r% r+ r� s z_ColumnEntity.__str__)N)r� r� r� r� r, r� r� r] r� rA r_ r� r� r� r% r% r% r+ r W s
q
r c @ s e Zd ZdZdd� ZdS )r$ ) r� rI 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 k r@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 k �r|j)| _*nd | _*d S )NFr% c s s | ]}|j r|V qd S )N)Zpropagate_to_loaders)rm rn r% r% r+ r� R s z(QueryContext.__init__.<locals>.<genexpr>)+r� rS r rT Z_textualr� Z apply_labelsr� rW r� r� r� r� r� r� rI r� r� r� r& r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r r� r r6 r r� r� )r) r� r% r% r+ r, 0 s@
zQueryContext.__init__N)r� r� r� � __slots__r, r% r% r% r+ r$ s c @ s e Zd Zdd� Zdd� ZdS )� AliasOptionc C s
|| _ dS )a! Return a :class:`.MapperOption` that will indicate to the :class:`.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:`~.sql.expression.Alias` object representing
the alias.
N)rU )r) rU r% r% r+ r, \ s !zAliasOption.__init__c C s8 t | jtj�r"|�� j�| j�}n| j}t�|�|_d S )N) rS rU r rJ r r: r< r= r[ )r) r� rU r% r% r+ r s zAliasOption.process_queryN)r� r� r� r, r r% r% r% r+ r� [ 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 rZ r r r rO r r r r r r< r Zsql.baser Zsql.expressionr! Zsql.selectabler" �__all__�rootr� Z_self_inspectsZ class_loggerr� r# r r- r� r� r� r r$ Z MapperOptionr� r% r% r% r+ �<module> s�
"xW :K