DB Sync currently supports skip_tables to exclude tables from synchronisation.
It would be great to add an include_tables option so users can explicitly define which tables should be synced from the database.
This would be useful when tables are added to a PostgreSQL schema, but only specific ones are intended for MerginMaps sync.
It would also make the sync process safer. At the moment, if new tables are added to the schema, they may automatically become part of the sync process. This can cause unexpected behaviour or potentially break the sync if the new tables are not intended or ready to be synced.
Example:
include_tables:
- table_1
- table_4
- table_9
DB Sync currently supports
skip_tablesto exclude tables from synchronisation.It would be great to add an
include_tablesoption so users can explicitly define which tables should be synced from the database.This would be useful when tables are added to a PostgreSQL schema, but only specific ones are intended for MerginMaps sync.
It would also make the sync process safer. At the moment, if new tables are added to the schema, they may automatically become part of the sync process. This can cause unexpected behaviour or potentially break the sync if the new tables are not intended or ready to be synced.
Example: