Columns prefixed with "upper_" or "lower_" incorrectly parsed
rpham-eog opened this issue · comments
rpham-eog commented
What version of GraphJin are you using?
Graphjin standalone v3.0.12 (latest)
Have you tried reproducing the issue with the latest release?
Yes
What is the hardware spec (RAM, OS)?
64 GB, macOS Monterey
Steps to reproduce the issue (config used to run GraphJin).
- Create a table with a column named
upper_bound
andlower_bound
. - Send a query to that table with
upper_bound
and/orlower_bound
selected.
Issue can be reproduced from this repo.
Expected behaviour and actual result.
Actual result:
Returns an error with message:
{ errors: [ { message: "column: 'ranges.bound' not found" } ] }
Expected:
Return with empty no error. (Table has no data).