Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#169: Adapt shared tests to bugfix in Exasol DB #170

Merged
merged 3 commits into from
Sep 23, 2024

Conversation

kaklakariada
Copy link
Collaborator

Closes #169

@kaklakariada kaklakariada enabled auto-merge (squash) September 23, 2024 13:22
assertThat(exception.getMessage(), containsString(
"OverflowException: E-VSD-38: A value for column 'EXA_COL' exceeded the configured varcharColumnSize of 6."));

this.assertQuery("SELECT * FROM TEST.BOOKS", table("VARCHAR").row("short").row("very_l").matches());
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 the name refreshVirtualSchemaReadsIgnoresNonSchemaChanges of the test case still reflects the old semantics. Maybe we should rename it?

Additionally, I wonder: How could / can the VSDF identify the version of the Exasol database?
Or is this up to the concrete implementations inheriting from VSDF?

In any way: Can and should the VSDF at least signal, which versions of Exasol database are supported or which include the bug and which fix it?

Copy link

sonarcloud bot commented Sep 23, 2024

@kaklakariada kaklakariada merged commit 9866d66 into main Sep 23, 2024
5 checks passed
@kaklakariada kaklakariada deleted the kaklakariada/issue169 branch September 23, 2024 15:47
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.

Adapt shared integration tests to bugfix in Exasol
2 participants