Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
when mysqldump was used to create INSERT or REPLACE statements with additional table-options, one unnecessary space was written to the dump for each INSERT or REPLACE
INSERT IGNORE INTO `test033` VALUES (1,'test test test'); |
note the 2 spaces between INSERT and IGNORE
motivation: when dumping databases without additional compression, this results in one unnecessary byte per row in dump-files which wastes disc space or creates unnecessay network traffic. my thesis is, because compressing dumps requires an additional manual step (as its not used per default), there will be a lot of db dumps beeing exported without compression - and these will benefit.