Duplicate database fails after upgrade from mysql 5.7 to 8

[paolomartini]

Thank you Sequel-Ace team for supporting the continuing development of Sequel Ace!

We have upgraded our DB from mySQL 5.7 to 8 (it's an AWS RDS). We are seeing no errors so far, except we just tried to duplicate a schema with Sequel Ace, including content ('duplicate database' option in the 'Database' dropdown) and we are consistently getting the following error: 'An error occurred while trying to copy the database'. The destination database gets created, but it is empty (no table, no data). This works perfectly with our mySQL 5.7 databases.

Anyone else encountering this problem with mySQL 8?

Thanks, paolo

[Jason-Morcos]

I see one sorta similar issue to this here #1712!

Do you see any specific error messages? Perhaps on the database log itself?

[paolomartini]

Hi Robin,

It's an RDS MySQL community version 8.034 (not Aurora).
I can try spinning up a new one later tonight, but if you have bandwidth it
would be good if you could kindly try yourself, so we would know if it is
something specific to us, you never know with AWS!

Thanks so much for pitching in, we appreciate it!

Paolo

[paolomartini]

Hi Jason,

Here are the server variables for the 5.7.42 DB:

character_set_client = utf8mb4
character_set_connection = utf8mb4
character_set_database = utf8
character_set_filesystem = binary
character_set_results = utf8mb4
character_set_server = latin1
character_set_system = utf8
collation_connection = utf8mb4_general_ci
collation_database = utf8_general_ci
collation_server = latin1_swedish_ci

[paolomartini]

As a bit of context, mySQL 5.7 was EOL this past October 31st and will no longer receive security patches. AWS won't make it available for install after end February 2024 and will only offer an extended support option for pay after that date.

[robinkunde]

#1919

[paolomartini]

That's fantastic! Thank you Robin!