The new restore does not create a non-existing filtered table during restore. This causes problems for the first restore, or whenever a new table that is filtered is added to the site.

Need to ensure that all tables are restored if they don't exist.

Comments

ceardach’s picture

ceardach commented

A work around is to do "./dbscripts/restore.php none" to have all tables restored.

jackalope’s picture

jackalope commented

Not sure if this is part of the same problem, but I've noticed that when I restore, my users table doesn't get restored; it's completely empty. This is true even when I do "./dbscripts/restore.php none." Other tables may also be experiencing this problem, haven't thoroughly checked. Is this part of this issue, or should I start a new issue? Thanks!

ceardach’s picture

ceardach commented

Jack, I ran a test on my local dev environment. I created a new user, erased my database, verified no tables remained, then restored. It restored my users table and retained my newly added user.

I'm going to say, then, that this is a different issue. Please post a new issue, and attach your config.inc file.

mnlund’s picture

mnlund commented

@jackaponte Are you using prefixes on your tables? I have seen this issue. Check in your data directory. In mine, if I use prefixes, I see a lot of files like this: prefix_tablename.sql and one users.sql file. This one is empty, when the prefix_users.sql file contains the data. I think the restore function are using the users.sql file, and therefore users are wiped. This is an issue posted before http://drupal.org/node/384390

hefox’s picture

hefox commented
Assigned: ceardach » hefox