MerginMaps / work-packages

Mergin Maps Work Packages: manage field surveys for multiple teams
MIT License
7 stars 4 forks source link

Option to drop some tables #24

Open dracic opened 3 years ago

dracic commented 3 years ago

wp.py line 299

TODO: drop tables that are not listed at all (?)

Suggestion - not listed tables should not be dropped. My thoughts about that... Let's assume we have a lot of tables, but a lot of them won't be filtered. We need all data (read only perhaps) for all users. It would be an overhead to list all tables. Let's assume that all data is needed.

wonder-sk commented 3 years ago

You're right - both options are valid - to keep some tables intact, and to drop some tables from WPs. That's one of the reasons why the method was introduced for tables - right now the only method is filter-column, but we could other filtering options, or to have an option to drop the particular table (and I agree, the best default is to keep tables).

There could be also another option that would control sync direction - right now we always sync both directions (master to WP, WP to master), but it would be useful in some cases to disable on direction.