I followed the documentation for 5.x but using the 6.x-2.x module. When I did a dump with the default config, it created an sql file for each table in databases/development rather than a standalone development.sql like I'm used to seeing.

Is this just because it's 6.x-2.x or am I doing something wrong?

Comments

JStarcher’s picture

JStarcher commented
Status: Active » Closed (works as designed)

Doh, should have read the release description, sorry.

This is using an entirely different approach to dumping and restoring. The 1.x version treats the database dumps as a single file, while 2.x is dumping every table and data as separate files. This allows much easier manipulation of files that will be faster to perform. Also, on large databases it will allow an easier opportunity to dump and restore only the required tables, which will be significantly faster.

Merging branches and with other developers should be superior this way... that is... if I can get it working :)

ceardach’s picture

ceardach commented
Status: Closed (works as designed) » Closed (fixed)

Yup! One of the reasons why I made it a 2.x branch was because I was entirely changing the dumping method.