db sync fails to start
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by reproducing the failure with DB-SYNC 2.1.1 on Windows against a PostgreSQL table using row-level security, then compare it with a table using a UUID key. Use the reported duplicate ogc_fid error and the empty UPDATE ... SET WHERE statement as the completion criteria: synchronization should start without either SQL error.
Written by the indexing model from the issue text.
Description
I actually experiencing two type of issues. I am using DB-SYNC 2.1.1 on windows.
I have couple of tables in a database and I am actively use row level security, to modify the availability of data to field users.
Whenever I try to sync a table with activated row level security the db sync fails as it tries to add the id column two times:
Error: postgres cmd error: ERROR: column "ogc_fid" specified more than once
so I removed all the privileges setup, it did fail. I tried with postgres user it did fail. I removed my original id column and added uuid field with uuid_generate_v4() this helped to generate another error
LINE 1: UPDATE "public_db_sync"."chambers_mergin" SET WHERE "uuid2"...
^
SQL:
UPDATE "public_db_sync"."chambers_mergin" SET WHERE "uuid2" = 'ffdc0ee4-6fd8-4e90-a5e3-32a975efc37c'
any help would be much appreciated
- Dominant language
- Python
- Stars
- 53
- Forks
- 25
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 ·
-
Build in CI pipelinePossibly taken @varmar05 claimed this 4 days ago. Open
MerginMaps/db-sync#189 · 1 assignee ·
-
Prevent duplicated sign in from db-syncPossibly taken @varmar05 claimed this 4 days ago. Open
MerginMaps/db-sync#188 · 1 comment · 1 assignee ·
-
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 geometriesOpen
Difficulty 4/5 3-5 days Newbie friendliness 42/100
MerginMaps/db-sync#182 ·
All issues in MerginMaps/db-sync
Similar issues
-
tool-calling
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
vllm-project/vllm#59838 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
raullenchai/Rapid-MLX#4042 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 92/100
transitmatters/mbta-slow-zone-bot#70 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
litestar-org/advanced-alchemy#811 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day