Request:
Given that WordPress has been defaulting to the utf8mb4_unicode_520_ci collation (or at least utf8_general_ci) for some time now, it would make sense for LocalWP to align with this standard by adjusting its default database collation settings.
Rationale:
Aligning LocalWP’s default database collation with WordPress’s standard would help prevent potential issues when creating custom database views or stored procedures. This small change could save developers time and headaches by ensuring consistency across environments.
Current Workaround:
While it’s possible to manually set the collation ourselves, it would be incredibly convenient if LocalWP handled this automatically when setting up new projects. This way, developers can focus more on building and less on configuration.
Additional Information:
For more details on how WordPress determines its charset and collation, you can refer to this documentation: WordPress determine_charset().
Conclusion:
Implementing this change would streamline the setup process for developers using LocalWP, making it even more aligned with WordPress best practices.
Thanks for considering this enhancement! It would make working with LocalWP even more seamless.
