From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Sat, 14 Mar 2015 14:17:12 +0000 (-0400)
Subject: - remove now-misleading comment that SQLite doesn't support MATCH,
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=3c3dc2bce9f0a8eb7f05060f01d9fff8bdd402ce;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

- remove now-misleading comment that SQLite doesn't support MATCH,
since they've apparently added something for it
---

diff --git a/lib/sqlalchemy/sql/operators.py b/lib/sqlalchemy/sql/operators.py
index e043c2a701..2775205ca6 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)