Nikhil Benesch 90bcf55a6a Fix the precedence of NOT LIKE ... NOT LIKE has the same precedence as the LIKE operator. The parser was previously assigning it the precedence of the unary NOT operator. NOT BETWEEN and NOT IN are treated similarly, as they are equivalent, from a precedence perspective, to NOT LIKE. The fix for this requires associating precedences with sequences of tokens, rather than single tokens, so that "NOT LIKE" and "NOT <expr>" can have different preferences. Perhaps surprisingly, this change is not very invasive. An alternative I considered involved adjusting the tokenizer to lex NOT, NOT LIKE, NOT BETWEEN, and NOT IN as separate tokens. This broke symmetry in strange ways, though, as NotLike, NotBetween, and NotIn gained dedicated tokens, while LIKE, BETWEEN, and IN remained as stringly identifiers. Fixes #81.		2019-06-01 02:52:18 -04:00
..
sqlparser_common.rs	Fix the precedence of NOT LIKE	2019-06-01 02:52:18 -04:00
sqlparser_mssql.rs	Add comments to the test files	2019-05-04 02:43:00 +03:00
sqlparser_postgres.rs	Add comments to the test files	2019-05-04 02:43:00 +03:00