MerginMaps / MerginMaps/mobile
App ignores the "descending" order for a date/time field of a child table
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
**Description**
In a QGIS relation, the child records/features are set to be shown in a descending manner, using a date/time field and in QGIS Desktop this works ok
Not so much in MM App, where the order seems to be always ascending
**Application (+ app version, build, operating system)**
2026.3.2 Android 16
**Steps to reproduce**
See above
**Expected results**
MM App to behave as QGIS Desktop.
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 the reported QGIS relation with a date/time field configured for descending child-record order on Android 16, then compare the result with QGIS Desktop. Trace how the mobile app reads and applies the relation ordering; done means child records follow the configured descending date/time order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, cpp
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100