MerginMaps / MerginMaps/db-sync
db sync fails to start
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 53
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
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
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.
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.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100