Symphony.

A new extension, “Dump DB” is now available for download. Comments and feedback can be left here but if you discover any issues, please post it on the issue tracker.

This extension will help you dump your complete Symphony CMS database into a file. It might come in handy when you start developing the same site on several machines or in collaboration with others.

Simply commit the generated file with the rest of your code and tell your collegues to import it into their database every time it updates.

99% of the code is taken from Alistairs Export Ensemble extension.

The difference between Dump DB and Export Ensemble is that Export Ensemble doesn’t dump all your tables but only the ones it knows about (default-fields and -data). Dump DB however dumps everything as long as it has the table prefix you chose on installation.

I must admit I haven’t yet tried “simply importing it into my database” but the export itself works flawlessly. ;-)

hm… so this could help when using the method of manually creating ensembles? without zip?

Thanks for this – I’ve been doing the same thing using phpMyAdmin for a while. I’ll give it a try.

hm… so this could help when using the method of manually creating ensembles? without zip?

Technically, the article you were referring to wasn’t about creating an ensemble but copying your Symphony copy. I am hoping this will help in exactly this case.

Dump DB updated to version 1.01 on 13th of March 2010

The data of tables sym_cache and sym_sessions won’t be dumped anymore, only their structure.

Dump DB updated to version 1.02 on 15th of March 2010

As it’s meant to be sent with the rest of the code anyway, the database is now being saved in /workspace/dump.sql instead of offering it for download.