I had intended the third commit to be part of another pull request, but it ended up in this one...

Commit 2d56c87 adds a flag to save extra data when exporting table definitions. I had an issue where field formats such as dropdown lists or checkboxes would be lost on reimport, and this fixes that issue.

Dropping tables is fairly dangerous, I wonder if we should provide some kind of safety mechanism to prevent accidents

I suggest adding a config to prefix the existing table, or delete it if empty. A prefix would be better than a suffix to keep the renamed tables together for easy deletion.

I'd probably er on the side of crashing out hard if there's a clash, but it's probably worth canvassing the opinion of regular contributors and ideally users if we can work out how to!

Hi,
I am starting to use your package - very nice idea, by the way. It looks to me that the behavior here should be to TRY to copy the data from table EXAMPLE to EXAMPLE1 (using a select into or something similar), if it fails it leaves both copies with a warning message; if it is succeeded, delete EXAMPLE, rename EXAMPLE1 to EXAMPLE. I can implement this if everyone agrees. As the code is now, we are getting a lot of tables1 without sense (sorry if I miss something).
A Database backup before any importAllSource, should be a good practice... it is data after all, not codebase.

this does seem like a staging table scenario. You createa staging table if it succeeds delete the others and then do a rename.