The OpenEMR database has been waiting patiently for a student to modernize it. At this time, OpenEMR overrides the sql_mode settings (sets it to empty) in order to ensure compatibility with MariaDB and MySQL and issues are beginning to arise because of this. Goal would be for OpenEMR’s database to support the default sql_mode settings in MariaDB and MySQL8 (note mysql8 has more by default). Goal of this modernization is to also support it for folks that are upgrading OpenEMR from prior versions. Another thing to consider is support for utf8mb4 encoding. After completing this, the student would then be in a good position to plan and begin development on a mechanism to support offsite use of OpenEMR; see here for thoughts and even a prelim PR on this using UUID’s: 2277 UUID by GJDBrink · Pull Request #2360 · openemr/openemr · GitHub
hi @vishal_io ,
I would probably start adding back the default sql_mode settings and see what breaks to get an idea of the scope of issues/improvements that would be involved.
Additionally would see what breaks when use utf8mb4 to get an idea of the scope of issues/improvements that would be involved.
Hi @brady.miller I’m Gaurav Kumar. Currently I’m a senior Undergraduate student at the Indian Institute of Technology, Mandi. I would like to work on this project. I worked with lablua in Google summer of code 2019 as a student and successfully completed the GSoC project last year. I have worked on a few web development projects which included working with MySQL, SQLite and MongoDB databases. I am quite proficient in MySQL , Javascript , docker and html. Let me know more about the project so that I can draft a proposal for the same.
For this project, a good starting point would be to see what happens (ie. what breaks) when adding back default sql_mode settings during the installation: