U x^j@sdZddlmZddlmZddlmZddlmZddlmZddlmZddlmZdd lm Z dd lm Z dd lm Z dd lm Z dd lm Z ddlmZddlmZddlmZddlmZddlmZddlmZddlmZddlmZejr ddlmZneZGdddeZGdddeZGdddeZeeeehZeee eee hZddZd d!Z d"d#Z!e d$d%Z"d&d'Z#d(d)Z$d*d+Z%d,d-Z&e d.d/Z'e d0d1Z(e d2d3Z)e d4d5Z*d6d7Z+d8d9Z,e dd;d<Z-e dd=d>Z.e dd?d@Z/e ddAdBZ0e ddDdEZ1e ddFdGZ2e dHdIZ3e dJdKZ4dLdMZ5dNdOZ6dPdQZ7dRdSZ8e ddTdUZ9e ddVdWZ:e ddXdYZ;e ddZd[Ze d`daZ?e dbdcZ@dddeZAe dfdgZBe dhdiZCdjdkZDdldmZEdndoZFdpdqZGdrdsZHdtduZIdvdwZJdxdyZKdzd{ZLd|d}ZMd~dZNddZOe e%e&eefZPddZQee ee e ee eiZRddZSeTeEeegUeegZVeVTeeJeKgZWejXdddZYejXdddZZejXdddZ[e!de"de6de7dedeJdeKdededede dedededeEdeDde?de@de/de0de-de.de3de4de)de*dedede'de(deBdeCdede dede de1de2de5de de%de&dededeAdeFdeGde+de#de$deYdeZeZe[e[i5Z\ddZ]d:S)z*Defines operators used in SQL expressions.)add)and_)contains)eq)ge)getitem)gt)inv)le)lshift)lt)mod)mul)ne)neg)or_)rshift)sub)truediv)util)divc@sPeZdZdZdZddZddZddZdd d ZdddZ ddZ ddZ d S) OperatorsaBase of comparison and logical operators. Implements base methods :meth:`~sqlalchemy.sql.operators.Operators.operate` and :meth:`~sqlalchemy.sql.operators.Operators.reverse_operate`, as well as :meth:`~sqlalchemy.sql.operators.Operators.__and__`, :meth:`~sqlalchemy.sql.operators.Operators.__or__`, :meth:`~sqlalchemy.sql.operators.Operators.__invert__`. Usually is used via its most common subclass :class:`.ColumnOperators`. cCs |t|S)a.Implement the ``&`` operator. When used with SQL expressions, results in an AND operation, equivalent to :func:`~.expression.and_`, that is:: a & b is equivalent to:: from sqlalchemy import and_ and_(a, b) Care should be taken when using ``&`` regarding operator precedence; the ``&`` operator has the highest precedence. The operands should be enclosed in parenthesis if they contain further sub expressions:: (a == 2) & (b == 4) )operaterselfotherrr@/tmp/pip-install-dq5v43_d/SQLAlchemy/sqlalchemy/sql/operators.py__and__;szOperators.__and__cCs |t|S)a*Implement the ``|`` operator. When used with SQL expressions, results in an OR operation, equivalent to :func:`~.expression.or_`, that is:: a | b is equivalent to:: from sqlalchemy import or_ or_(a, b) Care should be taken when using ``|`` regarding operator precedence; the ``|`` operator has the highest precedence. The operands should be enclosed in parenthesis if they contain further sub expressions:: (a == 2) | (b == 4) )rrrrrr__or__SszOperators.__or__cCs |tS)aImplement the ``~`` operator. When used with SQL expressions, results in a NOT operation, equivalent to :func:`~.expression.not_`, that is:: ~a is equivalent to:: from sqlalchemy import not_ not_(a) )rr rrrr __invert__kszOperators.__invert__rFNcs t||||fdd}|S)a!produce a generic operator function. e.g.:: somecolumn.op("*")(5) produces:: somecolumn * 5 This function can also be used to make bitwise operators explicit. For example:: somecolumn.op('&')(0xff) is a bitwise AND of the value in ``somecolumn``. :param operator: a string which will be output as the infix operator between this element and the expression passed to the generated function. :param precedence: precedence to apply to the operator, when parenthesizing expressions. A lower number will cause the expression to be parenthesized when applied against another operator with higher precedence. The default value of ``0`` is lower than all operators except for the comma (``,``) and ``AS`` operators. A value of 100 will be higher or equal to all operators, and -100 will be lower than or equal to all operators. :param is_comparison: if True, the operator will be considered as a "comparison" operator, that is which evaluates to a boolean true/false value, like ``==``, ``>``, etc. This flag should be set so that ORM relationships can establish that the operator is a comparison operator when used in a custom join condition. .. versionadded:: 0.9.2 - added the :paramref:`.Operators.op.is_comparison` flag. :param return_type: a :class:`.TypeEngine` class or object that will force the return type of an expression produced by this operator to be of that type. By default, operators that specify :paramref:`.Operators.op.is_comparison` will resolve to :class:`.Boolean`, and those that do not will be of the same type as the left-hand operand. .. versionadded:: 1.2.0b3 - added the :paramref:`.Operators.op.return_type` argument. .. seealso:: :ref:`types_operators` :ref:`relationship_custom_operator` cs |SNr)roperatorrrragainstszOperators.op..against) custom_op)ropstring precedence is_comparison return_typer&rr$rop|s:z Operators.opcCs|j||ddS)a+Return a custom boolean operator. This method is shorthand for calling :meth:`.Operators.op` and passing the :paramref:`.Operators.op.is_comparison` flag with True. .. versionadded:: 1.2.0b3 .. seealso:: :meth:`.Operators.op` T)r)r*r,)rr(r)rrrbool_opszOperators.bool_opcOstt|dS)a3Operate on an argument. This is the lowest level of operation, raises :class:`NotImplementedError` by default. Overriding this on a subclass can allow common behavior to be applied to all operations. For example, overriding :class:`.ColumnOperators` to apply ``func.lower()`` to the left and right side:: class MyComparator(ColumnOperators): def operate(self, op, other): return op(func.lower(self), func.lower(other)) :param op: Operator callable. :param \*other: the 'other' side of the operation. Will be a single scalar for most operations. :param \**kwargs: modifiers. These may be passed by special operators such as :meth:`ColumnOperators.contains`. NNotImplementedErrorstrrr,rkwargsrrrrszOperators.operatecKstt|dS)zXReverse operate on an argument. Usage is the same as :meth:`operate`. Nr/r2rrrreverse_operateszOperators.reverse_operate)rFN)r) __name__ __module__ __qualname____doc__ __slots__rr r"r,r.rr4rrrrr*s A rc@s6eZdZdZdZd ddZddZd d Zd d ZdS)r'aRepresent a 'custom' operator. :class:`.custom_op` is normally instantiated when the :meth:`.Operators.op` or :meth:`.Operators.bool_op` methods are used to create a custom operator callable. The class can also be used directly when programmatically constructing expressions. E.g. to represent the "factorial" operation:: from sqlalchemy.sql import UnaryExpression from sqlalchemy.sql import operators from sqlalchemy import Numeric unary = UnaryExpression(table.c.somecolumn, modifier=operators.custom_op("!"), type_=Numeric) .. seealso:: :meth:`.Operators.op` :meth:`.Operators.bool_op` rFNcCs6||_||_||_||_||_|r,||nd|_dSr#)r(r)r*natural_self_precedenteager_groupingZ _to_instancer+)rr(r)r*r+r:r;rrr__init__ s zcustom_op.__init__cCst|to|j|jkSr#) isinstancer'r(rrrr__eq__szcustom_op.__eq__cCst|Sr#)idr!rrr__hash__"szcustom_op.__hash__cKs|j||f|Sr#)r)rleftrightkwrrr__call__%szcustom_op.__call__)rFNFF)r5r6r7r8r<r>r@rDrrrrr's r'c@seZdZdZdZdZddZddZej Z dd Z d d Z d d Z ddZ ddZddZddZddZddZddZddZddZdcd d!Zddd"d#Zd$d%Zd&d'Zded(d)Zdfd*d+Zd,d-Zd.d/Zd0d1Zd2d3Zd4d5Z d6d7Z!d8d9Z"d:d;Z#dd?Z%d@dAZ&dBdCZ'dDdEZ(dFdGZ)dHdIZ*dJdKZ+dgdMdNZ,dOdPZ-dQdRZ.dSdTZ/dUdVZ0dWdXZ1dYdZZ2d[d\Z3d]d^Z4d_d`Z5dadbZ6dS)hColumnOperatorsaDefines boolean, comparison, and other operators for :class:`.ColumnElement` expressions. By default, all methods call down to :meth:`.operate` or :meth:`.reverse_operate`, passing in the appropriate operator function from the Python builtin ``operator`` module or a SQLAlchemy-specific operator function from :mod:`sqlalchemy.expression.operators`. For example the ``__eq__`` function:: def __eq__(self, other): return self.operate(operators.eq, other) Where ``operators.eq`` is essentially:: def eq(a, b): return a == b The core column expression unit :class:`.ColumnElement` overrides :meth:`.Operators.operate` and others to return further :class:`.ColumnElement` constructs, so that the ``==`` operation above is replaced by a clause construct. .. seealso:: :ref:`types_operators` :attr:`.TypeEngine.comparator_factory` :class:`.ColumnOperators` :class:`.PropComparator` rNcCs |t|S)zdImplement the ``<`` operator. In a column context, produces the clause ``a < b``. )rr rrrr__lt__TszColumnOperators.__lt__cCs |t|S)zfImplement the ``<=`` operator. In a column context, produces the clause ``a <= b``. )rr rrrr__le__\szColumnOperators.__le__cCs |t|S)zImplement the ``==`` operator. In a column context, produces the clause ``a = b``. If the target is ``None``, produces ``a IS NULL``. )rrrrrrr>fszColumnOperators.__eq__cCs |t|S)zImplement the ``!=`` operator. In a column context, produces the clause ``a != b``. If the target is ``None``, produces ``a IS NOT NULL``. )rrrrrr__ne__oszColumnOperators.__ne__cCs |t|S)zImplement the ``IS DISTINCT FROM`` operator. Renders "a IS DISTINCT FROM b" on most platforms; on some such as SQLite may render "a IS NOT b". .. versionadded:: 1.1 )ris_distinct_fromrrrrrIxs z ColumnOperators.is_distinct_fromcCs |t|S)zImplement the ``IS NOT DISTINCT FROM`` operator. Renders "a IS NOT DISTINCT FROM b" on most platforms; on some such as SQLite may render "a IS b". .. versionadded:: 1.1 )risnot_distinct_fromrrrrrJs z#ColumnOperators.isnot_distinct_fromcCs |t|S)zdImplement the ``>`` operator. In a column context, produces the clause ``a > b``. )rrrrrr__gt__szColumnOperators.__gt__cCs |t|S)zfImplement the ``>=`` operator. In a column context, produces the clause ``a >= b``. )rrrrrr__ge__szColumnOperators.__ge__cCs |tS)zaImplement the ``-`` operator. In a column context, produces the clause ``-a``. )rrr!rrr__neg__szColumnOperators.__neg__cCs |t|Sr#)rrrrrr __contains__szColumnOperators.__contains__cCs |t|S)zImplement the [] operator. This can be used by some database-specific types such as PostgreSQL ARRAY and HSTORE. )rr)rindexrrr __getitem__szColumnOperators.__getitem__cCs |t|S)zimplement the << operator. Not used by SQLAlchemy core, this is provided for custom operator systems which want to use << as an extension point. )rr rrrr __lshift__szColumnOperators.__lshift__cCs |t|S)zimplement the >> operator. Not used by SQLAlchemy core, this is provided for custom operator systems which want to use >> as an extension point. )rrrrrr __rshift__szColumnOperators.__rshift__cCs |t|S)zImplement the 'concat' operator. In a column context, produces the clause ``a || b``, or uses the ``concat()`` operator on MySQL. )r concat_oprrrrconcatszColumnOperators.concatcCs|jt||dS)aImplement the ``like`` operator. In a column context, produces the expression:: a LIKE other E.g.:: stmt = select([sometable]).\ where(sometable.c.column.like("%foobar%")) :param other: expression to be compared :param escape: optional escape character, renders the ``ESCAPE`` keyword, e.g.:: somecolumn.like("foo/%bar", escape="/") .. seealso:: :meth:`.ColumnOperators.ilike` escape)rlike_oprrrVrrrlikeszColumnOperators.likecCs|jt||dS)aImplement the ``ilike`` operator, e.g. case insensitive LIKE. In a column context, produces an expression either of the form:: lower(a) LIKE lower(other) Or on backends that support the ILIKE operator:: a ILIKE other E.g.:: stmt = select([sometable]).\ where(sometable.c.column.ilike("%foobar%")) :param other: expression to be compared :param escape: optional escape character, renders the ``ESCAPE`` keyword, e.g.:: somecolumn.ilike("foo/%bar", escape="/") .. seealso:: :meth:`.ColumnOperators.like` rU)rilike_oprXrrrilikeszColumnOperators.ilikecCs |t|S)a Implement the ``in`` operator. In a column context, produces the clause ``column IN ``. The given parameter ``other`` may be: * A list of literal values, e.g.:: stmt.where(column.in_([1, 2, 3])) In this calling form, the list of items is converted to a set of bound parameters the same length as the list given:: WHERE COL IN (?, ?, ?) * A list of tuples may be provided if the comparison is against a :func:`.tuple_` containing multiple expressions:: from sqlalchemy import tuple_ stmt.where(tuple_(col1, col2).in_([(1, 10), (2, 20), (3, 30)])) * An empty list, e.g.:: stmt.where(column.in_([])) In this calling form, the expression renders a "false" expression, e.g.:: WHERE 1 != 1 This "false" expression has historically had different behaviors in older SQLAlchemy versions, see :paramref:`.create_engine.empty_in_strategy` for behavioral options. .. versionchanged:: 1.2 simplified the behavior of "empty in" expressions * A bound parameter, e.g. :func:`.bindparam`, may be used if it includes the :paramref:`.bindparam.expanding` flag:: stmt.where(column.in_(bindparam('value', expanding=True))) In this calling form, the expression renders a special non-SQL placeholder expression that looks like:: WHERE COL IN ([EXPANDING_value]) This placeholder expression is intercepted at statement execution time to be converted into the variable number of bound parameter form illustrated earlier. If the statement were executed as:: connection.execute(stmt, {"value": [1, 2, 3]}) The database would be passed a bound parameter for each value:: WHERE COL IN (?, ?, ?) .. versionadded:: 1.2 added "expanding" bound parameters If an empty list is passed, a special "empty list" expression, which is specific to the database in use, is rendered. On SQLite this would be:: WHERE COL IN (SELECT 1 FROM (SELECT 1) WHERE 1!=1) .. versionadded:: 1.3 "expanding" bound parameters now support empty lists * a :func:`.select` construct, which is usually a correlated scalar select:: stmt.where( column.in_( select([othertable.c.y]). where(table.c.x == othertable.c.x) ) ) In this calling form, :meth:`.ColumnOperators.in_` renders as given:: WHERE COL IN (SELECT othertable.y FROM othertable WHERE othertable.x = table.x) :param other: a list of literals, a :func:`.select` construct, or a :func:`.bindparam` construct that includes the :paramref:`.bindparam.expanding` flag set to True. )rin_oprrrrin_sYzColumnOperators.in_cCs |t|S)aimplement the ``NOT IN`` operator. This is equivalent to using negation with :meth:`.ColumnOperators.in_`, i.e. ``~x.in_(y)``. In the case that ``other`` is an empty sequence, the compiler produces an "empty not in" expression. This defaults to the expression "1 = 1" to produce true in all cases. The :paramref:`.create_engine.empty_in_strategy` may be used to alter this behavior. .. versionchanged:: 1.2 The :meth:`.ColumnOperators.in_` and :meth:`.ColumnOperators.notin_` operators now produce a "static" expression for an empty IN sequence by default. .. seealso:: :meth:`.ColumnOperators.in_` )rnotin_oprrrrnotin_^szColumnOperators.notin_cCs|jt||dS)zimplement the ``NOT LIKE`` operator. This is equivalent to using negation with :meth:`.ColumnOperators.like`, i.e. ``~x.like(y)``. .. seealso:: :meth:`.ColumnOperators.like` rU)r notlike_oprXrrrnotlikevs zColumnOperators.notlikecCs|jt||dS)zimplement the ``NOT ILIKE`` operator. This is equivalent to using negation with :meth:`.ColumnOperators.ilike`, i.e. ``~x.ilike(y)``. .. seealso:: :meth:`.ColumnOperators.ilike` rU)r notilike_oprXrrrnotilikes zColumnOperators.notilikecCs |t|S)aVImplement the ``IS`` operator. Normally, ``IS`` is generated automatically when comparing to a value of ``None``, which resolves to ``NULL``. However, explicit usage of ``IS`` may be desirable if comparing to boolean values on certain platforms. .. seealso:: :meth:`.ColumnOperators.isnot` )ris_rrrrrds zColumnOperators.is_cCs |t|S)a`Implement the ``IS NOT`` operator. Normally, ``IS NOT`` is generated automatically when comparing to a value of ``None``, which resolves to ``NULL``. However, explicit usage of ``IS NOT`` may be desirable if comparing to boolean values on certain platforms. .. seealso:: :meth:`.ColumnOperators.is_` )risnotrrrrres zColumnOperators.isnotcKs|jt|f|S)a Implement the ``startswith`` operator. Produces a LIKE expression that tests against a match for the start of a string value:: column LIKE || '%' E.g.:: stmt = select([sometable]).\ where(sometable.c.column.startswith("foobar")) Since the operator uses ``LIKE``, wildcard characters ``"%"`` and ``"_"`` that are present inside the expression will behave like wildcards as well. For literal string values, the :paramref:`.ColumnOperators.startswith.autoescape` flag may be set to ``True`` to apply escaping to occurrences of these characters within the string value so that they match as themselves and not as wildcard characters. Alternatively, the :paramref:`.ColumnOperators.startswith.escape` parameter will establish a given character as an escape character which can be of use when the target expression is not a literal string. :param other: expression to be compared. This is usually a plain string value, but can also be an arbitrary SQL expression. LIKE wildcard characters ``%`` and ``_`` are not escaped by default unless the :paramref:`.ColumnOperators.startswith.autoescape` flag is set to True. :param autoescape: boolean; when True, establishes an escape character within the LIKE expression, then applies it to all occurrences of ``"%"``, ``"_"`` and the escape character itself within the comparison value, which is assumed to be a literal string and not a SQL expression. An expression such as:: somecolumn.startswith("foo%bar", autoescape=True) Will render as:: somecolumn LIKE :param || '%' ESCAPE '/' With the value of :param as ``"foo/%bar"``. .. versionadded:: 1.2 .. versionchanged:: 1.2.0 The :paramref:`.ColumnOperators.startswith.autoescape` parameter is now a simple boolean rather than a character; the escape character itself is also escaped, and defaults to a forwards slash, which itself can be customized using the :paramref:`.ColumnOperators.startswith.escape` parameter. :param escape: a character which when given will render with the ``ESCAPE`` keyword to establish that character as the escape character. This character can then be placed preceding occurrences of ``%`` and ``_`` to allow them to act as themselves and not wildcard characters. An expression such as:: somecolumn.startswith("foo/%bar", escape="^") Will render as:: somecolumn LIKE :param || '%' ESCAPE '^' The parameter may also be combined with :paramref:`.ColumnOperators.startswith.autoescape`:: somecolumn.startswith("foo%bar^bat", escape="^", autoescape=True) Where above, the given literal parameter will be converted to ``"foo^%bar^^bat"`` before being passed to the database. .. seealso:: :meth:`.ColumnOperators.endswith` :meth:`.ColumnOperators.contains` :meth:`.ColumnOperators.like` )r startswith_oprrr3rrr startswithsVzColumnOperators.startswithcKs|jt|f|S)a Implement the 'endswith' operator. Produces a LIKE expression that tests against a match for the end of a string value:: column LIKE '%' || E.g.:: stmt = select([sometable]).\ where(sometable.c.column.endswith("foobar")) Since the operator uses ``LIKE``, wildcard characters ``"%"`` and ``"_"`` that are present inside the expression will behave like wildcards as well. For literal string values, the :paramref:`.ColumnOperators.endswith.autoescape` flag may be set to ``True`` to apply escaping to occurrences of these characters within the string value so that they match as themselves and not as wildcard characters. Alternatively, the :paramref:`.ColumnOperators.endswith.escape` parameter will establish a given character as an escape character which can be of use when the target expression is not a literal string. :param other: expression to be compared. This is usually a plain string value, but can also be an arbitrary SQL expression. LIKE wildcard characters ``%`` and ``_`` are not escaped by default unless the :paramref:`.ColumnOperators.endswith.autoescape` flag is set to True. :param autoescape: boolean; when True, establishes an escape character within the LIKE expression, then applies it to all occurrences of ``"%"``, ``"_"`` and the escape character itself within the comparison value, which is assumed to be a literal string and not a SQL expression. An expression such as:: somecolumn.endswith("foo%bar", autoescape=True) Will render as:: somecolumn LIKE '%' || :param ESCAPE '/' With the value of :param as ``"foo/%bar"``. .. versionadded:: 1.2 .. versionchanged:: 1.2.0 The :paramref:`.ColumnOperators.endswith.autoescape` parameter is now a simple boolean rather than a character; the escape character itself is also escaped, and defaults to a forwards slash, which itself can be customized using the :paramref:`.ColumnOperators.endswith.escape` parameter. :param escape: a character which when given will render with the ``ESCAPE`` keyword to establish that character as the escape character. This character can then be placed preceding occurrences of ``%`` and ``_`` to allow them to act as themselves and not wildcard characters. An expression such as:: somecolumn.endswith("foo/%bar", escape="^") Will render as:: somecolumn LIKE '%' || :param ESCAPE '^' The parameter may also be combined with :paramref:`.ColumnOperators.endswith.autoescape`:: somecolumn.endswith("foo%bar^bat", escape="^", autoescape=True) Where above, the given literal parameter will be converted to ``"foo^%bar^^bat"`` before being passed to the database. .. seealso:: :meth:`.ColumnOperators.startswith` :meth:`.ColumnOperators.contains` :meth:`.ColumnOperators.like` )r endswith_oprgrrrendswithsVzColumnOperators.endswithcKs|jt|f|S)a Implement the 'contains' operator. Produces a LIKE expression that tests against a match for the middle of a string value:: column LIKE '%' || || '%' E.g.:: stmt = select([sometable]).\ where(sometable.c.column.contains("foobar")) Since the operator uses ``LIKE``, wildcard characters ``"%"`` and ``"_"`` that are present inside the expression will behave like wildcards as well. For literal string values, the :paramref:`.ColumnOperators.contains.autoescape` flag may be set to ``True`` to apply escaping to occurrences of these characters within the string value so that they match as themselves and not as wildcard characters. Alternatively, the :paramref:`.ColumnOperators.contains.escape` parameter will establish a given character as an escape character which can be of use when the target expression is not a literal string. :param other: expression to be compared. This is usually a plain string value, but can also be an arbitrary SQL expression. LIKE wildcard characters ``%`` and ``_`` are not escaped by default unless the :paramref:`.ColumnOperators.contains.autoescape` flag is set to True. :param autoescape: boolean; when True, establishes an escape character within the LIKE expression, then applies it to all occurrences of ``"%"``, ``"_"`` and the escape character itself within the comparison value, which is assumed to be a literal string and not a SQL expression. An expression such as:: somecolumn.contains("foo%bar", autoescape=True) Will render as:: somecolumn LIKE '%' || :param || '%' ESCAPE '/' With the value of :param as ``"foo/%bar"``. .. versionadded:: 1.2 .. versionchanged:: 1.2.0 The :paramref:`.ColumnOperators.contains.autoescape` parameter is now a simple boolean rather than a character; the escape character itself is also escaped, and defaults to a forwards slash, which itself can be customized using the :paramref:`.ColumnOperators.contains.escape` parameter. :param escape: a character which when given will render with the ``ESCAPE`` keyword to establish that character as the escape character. This character can then be placed preceding occurrences of ``%`` and ``_`` to allow them to act as themselves and not wildcard characters. An expression such as:: somecolumn.contains("foo/%bar", escape="^") Will render as:: somecolumn LIKE '%' || :param || '%' ESCAPE '^' The parameter may also be combined with :paramref:`.ColumnOperators.contains.autoescape`:: somecolumn.contains("foo%bar^bat", escape="^", autoescape=True) Where above, the given literal parameter will be converted to ``"foo^%bar^^bat"`` before being passed to the database. .. seealso:: :meth:`.ColumnOperators.startswith` :meth:`.ColumnOperators.endswith` :meth:`.ColumnOperators.like` )r contains_oprgrrrrZsWzColumnOperators.containscKs|jt|f|S)aYImplements a database-specific 'match' operator. :meth:`~.ColumnOperators.match` attempts to resolve to a MATCH-like function or operator provided by the backend. Examples include: * PostgreSQL - renders ``x @@ to_tsquery(y)`` * MySQL - renders ``MATCH (x) AGAINST (y IN BOOLEAN MODE)`` * Oracle - renders ``CONTAINS(x, y)`` * other backends may provide special implementations. * Backends without any special implementation will emit the operator as "MATCH". This is compatible with SQLite, for example. )rmatch_oprgrrrmatchszColumnOperators.matchcCs |tS)zMProduce a :func:`~.expression.desc` clause against the parent object.)rdesc_opr!rrrdescszColumnOperators.desccCs |tS)zLProduce a :func:`~.expression.asc` clause against the parent object.)rasc_opr!rrrascszColumnOperators.asccCs |tS)zSProduce a :func:`~.expression.nullsfirst` clause against the parent object.)r nullsfirst_opr!rrr nullsfirstszColumnOperators.nullsfirstcCs |tS)zRProduce a :func:`~.expression.nullslast` clause against the parent object.)r nullslast_opr!rrr nullslastszColumnOperators.nullslastcCs |t|S)zProduce a :func:`~.expression.collate` clause against the parent object, given the collation string. .. seealso:: :func:`~.expression.collate` )rcollate)rZ collationrrrrvs zColumnOperators.collatecCs |t|S)zaImplement the ``+`` operator in reverse. See :meth:`.ColumnOperators.__add__`. )r4rrrrr__radd__szColumnOperators.__radd__cCs |t|S)zaImplement the ``-`` operator in reverse. See :meth:`.ColumnOperators.__sub__`. )r4rrrrr__rsub__szColumnOperators.__rsub__cCs |t|S)zaImplement the ``*`` operator in reverse. See :meth:`.ColumnOperators.__mul__`. )r4rrrrr__rmul__szColumnOperators.__rmul__cCs |t|S)zaImplement the ``/`` operator in reverse. See :meth:`.ColumnOperators.__div__`. )r4rrrrr__rdiv__szColumnOperators.__rdiv__cCs |t|S)zaImplement the ``%`` operator in reverse. See :meth:`.ColumnOperators.__mod__`. )r4r rrrr__rmod__szColumnOperators.__rmod__FcCs|jt|||dS)z{Produce a :func:`~.expression.between` clause against the parent object, given the lower and upper range.  symmetric)r between_op)rZcleftZcrightr}rrrbetween szColumnOperators.betweencCs |tS)z[Produce a :func:`~.expression.distinct` clause against the parent object. )r distinct_opr!rrrdistinctszColumnOperators.distinctcCs |tS)aProduce a :func:`~.expression.any_` clause against the parent object. This operator is only appropriate against a scalar subquery object, or for some backends an column expression that is against the ARRAY type, e.g.:: # postgresql '5 = ANY (somearray)' expr = 5 == mytable.c.somearray.any_() # mysql '5 = ANY (SELECT value FROM table)' expr = 5 == select([table.c.value]).as_scalar().any_() .. seealso:: :func:`~.expression.any_` - standalone version :func:`~.expression.all_` - ALL operator .. versionadded:: 1.1 )rany_opr!rrrany_szColumnOperators.any_cCs |tS)aProduce a :func:`~.expression.all_` clause against the parent object. This operator is only appropriate against a scalar subquery object, or for some backends an column expression that is against the ARRAY type, e.g.:: # postgresql '5 = ALL (somearray)' expr = 5 == mytable.c.somearray.all_() # mysql '5 = ALL (SELECT value FROM table)' expr = 5 == select([table.c.value]).as_scalar().all_() .. seealso:: :func:`~.expression.all_` - standalone version :func:`~.expression.any_` - ANY operator .. versionadded:: 1.1 )rall_opr!rrrall_3szColumnOperators.all_cCs |t|S)a4Implement the ``+`` operator. In a column context, produces the clause ``a + b`` if the parent object has non-string affinity. If the parent object has a string affinity, produces the concatenation operator, ``a || b`` - see :meth:`.ColumnOperators.concat`. )rrrrrr__add__Ls zColumnOperators.__add__cCs |t|S)zdImplement the ``-`` operator. In a column context, produces the clause ``a - b``. )rrrrrr__sub__XszColumnOperators.__sub__cCs |t|S)zdImplement the ``*`` operator. In a column context, produces the clause ``a * b``. )rrrrrr__mul__`szColumnOperators.__mul__cCs |t|S)zdImplement the ``/`` operator. In a column context, produces the clause ``a / b``. )rrrrrr__div__hszColumnOperators.__div__cCs |t|S)zdImplement the ``%`` operator. In a column context, produces the clause ``a % b``. )rr rrrr__mod__pszColumnOperators.__mod__cCs |t|S)zeImplement the ``//`` operator. In a column context, produces the clause ``a / b``. )rrrrrr __truediv__xszColumnOperators.__truediv__cCs |t|S)zfImplement the ``//`` operator in reverse. See :meth:`.ColumnOperators.__truediv__`. )r4rrrrr __rtruediv__szColumnOperators.__rtruediv__)N)N)N)N)F)7r5r6r7r8r9 timetuplerFrGrr@r>rHrIrJrKrLrMrNrPrQrRrTrYr[r]r_rarcrdrerhrjrrmrorqrsrurvrwrxryrzr{rrrrrrrrrrrrrrrrE)sf%         [   XXY   rEcCst||Sr#) _commutativerfnrrrcommutative_ops rcCst||Sr#) _comparisonrrrrr comparison_ops rcCs tdSr#r0rrrrfrom_srcCs tdSr#rrrrrfunction_as_comparison_opsrcCs tdSr#rrrrras_srcCs tdSr#rrrrrexistssrcCs tdSr#rarrristruesrcCs tdSr#rrrrrisfalsesrcCs ||Sr#)rIrbrrrrIsrIcCs ||Sr#)rJrrrrrJsrJcCs ||Sr#)rdrrrrrdsrdcCs ||Sr#)rerrrrresrecCs ||Sr#)rvrrrrrvsrvcCs|||Sr#r-)rr(rrrrr,sr,NcCs|j||dSNrU)rYrrrVrrrrWsrWcCs|j||dSr)rarrrrr`sr`cCs|j||dSr)r[rrrrrZsrZcCs|j||dSr)rcrrrrrbsrbFcCs|j|||dSNr|)rrrcr}rrrr~sr~cCs|j|||dSr)Z notbetweenrrrr notbetween_opsrcCs ||Sr#)r]rrrrr\sr\cCs ||Sr#)r_rrrrr^sr^cCs|Sr#)rrrrrrsrcCs|Sr#)rrrrrrsrcCs|Sr#)rrrrrrsrcCsx|rl|dk rtd|dkr"d}t|tjjs8td|dkrP||||}|d|dd|d}|||dS) NTz;The autoescape parameter is now a simple boolean True/False/z*String value expected when autoescape=True)%_rrrU)rwarnr=compat string_types TypeErrorreplace)rrrV autoescaperrr_escaped_like_implsrcCst|j|||Sr#rrhrrrVrrrrrfsrfcCst|j|||Sr#rrrrrnotstartswith_opsrcCst|j|||Sr#rrjrrrrrisricCst|j|||Sr#rrrrrnotendswith_op#srcCst|j|||Sr#rrrrrrrk(srkcCst|j|||Sr#rrrrrnotcontains_op-srcKs|j|f|Sr#)rmrrrCrrrrl2srlcKs|j|f|Sr#)Znotmatchrrrr notmatch_op7srcCs tdSr#rrrrrcomma_op<srcCs tdSr#rrrrr empty_in_op@srcCs tdSr#rrrrrempty_notin_opEsrcCs tdSr#rrrrr filter_opJsrcCs ||Sr#)rTrrrrrSNsrScCs|Sr#)rorrrrrnRsrncCs|Sr#)rqrrrrrpVsrpcCs|Sr#)rsrrrrrrZsrrcCs|Sr#)rurrrrrt^srtcCs tdSr#rrrrrjson_getitem_opbsrcCs tdSr#rrrrrjson_path_getitem_opfsrcCs|tkpt|to|jSr#)rr=r'r*r-rrrr*jsr*cCs|tkSr#)rr-rrris_commutativensrcCs|ttttfkSr#)rprnrrrtr-rrris_ordering_modifierrsrcCs|tkpt|to|jSr#)_natural_self_precedentr=r'r:r-rrris_natural_self_precedentvs rcCst|p|tkSr#)r* _booleansr-rrr is_booleansrcCs t||S)z[rotate a comparison operator 180 degrees. Note this is not the same as negation. )_mirrorgetr-rrrmirrorsr_asbooli) canonical _smallesti_largestdcCs@||krt|rdSt|t|dtt|t|dtkSdS)NFr))r _PRECEDENCErgetattrrr)r%r&rrr is_precedents r)N)N)N)N)F)F)NF)NF)NF)NF)NF)NF)^r8r%rrrrrrrr r r r r rrrrrrrrZpy2krobjectrr'rErrrrrrrrrrrIrJrdrervr,rWr`rZrbr~rr\r^rrrrrfrrirrkrrlrrrrrrSrnrprrrtrrr*rrrrrrrunion differenceZ _associativersymbolrrrrrrrrr s                    H8f                          9