Thanks Peter. I was wondering if the age of our installation might have
been the issue. I was even trying to poke through the code to see what it
was looking for in the check to see if there was that sort of mis-match
between what ASpac was looking for and what MySQL was returning.
Fortunately,
Indeed, university IT updated our MySQL server from 5.x to 8.x. But this
was back in early November. Everything had been working fine since then.
*Matt Adair*
Archivist for Digital Imaging and Infrastructure
Bentley Historical Library
1150 Beal Avenue
Ann Arbor, Michigan 48109-2113
Matthew Adair wrote on 2023-01-18 14:23:14:
> Version 2.5.2 of ASpace. Version 8.0.30 of MySQL
A couple of versions prior to yours MySQL started explicitly reporting
'utf8mb3' where in the past it would say 'utf8'. That's because 'utf8' is
currently an alias for 'utf8mb3' and they want to
Is there any way that your version of MySQL got upgraded? I see this in
the MySQL documentation:
https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-utf8.html
which indicates that utf8mb3 is deprecated after Mysql 8.0.28.
I don't have any experience to say that this is where the problem
Version 2.5.2 of ASpace. Version 8.0.30 of MySQL
We get the following error in the log file:
"The following MySQL database tables are not set to use UTF-8 for their
character encoding:"
and then it lists all of the database tables, and fails with an unable to
connect to database error
Encoding
