# OpenEMR 5.0.2 Patch **URL:** \ **Category:** OpenEMR Development\ **Created:** [October 15, 2019, 8:46am UTC](https://community.open-emr.org/t/openemr-5-0-2-patch/13007 "2019-10-15T08:46:15Z")\ **Posts on this page:** 1\ **Showing post:** 46
**Author:** ![stephenwaite](https://community.open-emr.org/user_avatar/community.open-emr.org/stephenwaite/32/15754_2.png) [@stephenwaite](https://community.open-emr.org/u/stephenwaite)\ **Post date:** [May 22, 2020, 8:41pm UTC](https://community.open-emr.org/t/openemr-5-0-2-patch/13007/46 "2020-05-22T20:41:15Z")
always good to go back and see what brady recommended: > [@Error Installing Version 5.0.2](https://community.open-emr.org/t/error-installing-version-5-0-2/12806/19): > > hi @konsyr11 , I tested to work ok on mariadb 10.3.18. You need to use utf8\_general\_ci collation when you create the database. The utf8mb4\_unicode\_ci will take up more space, which is why it breaks history\_data table. In the future, it would be good if somebody took the task to ensure mb4 support in OpenEMR, but I’m guessing that’s likely not gonna happen anytime soon. it’s the collation of the openemr database 🙂 --- _[View the full topic](https://community.open-emr.org/t/openemr-5-0-2-patch/13007)._