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

Add test class to ensure that version specific features have still not been implemented yet #1820

Open
lauxjpn opened this issue Dec 3, 2023 · 0 comments

Comments

@lauxjpn
Copy link
Collaborator

lauxjpn commented Dec 3, 2023

The ServerVersionSupport derived classes of MySqlServerVersionSupport and MariaDbServerVersionSupport are heavily used internally to determine which features are available and what syntax to use for them.

We current do not check whether a once unavailable/not implemented feature became available/was implemented in the meantime in a newer database engine version.

We should add a test class for that (or one for each officially supported database engine), so that we get a failed test, once a feature becomes available, which would then prompt us to look into that change.

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

No branches or pull requests

1 participant