fix(admin_manual): Explicitly specify which versions of MySQL #11801
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
☑️ Resolves
Rather than say "8.0+" (which could lead to problems with deployments using untested versions of MySQL with Nextcloud) let's stick to the actual versions we test against.
Currently (in
master
) that is, technically 8.0 and 8.3, but not the recently published 8.4. We are explicit with our other recommended databases so let's be consistent here too.Included 8.2 since, like for PostgreSQL, our automated test matrix skips it for efficiency (presumably) since it likely is covered by our 8.0 and 8.3 tests (it's out of scope to debate the pros/cons of that here).
🖼️ Screenshots
New:
Existing: