Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Export on per table basis #61
I'm not sure if this kind of feature is important for others, but I would find it helpful if the export (in my case, using mysql) created an SQL file per table instead of one combined file. This would be helpful for several reasons:
I can live without this and I can see potentially the feature complicating the archival and sync steps but I put it out there in case the idea benefits others too.
If I were to suggest how to change the configuration directive, I would make it look sort of like this:
The trick is how to reconcile this with the filename directive. Do we add a mask for it, like filename="foo-tablename.sql" or have it automatically prepend the table name to the output file if the separatetables variable is set? I tend to prefer the latter but I'm easy.
I think the target would be the wrong place to configure a MySql behaviour
<target dirname="backup/mysql" filename="mysqldump-%Y%m%d-%H%i.tar" compress="bzip2"/> <source type="mysqldump"> <option name="filePerTable" value="true">
Seems to be the better solution.
Mysqldump should create a directory /backup/mysql/mysqldump-%Y%m%d-%H%/
So we end up with one file for any possible sync.