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
..
parser	don't panic on a MIN that isn't a call	2023-04-03 16:29:21 -05:00
planner	Improve test coverage for ast components in ast.go (#2355)	2023-03-31 14:27:18 -04:00
test	Fb 2048 (#2363)	2023-04-03 12:04:41 -05:00
errors.go	fb-2036 improve coverage for create view statement (#2333)	2023-03-21 14:06:38 -04:00
interfaces.go	introduce performance counters and system table fanout, plus refactor metrics (#2363)	2023-01-19 21:35:02 +00:00
main_test.go	added testify dependency	2022-09-30 11:31:37 -07:00
sql_complex_test.go	Fb 2048 (#2363)	2023-04-03 12:04:41 -05:00
sql_test.go	Fb 2048 (#2363)	2023-04-03 12:04:41 -05:00