summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/sql/operators.py
diff options
context:
space:
mode:
Diffstat (limited to 'lib/sqlalchemy/sql/operators.py')
-rw-r--r--lib/sqlalchemy/sql/operators.py19
1 files changed, 13 insertions, 6 deletions
diff --git a/lib/sqlalchemy/sql/operators.py b/lib/sqlalchemy/sql/operators.py
index 98d763e98..0a8527761 100644
--- a/lib/sqlalchemy/sql/operators.py
+++ b/lib/sqlalchemy/sql/operators.py
@@ -217,14 +217,17 @@ class 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
+ :param is_comparison: legacy; 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 is provided
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.
+ Using the ``is_comparison`` parameter is superseded by using the
+ :meth:`.Operators.bool_op` method instead; this more succinct
+ operator sets this parameter automatically, but also provides
+ correct :pep:`484` typing support as the returned object will
+ express a "boolean" datatype, i.e. ``BinaryExpression[bool]``.
:param return_type: a :class:`.TypeEngine` class or object that will
force the return type of an expression produced by this operator
@@ -255,6 +258,8 @@ class Operators:
.. seealso::
+ :meth:`.Operators.bool_op`
+
:ref:`types_operators`
:ref:`relationship_custom_operator`
@@ -284,7 +289,9 @@ class Operators:
This method is shorthand for calling
:meth:`.Operators.op` and passing the
:paramref:`.Operators.op.is_comparison`
- flag with True.
+ flag with True. A key advantage to using :meth:`.Operators.bool_op`
+ is that when using column constructs, the "boolean" nature of the
+ returned expression will be present for :pep:`484` purposes.
.. seealso::