SQL dump files include partial table definitions

For Drupal 7 the latest .dev - Version works fine for me. Just as hint if you have any problems with broken dumps.

I have the same issue using the dev version on a local Drupal 7.17 installation. As said by nd987, this makes the module completely unusable.

Matthijs: Are you sure? The fix committed on May 26 2012 appears to work, though of course snapshots made with 1.0 will still be broken.

Can the maintainers create a 1.1 release? Really shouldn't have a known broken version as the recommended release.

1+ for new release, although https://drupal.org/node/901954 may be blocking the release.

Folks, regardless if this is fixed or not, of if there are other blocking issues, this problem deserves a big red-36px-font box on the module page warning people that the recommended release is completely broken and should not be used.

This is a grave issue. It's not only about the module not working properly. It's about complete loss of data (or, at least, loss of information that is very hard/time consuming to recreate, and that will allow you to get your site back).

This bug is nasty. It can ruin your site without you noticing. I don't know about you, but below is my most common use-case for this module:

snapshot 1 > develop something > snapshot 1+dev > rollback to snapshot 1

Do it using the recommended 7.x release and suddenly you cannot reset to neither snapshot 1 nor snapshot 1+dev. In other words, you'd better to have fresh backups handy... Been there, done that.

+1 for new release since the dev release is working.

My bad for suggesting in comment #5 that another issue #901954: file_directory_path() removed may be blocking the release. That issue does have a patch committed as a "stop-gap measure". And a related issue #901996: file_directory_path() removed is open for feedback on the patch.

Edited links above to show issue title and status.

It is entirely contradictional to have a completely broken "recommended" release and a (better) working -dev... , so either new release, or at least remove the recommended release with a project page warning while waiting for a proper release.

Please just tag a new release. There is no reason to wait.
The dev release works and the current release is just egg on the face of this useful module.
It's also the first module I would reach for when testing drupal 8, but it's not on everyone's priority list.

I would also suggest commit of #1153206: Full URI not passed to demo_admin_settings_validate prior to tagging a new release.

I have, through the use of the release, just broken my site.

As I am a terrible person and rarely take backup of my sites before they launch, I am at a complete loss. The module have, however, created a dump, which, according to this issue, isn't working without a lot of manual work.

Now, if I was willing to put in this work to recreate the database, how would I go about doing that?

EDIT: Got it working after a lot of manual work. Essentially what's missing is all the information regarding the tables, so you'd have to create them manually or let Drupal do the work. Then it's pretty much just copy and paste the insert statement into your favourite SQL client.

@trillex Good news. Now that you have your data and a backup :-) would you consider testing the dev version?

Dev worked for me too.

The fix committed on May 26 2012 appears to work, though of course snapshots made with 1.0 will still be broken.

I guess 'snapshots made with 1.0 will still be broken' would warrant it's own issue.

So this is actually fixed in dev, so nothing left in this thread to do, so it probably should be closed.

I have created #2505023: Time for new release of demo module, please. for the release request.