MerginMaps / MerginMaps/mobile
Wrong feature count for PostgreSQL/PostGIS layers/tables
Open
Nobody has claimed this yet.
bug
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
The feature count is always -1 for such datasources, while is ok for GPKGs.
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
The issue names no files, tests, or entry points. Start by tracing feature-count handling for PostgreSQL/PostGIS layers and compare it with the working GPKG path; done means PostgreSQL/PostGIS counts are no longer -1 while GPKG behavior remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, postgresql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100