Skip to content

Conversation

@CelestaLiu
Copy link
Collaborator

Support duckdb testing by using Versions Plugin to modify pom.xml while building sqlancer image.
Closes #18

@CelestaLiu CelestaLiu requested a review from suyZhong August 17, 2025 19:51

WORKDIR /root/sqlancer

ARG DUCKDB_JDBC_VERSION=1.3.0.0
Copy link
Collaborator

Choose a reason for hiding this comment

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

hmmm, is it hardcode or? I find it doesn't match the 1.2.2.0 in config

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

return to the original version

Copy link
Collaborator

Choose a reason for hiding this comment

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

I'm not sure if we should make the DuckDB components in the SQLancer Dockerfile. i.e., if we have more DBs, we might make this file very messy. Perhaps alternatively, we can have a 'fork' of the SQLancer Dockerfile in the duckdb folder?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

add customized dockerfile to duckdb/

"embedded": "yes",
"dbms": "duckdb",
"version": "1.2.2.0",
"username": "N/A",
Copy link
Collaborator

Choose a reason for hiding this comment

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

Do we need this entry or we can also remove it with no hurt?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

remove "version"

@suyZhong suyZhong merged commit ecaf243 into main Sep 8, 2025
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.

Add support for DuckDB

3 participants