MerginMaps / MerginMaps/db-sync
handle automatically new table/field in schema
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 53
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
follow-up for https://github.com/MerginMaps/geodiff/issues/178
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 reading the linked geodiff issue 178 and compare its schema-change requirements with this repository's synchronization flow. The issue does not name files, tests, or acceptance criteria, so the expected handling of newly added tables or fields must be clarified before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100