Add initial QuestDB support with simple SELECT generator (Fixes #457) - #1277
Add initial QuestDB support with simple SELECT generator (Fixes #457)#1277Swastik092 wants to merge 4 commits into
Conversation
Sorry, something went wrong.
mrigger
left a comment
There was a problem hiding this comment.
Thanks, this is great! We currently don't have a CI/CD test for QuestDB. Do you think it would be possible to add one first before adding new features?
Sorry, something went wrong.
There was a problem hiding this comment.
Seems like an accidental commit.
Sorry, something went wrong.
| errors.add("missing required column"); | ||
| errors.add("table does not exist"); | ||
| errors.add("permission denied"); | ||
| errors.add("syntax error in INSERT statement"); |
There was a problem hiding this comment.
Syntax errors are always unexpected, so we should fix this in the generator.
Sorry, something went wrong.
| return r.getInteger(0, 3); | ||
| case TRUNCATE: | ||
| return r.getInteger(0, 5); | ||
| case UPDATE: |
There was a problem hiding this comment.
I think we should only add new features once we have a CI/CD that works for a given QuestDB version.
Sorry, something went wrong.
Reviewers
At least 1 approving review is required to merge this pull request.
This PR adds initial support for QuestDB in SQLancer.
Changes included:
Currently, only basic SELECT queries are supported. INSERT, DELETE, and more complex queries will be added in future iterations.
This addresses Issue #457 and lays the foundation for full QuestDB testing support.