summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMike Bayer <mike_mp@zzzcomputing.com>2015-03-14 10:17:12 -0400
committerMike Bayer <mike_mp@zzzcomputing.com>2015-03-14 10:17:43 -0400
commit3c3dc2bce9f0a8eb7f05060f01d9fff8bdd402ce (patch)
treea692b1749a466cbddf7150c11b38e111f900f1f5
parent2c893b520a6ff67f5604dc27644aedc96d3929ff (diff)
downloadsqlalchemy-3c3dc2bce9f0a8eb7f05060f01d9fff8bdd402ce.tar.gz
- remove now-misleading comment that SQLite doesn't support MATCH,
since they've apparently added something for it
-rw-r--r--lib/sqlalchemy/sql/operators.py6
1 files changed, 4 insertions, 2 deletions
diff --git a/lib/sqlalchemy/sql/operators.py b/lib/sqlalchemy/sql/operators.py
index e043c2a70..2775205ca 100644
--- a/lib/sqlalchemy/sql/operators.py
+++ b/lib/sqlalchemy/sql/operators.py
@@ -512,8 +512,10 @@ class ColumnOperators(Operators):
* 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;
- some backends such as SQLite have no support.
+ * other backends may provide special implementations.
+ * Backends without any special implementation will emit
+ the operator as "MATCH". This is compatible with SQlite, for
+ example.
"""
return self.operate(match_op, other, **kwargs)