Releases: MerginMaps/db-sync
Releases · MerginMaps/db-sync
2.1.1
2.1.0
2.0.1
2.0
This is a major release with many improvements aiming towards better robustness and ease of use.
We are starting to provide a Windows executable (#99) that can be used from terminal,
so that Windows users do not need to worry about Docker or manual compilation anymore!
-
Minor changes in the YAML configuration file (#98):
- New required entry:
init_from
specifies whether the initialization is done from a database (db
)
or from a GeoPackage in a Mergin Maps project (gpkg
). Previously this was specified on the command
line when running the tool. - Removed entries:
geodiff_exe
(now using geodiff from PATH) andworking_dir
(now using TEMP/dbsync)
- New required entry:
-
Much easier way to restart synchronization (when the data schema has changed, or when initialization failed) - simply
add--force-init
command line option to let db-sync do the cleanup (#16) -
Configuration file can be specified on command line instead of the default
config.yaml
(#97) -
Logging improvements
-
Robustness fixes and improvements
- Check that PostGIS extension is available on init (#113)
- Clean up database if initialization fails (#90, #95)
- Quote schema names correctly, e.g. when using upper case characters (#54)
- Use project ID to check that the project is the same (#76)
- Handle push errors to avoid broken sync (#60)
- Warn if the working dir exists but it is empty on init (#75)
- Provide better error messages
-
Infrastructure improvements:
1.1.2
1.1.1
1.1.0
New features:
- Support for skipping table(s) within a schema, so users do not need to sync the whole schema (#62)
- Support for running multiple projects (connections) within one docker command (#66)
- Fixed support for UUID, decimal, numeric, char(N) and character(N) data types
Changes:
- Configuration has been changed - please see README.md for examples how to run it