MerginMaps / MerginMaps/db-sync
Warn if a table does not have integer primary key
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 53
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
GeoPackage (as of v1.4.0) require that vector and attribute tables have integer primary keys (see requirement 29 and 119 in https://www.geopackage.org/spec140/). It would be good to check during init whether the tables we are going to sync have integer primary keys - and if not, report that to the user.
The sync will probably work fine even with non-integer primary keys, but such .gpkg files may cause interoperability issues, so this should be avoided.
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 source file or test is named in the issue. Start by tracing the initialization path that determines which tables will be synchronized, then inspect how their primary-key metadata is read. Done means users are warned when a selected table lacks an integer primary key, with behavior aligned to GeoPackage requirements 29 and 119.
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
- 45/100