MerginMaps / MerginMaps/db-sync
Database tables with inheritance do not work
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 53
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
It looks like when the database uses inheritance, db-sync / geodiff get confused about the table schema and init fails. We should either detect this and fail early saying that this is not supported, or fix it...
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 initialization with a PostGIS database whose tables use inheritance, then trace how db-sync and geodiff inspect the table schema. Done means either inherited tables are supported correctly or initialization fails early with a clear message that inheritance is unsupported.
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
- 35/100