MySQL Bugs: #8674: CREATE DATABASE db DEFAULT ROW

Bug #8674	CREATE DATABASE db DEFAULT ROW_FORMAT=...
Submitted:	22 Feb 2005 10:58	Modified:	4 Feb 2009 9:44
Reporter:	Marko Mäkelä	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: DDL	Severity:	S4 (Feature request)
Version:	5.0.3	OS:	Any (all)
Assigned to:		CPU Architecture:	Any

Description:
MySQL 5.0.3 introduces another storage format for InnoDB tables, ROW_FORMAT=COMPACT, which is the default.

It would be nice to be override the default ROW_FORMAT on per-database basis for testing and benchmarking purposes.

How to repeat:
CREATE DATABASE test DEFAULT ROW_FORMAT=REDUNDANT;
-- returns ERROR 1064
CREATE DATABASE test ROW_FORMAT=REDUNDANT;
-- returns ERROR 1064
USE test;

Suggested fix:
The ROW_FORMAT for a CREATE TABLE statement would be interpreted as follows:
(1) if ROW_FORMAT=... is specified with CREATE TABLE, use it
(2) if ROW_FORMAT=... has been specified for the database, use it
(3) fall back to the default row format of the table handler

While you are at it, allow DEFAULT ENGINE=... as well. DEFAULT CHARACTER SET=... is already allowed.

Many thanks for writing a feature request. We will discuss this.

This is a feature that I wish existed, it would save me a lot of hassle for an issue I'm having now. I basically need to restore a large database onto a server setup for table compression, with a disk size about 10% larger than the compressed tables are. However as I cannot instruct the restore to use compressed tables, I don't have enough space.

So, add one vote to this feature.

row_format=dynamic is required for proper utf8mb4 support Django. I vote for this.

see also bug #77090