[Bug]: MySQL `utf8` -> `utf8mb3` deprecation / transition handling
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
The upgrade command changes the row format of many tables to dynamic, even if it is already set to dynamic. The attempted change is repeated, apparently for each app that is upgraded. This takes almost an hour on larger installation, several minutes alone on oc_filecache.
Steps to reproduce
- Check on oc_filecache for format: dynamic; options:row_format=DYNAMIC.
- Run
occ upgrade - Monitor MySQL status, you will see ALTER TABLE
oc_filecacheROW_FORMAT = DYNAMIC
Expected behavior
No change of DB format if it is already correctly set
Installation method
Community Docker image
Nextcloud Server version
29
Operating system
Debian/Ubuntu
PHP engine version
None
Web server
None
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 28 to 29)
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the database schema handling invoked by occ upgrade, focusing on the repeated ALTER TABLE oc_filecache ROW_FORMAT = DYNAMIC operation and the MySQL/MariaDB upgrade path. Done means an already-DYNAMIC table is not altered again during upgrade, while the reported utf8 to utf8mb3 transition is handled as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mariadb, mysql, php
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100