MySQL Bugs: #73181: Copy db.opt when using --include-tables="db.*"

Bug #73181	Copy db.opt when using --include-tables="db.*"
Submitted:	2 Jul 2014 20:28
Reporter:	Daniël van Eeden (OCA)	Email Updates:
Status:	Open	Impact on me:	None
Category:	MySQL Enterprise Backup	Severity:	S4 (Feature request)
Version:	3.10	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	character set

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
If I use the new --include-tables to copy all tables from one database then the db.opt file is not copied. This can result in a different database collation.

How to repeat:
Use --include-tables option to copy a whole database and see if the collation and charset for the database on the target and source match. You should try a non-default charset like utf8mb4 too 'see' the difference.

Suggested fix:
Copy db.opt when appropriate.