First off, great module! There is one feature that would be great to have.

For restore, could there be an option to select that all tables in the database be dropped first (or drop database and recreate it new) and then the restore performed? I have a sandbox where I try out new modules that create new tables, and when I try to restore a backup from my actual site, only the saved tables will be dropped,recreated&filled, but the tables that were created by the modules I was trying out are still there.

I suspect many would find it useful if they could do a clean recreate so that only what's in the backup file is in the database and nothing else.

Comments

ronan’s picture

ronan commented
Version: 6.x-1.2 » 6.x-2.x-dev
Category: feature » task

That's not a bad idea, I'll put it on the todo list.

elijah lynn’s picture

elijah lynn
Location Portland, Oregon
commented

+1

jennycita’s picture

jennycita commented

+1

yareckon’s picture

yareckon commented

+1 (sorry if this is too old to +1)

Would be wonderful to be able to actually drop tables that don't exist in the restore... exactly for trying out modules.

frenkx’s picture

frenkx commented

You might want to try the solution at #1104012: On restore, provide option to drop all tables. Dropping all tables might lead to permission issues, the provided patch only deletes tables, that are not part of the backup.

yareckon’s picture

yareckon commented

I got bitten by this for 20 mins again last night. (i.e. bleary eyed me: "Why is this bug not going away? ...Oh, Why is this damn table here after a restore!?")

Having a option to delete tables that are not part of the backup is a great solution.

ronan’s picture

ronan commented
Issue summary: View changes
Status: Active » Closed (duplicate)

This is in progress here: #1104012: On restore, provide option to drop all tables