[wp-trac] [WordPress Trac] #60096: Remove back-compat for database servers that don't support utf8mb4
WordPress Trac
noreply at wordpress.org
Thu Feb 15 05:31:46 UTC 2024
#60096: Remove back-compat for database servers that don't support utf8mb4
--------------------------------------+--------------------------
Reporter: johnbillion | Owner: johnbillion
Type: task (blessed) | Status: assigned
Priority: normal | Milestone: 6.5
Component: Database | Version: trunk
Severity: normal | Resolution:
Keywords: has-patch has-unit-tests | Focuses:
--------------------------------------+--------------------------
Comment (by jlekbpnl27):
To remove the back-compatibility code for database servers that don't
support the utf8mb4 charset, follow these steps:
1. **Identify Back-Compat Code**: Locate the portions of the codebase that
handle compatibility with database servers that do not support utf8mb4
charset. This may involve searching for conditionals or functions
specifically designed for this purpose.
2. **Review Changes Since [57173]**: Review the changes introduced in
revision [57173] to ensure that the minimum supported version of MySQL is
5.5.5, making utf8mb4 charset support universally available. Confirm that
there are no regressions or compatibility issues introduced by this
change.
3. **Remove Back-Compat Code**: Once you've identified the back-
compatibility code, remove it from the codebase. This may involve deleting
conditionals, functions, or entire code blocks related to handling servers
that don't support utf8mb4.
4. **Update Tests and Health Checks**: Remove any related tests or health
checks that were specifically designed to handle compatibility with
database servers lacking utf8mb4 support. Ensure that all tests and health
checks still pass after the removal of this code.
5. **Testing**: Thoroughly test the application after removing the back-
compat code to ensure that it behaves as expected on all supported
database servers. Pay particular attention to any areas of functionality
that were previously affected by the compatibility code.
6. **Documentation**: Update any relevant documentation, including
changelogs or README files, to reflect the removal of back-compatibility
code and the updated minimum supported version of MySQL.
7. **Review and Commit**: Have the changes reviewed by other contributors
or maintainers to ensure their correctness and adherence to project
standards. Once approved, commit the changes to the codebase.
8. **Announcement (Optional)**: Consider making an announcement to the
community or relevant stakeholders about the removal of back-compat code
and the implications for database server support.
By following these steps, you can safely remove back-compatibility code
for database servers that don't support utf8mb4 charset, in alignment with
the updated minimum supported version of MySQL.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/60096#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list