Hi 

It happens to me from time to time that a table gets damaged when saving it. It happens to me mostly on SQL lined tables, but not only after saving an error message is shown.

The problem is that after such an incident, few BAD things happen:

·         You cannot open the table again in the backend. (Error).

·         Or you can open it, but it's empty.

·         All the work you put into configuring it is lost.

·         In some cases, all the HTML pages where the table was in don't load and display an error.

·         The only way to get the HTML pages live again is by deleting the table.

In my opinion, this is unacceptable! If there is a problem, the software should warn, but keep the previously saved version working!

The combination of the above with the lack of an import/export option is even more problematic.

When I work on a complicated table, from time to time, I duplicated the table so if something goes wrong, I can go back to an older working version, but I think there should be a solid solution within the plugin.

·         Not enabling to save a table that will generate an error. (always keep the last working version).

·         Having a proper Import/Export option to backup tables

·         Revision control for the last few saves.

·          

I am generally super happy with the plugin, and this is friendly feedback for future improvements!

Thanks!

One case for sure was when I changed the SQL query. I think it is sensitive to modifications in the query.

I am happy with the direction you mentioned. I think the plugin is awesome, but has too many small bugs that you must stabalize.

Keep up the good work!

OK. I underatnd that and I also understand that errors can occur in any system.

The more critical thing is that in a case of any error the previous working version of the table must remain and not overwriten unless the save is sucsusfull. And/or there should be a roleback option to previous versions