-
Notifications
You must be signed in to change notification settings - Fork 89
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
FR - Consider adding support for MySQL 8 #41
Comments
Hi @fraenki , there are two ways to fix this:
We discussed this and will postpone support for MySQL 8 to the first feature branch. This will be released at the end of June / beginning of July. In both cases existing addons would not work anymore, if they rely on the groups table (for what ever reason). Regards |
@hanneshal Sounds great, thanks for the status update! |
@rkaldung Great news, thanks for the update! 👍 |
@fraenki It's already in Znuny, starting with version 6.1.1 |
This means that in https://doc.znuny.org/doc/manual/admin/stable/en/html/otrs.html#software-requirements
is not valid anymore? |
Correct. Since 6.1 MySQL 8 can be used. https://doc.znuny.org/manual/releases/installupdate/install.html |
Environment
Expected behaviour
As a software that is maintained and under active development, Znuny should support current database versions like MySQL 8.
Actual behaviour
The README clearly states:
MySQL 8+ is not supported
So I'd assume that Znuny does not work when using MySQL 8.
How to reproduce
Not tested.
Additional information
We're considering to migrate to Znuny. However, having MySQL 8 on the roadmap would allow us to plan the next steps. Other applications are already dropping support for MySQL 5.7, so it's getting harder for Znuny to co-exist with other applications on the same infrastructure.
For OTRS 6.x a patch was provided by a community member that should address some MySQL 8 issues:
https://bugs.otrs.org/show_bug.cgi?id=13866
Maybe this could be seen as a starting point for some progress towards MySQL 8 support.
Screenshots
The text was updated successfully, but these errors were encountered: