Bug 39833 - mysqldump SET character_set_client = utf8 vs utf8mb4
Summary: mysqldump SET character_set_client = utf8 vs utf8mb4
Status: Pushed to main
Alias: None
Product: Koha
Classification: Unclassified
Component: Architecture, internals, and plumbing (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low normal
Assignee: Jonathan Druart
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-05 12:13 UTC by Jonathan Druart
Modified: 2025-05-06 00:29 UTC (History)
1 user (show)

See Also:
GIT URL:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
25.05.00
Circulation function:


Attachments
Bug 39833: Adjust character_set_client in kohastructure.sql (117.91 KB, patch)
2025-05-05 12:21 UTC, Jonathan Druart
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Druart 2025-05-05 12:13:06 UTC
We have 
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

but kohastructure.sql has
/*!40101 SET character_set_client = utf8 */;

However it seems that now koha-dump uses:
/*!40101 SET character_set_client = utf8mb4 */;
Comment 1 Jonathan Druart 2025-05-05 12:21:14 UTC
Created attachment 181914 [details] [review]
Bug 39833: Adjust character_set_client in kohastructure.sql

koha-dump now generates the dump with utf8mb4
Comment 2 Jonathan Druart 2025-05-05 12:24:14 UTC
Pushed to main for 25.05.