Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@Swastik092
Copy link

This PR adds initial support for QuestDB in SQLancer.

Changes included:

  • Created QuestDBQueryGenerator.java to generate simple SELECT queries.
  • Updated QuestDBProvider.java to use the new generator.
  • Ensured queries are executed against a running QuestDB instance.
  • Limited multi-threading (--num-threads 1) for stability during testing.

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.

Copy link
Contributor

@mrigger mrigger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like an accidental commit.

errors.add("missing required column");
errors.add("table does not exist");
errors.add("permission denied");
errors.add("syntax error in INSERT statement");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Syntax errors are always unexpected, so we should fix this in the generator.

return r.getInteger(0, 3);
case TRUNCATE:
return r.getInteger(0, 5);
case UPDATE:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should only add new features once we have a CI/CD that works for a given QuestDB version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants