MySQL Bugs: #8697: backup modul, option 'no CREATEs'

Bug #8697	backup modul, option 'no CREATEs'
Submitted:	22 Feb 2005 16:52	Modified:	30 May 2005 14:08
Reporter:	Michael Kofler	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.0.19	OS:	Windows (win + linux)
Assigned to:	Vladimir Kolesnikov	CPU Architecture:	Any

Description:
the documentation says, the option 'no CREATEs' produces backup files without CREATE DATABASE commands:

http://dev.mysql.com/doc/administrator/en/mysql-administrator-backup-advanced-options-outp...

however, the option affects wheter CREATE TABLE commands are used or not

either the documentation is wrong or this is a bug in MySQL Administrator

How to repeat:
-

Suggested fix:
drop the 'No CREATE' option;

add two new options 'use CREATE DATABASE' and 'use CREATE TABLE' and enable them per default; both options make sense, and mysqldump also implemented both (--no-create-info and --no-create-db)

fix documentation

PS: a option beginning with 'no' just causes confusion; if the option is disabled, we have two negations in the sense of -(-1)=+1

Thank you for the bug report.

The documentation is wrong. Option 'no CREATEs' by design controls only creation of tables. Creation of databases is controlled by 'Don't write full path' check-box.

It's been several years. Could you please fix the documentation?

"No CREATEs will suppress CREATE DATABASE statements. This can be useful if you need to restore the data to a different database than it was backed up from."

Another note/bug. "No CREATEs" works differently on MySQL Administrator for Windows than it does on Mac. On Mac it means don't add syntax to create Tables. On Windows it means don't add syntax to create Tables OR Databases.