Luca Lanteri

Hi. I have the same problem, I can't configure an existing schema to start with. I saw that the issue was labeled as bug. If it helps I could do...

Yes, the names seem corrects. May be the problem is in the initializing phase ? If I add by hand this comment to the base schema: {"name": "admin/db-sync", "version": "v0"}...

I've created the schema by hand because I've this previous error File "/mergin-db-sync/dbsync.py", line 651, in dbsync_init _geodiff_make_copy(config.db_driver, config.db_conn_info, config.db_schema_modified, File "/mergin-db-sync/dbsync.py", line 199, in _geodiff_make_copy _run_geodiff([config.geodiff_exe, "copy", "--driver-1", src_driver,...

Problem seem partially to due to starting data. If I change my real table with a very simple test table the base schema was created successfully, but this error remains...

Ok. The last problem was resolved by add some data to the test table. So the main problem remain my real data. I discovered some limits: 1) table must have...

Hi Martin, after some other tests it seems that changing data type from numeric(10,2) to real resolve also the problem of void table. Thanks and sorry for the noise

Confirm. Same problem for me.