featurebase/pql
Seebs 6d93e41e7f catch the panic we throw for an invalid timestamp
We recover from some specific panics deeper in the PEG parser, but when
we added the invalid timestamp, we didn't add it to the list we catch
and handle gracefully. Add test case for this, and test case for
successful parsing. Also add the word "valid" to the error message so
people don't get as confused by it.
2022-02-22 16:20:09 -06:00
..
ast.go Restrict max-memory to Extract() calls only 2022-02-11 14:19:56 -06:00
ast_test.go add test 2022-02-09 12:33:12 -06:00
decimal.go add copyright notice back in 2021-12-10 11:01:04 -06:00
decimal_test.go Upgrade go.mod to featurebase/v3 2022-01-21 10:57:05 -07:00
doc.go add copyright notice back in 2021-12-10 11:01:04 -06:00
parser.go catch the panic we throw for an invalid timestamp 2022-02-22 16:20:09 -06:00
parser_test.go catch the panic we throw for an invalid timestamp 2022-02-22 16:20:09 -06:00
pql.peg messing with parser, Rows call 2022-02-07 16:21:35 -06:00
pql.peg.go messing with parser, Rows call 2022-02-07 16:21:35 -06:00
pqlpeg_test.go Parse variables for _field 2022-02-07 15:40:24 -07:00
token.go add copyright notice back in 2021-12-10 11:01:04 -06:00