MySQL Data Dumper

MySQL Data Dumper 0.6.0

  1. Series 0.6
  2. 0.6.0

Milestone information

Project:
MySQL Data Dumper
Series:
0.6
Version:
0.6.0
Released:
 
Registrant:
Max Bubenick
Release registered:
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
10 Max Bubenick
Blueprints:
2 Implemented
Bugs:
9 Fix Released

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon mydumper-0.6.0.tar.gz (md5, sig) mydumper 0.6.0 source code 990
last downloaded 15 weeks ago
Total downloads: 990

Release notes 

This is the first 0.6 series release, with new features and bug fixes, see changelog for details

Changelog 

View the full changelog

New features:
 - Consistent backups with less locking
  This new feature consist on locking all non-innodb tables with the dumping threads at the begining so in this way we can unlock the flush tables with read lock earlier and no need to wait until all that tables were dumped. You can take advantage of this feature when you have big archive or myisam tables.
 - File size chunks
  Now you can split tables dump into different files with fixed size. This is usefull to reduce storage capacity needed to keep history backups by using hardlinks. Think on big "log" tables or tables where old data didnt change, now you will be able to hardlink back those chunks.

Fixed Bugs:
 #1250269 ensure satetement is not bigger than statement_size
 #827328 myloader to set UNIQUE_CHECKS = 0 when importing
 #993714 Reducing the time spent with a global read lock
 #1250271 make it more obvious when mydumper is not successful
 #1250274 table doesnt exist should not be an error
 #987344 Primary key name not quoted in showed_nulls test
 #1075611 error when restoring tables with dashes in name
 #1124106 Mydumper/myloader does not care for 0-s in AUTO_INCREMENT fields
 #1125997 Timestamp data not portable between servers on differnt timezones

2 blueprints and 9 bugs targeted

Blueprint Priority Assignee Delivery
Consistent backups with less locking Consistent backups with less locking 1 Undefined Max Bubenick  11 Implemented
File size chunks File size chunks 1 Undefined Max Bubenick  11 Implemented
Bug report Importance Assignee Status
987344 #987344 Primary key name not quoted in showed_nulls test 3 High Max Bubenick  10 Fix Released
1075611 #1075611 error when restoring tables with dashes in name 3 High Max Bubenick  10 Fix Released
1125997 #1125997 Timestamp data not portable between servers on differnt timezones 3 High   10 Fix Released
1124106 #1124106 Mydumper/myloader does not care for 0-s in AUTO_INCREMENT fields 4 Medium Max Bubenick  10 Fix Released
1250269 #1250269 ensure statement is not bigger than statement_size 5 Low Max Bubenick  10 Fix Released
827328 #827328 myloader to set UNIQUE_CHECKS = 0 when importing 6 Wishlist Max Bubenick  10 Fix Released
993714 #993714 Reducing the time spent with a global read lock 6 Wishlist Max Bubenick  10 Fix Released
1250271 #1250271 make it more obvious when mydumper is not successful 6 Wishlist Max Bubenick  10 Fix Released
1250274 #1250274 table doesnt exist should not be an error 6 Wishlist Max Bubenick  10 Fix Released
This milestone contains Public information
Everyone can see this information.