From e9241945801808d1db7f76bdccbbe9a200042c37 Mon Sep 17 00:00:00 2001
From: Andi Albrecht <albrecht.andi@gmail.com>
Date: Fri, 30 Dec 2022 10:57:31 +0100
Subject: Revert "add regex pattern to identify IN as a Compasion token"

This reverts commit 28c4d4026e1d9389a99d8cd627c96fa360c17fc4.

See #694. The expectation is that IN is primarily recognized as a keyword,
although it acts as a comparison operator. This also matches the definition of
IN in most SQL syntax references where it is listed as a reserved
keyword (PostgreSQL:
https://www.postgresql.org/docs/current/sql-keywords-appendix.html, MySQL:
https://dev.mysql.com/doc/refman/8.0/en/keywords.html, for example).
---
 sqlparse/keywords.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'sqlparse')

diff --git a/sqlparse/keywords.py b/sqlparse/keywords.py
index d73e114..dff5e1c 100644
--- a/sqlparse/keywords.py
+++ b/sqlparse/keywords.py
@@ -50,7 +50,7 @@ SQL_REGEX = {
         (r'(?<!\w)[$:?]\w+', tokens.Name.Placeholder),
 
         (r'\\\w+', tokens.Command),
-        (r'(NOT\s+)?(IN)\b', tokens.Operator.Comparison),
+
         # FIXME(andi): VALUES shouldn't be listed here
         # see https://github.com/andialbrecht/sqlparse/pull/64
         # AS and IN are special, it may be followed by a parenthesis, but
-- 
cgit v1.2.1