db-sync
db-sync copied to clipboard
MerginMaps
A tool for two-way synchronization between Mergin Maps and a PostGIS database
/var/lib/docker/overlay2/_$long-string$_/diff/tmp/dbsyc/.mergin/work-packages directory is not cleaned in docker container and can easily reach up to a million+ diff files which uses up inodes on Linux, so although I have, for example,...
Sometimes users modify structure of their database and this naturally breaks db-sync. It would be good to document how to restart db-sync when this happens. If the "source" is a...
It would be useful if the daemon would somehow notify admin when things go wrong (e.g. database schema has changed, unable to access project) - currently it just silently stops....
This is the traceback:  Just checked in `psql`: ```sql create schema "Hello"; select 'Hello'::regnamespace; -- error select "Hello"::regnamespace; -- error select '"Hello"'::regnamespace; -- works ``` So we'll just need...
With a remote PostgreSQL when doing --init-from-db, the initial copy from the main schema to base schema takes very long time.
When doing init from gpkg or from db, it would be useful to have an option to force remove: - working directory if it exists already - drop destination schemas...
It would be useful to have functionality that would take an existing QGIS project file (.qgs or .qgz) and convert references to map layer data providers from database to geopackage...
It seems that mergin python client does not have any timeouts set. In case of a temporary network connection issue, the sync daemon may freeze and hang forever. It would...
Metadata
Owner
Metadata
A tool for two-way synchronization between Mergin Maps and a PostGIS database