Your insight is very much needed here.
On a similar note on database, I am noticing some strange issues that has to do with character encoding issues. For example, after a successful upgrade, I noticed that if apostrophe, double quotations, or if a tick mark is on any letters, in the article title, abstract, and authors bio, it creates an issues. This is what happens:
While logged in as an admin, if I click on an affected article (the affected articles sometimes have a black circle with a question mark symbol in the middle of the circle and sometimes, affected articles do not have any weird symbols), I will see the title, abstract, keywords, authors bio, and indexing information. All these will show up when viewing a submission or published piece. This is where it gets wonky. When I click "Edit Metadata" for the affected article, I notice that the data in the bio and abstracts, and sometimes the title are not there. In other words, the bio and abstracts boxes are blank when you click Edit the Metadata, but the text will display if you are not editing the metadata of the article. In many cases, bio and abstracts are always the one affected, and few times, the title. I do not know how the text shows up when not logged in as a user, and when not editing the article submission even though you are logged in as an admin.
I have also noticed some of the same issue in announcement. If you have double quotation marks " " or apostrophe, it spits out a little black circle like above. To make sure I do not loose the information entered originally, I have to open different 2 browser tabs. The first tab is to show the actual announcement as it would appear to the website visitor, and the other tab is for editing the actual announcement. When logged in as the admin, if I click the edit link to edit the actual announcement, there is no text in the two boxes. So, while anyone can view the announcement, when you click to edit the announcement, the text disappears. If you hit save, you loose data that shows up on the frontend but not in the backend.
At one time, I did set this character set in the configuration to on.
Database connection character set
connection_charset = On
Database storage character set
database_charset = On
Enable character normalization to utf-8 (recommended)
charset_normalization = On
In my database, some of the tables have the collation as latin1_swedish_ci and some have utf8_general_ci collation?
Should I change to utf8_general_ci collation? If changing to utf8_general_ci collation, will these solve the issues?