Seebs 2af417d5c2 don't panic on a MIN that isn't a call ... parseOperand was assuming that any reference to MIN in a place where an operand was expected was a call, which it should be, but it might not be. parseCallExpression panics if it doesn't find a parenthesis, because it's never supposed to be called when we don't know we have one. The test for this is in with MinMaxColumnConstraints, even though it's actually a test of MinMaxFunctionCalls, because that's where the other tests involving the special MIN/MAX tokens live. We also stop checking whether MIN or MAX might actually be QIDENT. If you use a quoted identifier, we're over in the QIDENT case, not the MIN/MAX case. If the token was MIN or MAX, it's always unquoted.		2023-04-03 16:29:21 -05:00
..
ast.go	Improve test coverage for ast components in ast.go (#2355)	2023-03-31 14:27:18 -04:00
ast_test.go	Improve test coverage for ast components in ast.go (#2355)	2023-03-31 14:27:18 -04:00
astdatatype.go	implement select from time quantum columns (fb-1654) (#2282)	2023-03-02 00:06:58 -06:00
parser.go	don't panic on a MIN that isn't a call	2023-04-03 16:29:21 -05:00
parser_test.go	don't panic on a MIN that isn't a call	2023-04-03 16:29:21 -05:00
scanner.go	drop unused isHex and IsInteger functions	2023-03-27 16:56:29 -05:00
scanner_test.go	increase parser test coverage significantly	2023-03-27 16:56:29 -05:00
token.go	Support for setting individual DatabaseOptions (#2231)	2023-02-06 08:50:28 -06:00
token_test.go	cleaned up sync from private repo	2022-09-30 11:20:58 -07:00
walk.go	Enable linter: stylecheck (#2317)	2023-03-14 08:45:18 -05:00