MerginMaps / MerginMaps/db-sync
Allow configure the order used to synch tables back to postgresql
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 53
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
In a scenario where the postgresql/postgis data model has functions and triggers, then is also likely that the tables must be updated following a specific order. This also means that this https://github.com/MerginMaps/db-sync/issues/145#issuecomment-2838156727 should be fixed first, as dbsync fails if a table has a trigger.
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
No files or tests are named. Start by reading the referenced comment on issue 145 and trace the table synchronization path to understand the trigger failure and where table order is determined. Done means users can configure a required table order and synchronization succeeds for PostgreSQL/PostGIS models with functions and triggers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100