Change in Mergin QGIS not showing in DB
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 15/100
Research direction
No source file or test is named. Start by reproducing the Mergin-to-PostGIS sync with the daemon running and with --force-init, then compare the behavior when the daemon is stopped; done means identifying why normal synchronization stops and clarifying whether the daemon must remain running during edits.
Written by the indexing model from the issue text.
Description
Hi, I have config the link bewteen Mergin GPKG layers in QGIS to my schemas in postgis DB.
I noticed at first my change synced to server that also pushed to postgis, but later, it stop update.
I have to run daemon again with --force-init to get the changes. What I did wrong that caused this?
I am new to dbcync, please let me know if anything I did is wrong.
Also, can I ask if I have to have daemon keep running in the background everytime when I edit a Mergin project?
I tested with running and not running but the result is the same.
Thank you for your time, I have also raise this question to support team by email last Thursday afternoon and I have raise this question in Slack this morning. Will tidy my posts when I heard back from any of the threads.
Lei
- Dominant language
- Python
- Stars
- 53
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MerginMaps/db-sync
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MerginMaps/db-sync#184 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
MerginMaps/db-sync#185 · 1 comment ·
-
db-sync enters an infinite drop/recreate loop when geodiff init fails on invalid source geometries Open
Difficulty 4/5 3-5 days Newbie friendliness 42/100
MerginMaps/db-sync#182 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
MerginMaps/db-sync#181 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
MerginMaps/db-sync#179 · 3 comments ·
All issues in MerginMaps/db-sync
Similar issues
-
triage/confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/agentscope#2775 ·
-
comp/desktop P3 type/bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
NousResearch/hermes-agent#118866 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100