MerginMaps / MerginMaps/mobile
NULL values saved when not allowed
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
This might be plugin or QGIS issue.
What happens
Input can save and upload Null value in field where is Null not allowed constraint
How to reproduce
Download (or clone) and open project input-testing/tc05_decimals from public Mergin
Record a point, go to Null values tab, do not set anything to Null not allowed field.
To be able to save the point, go to deafult values tab and set red field to 10.
You can save the point even it does not meet the constraint.
(If you cloned the project, you can check in QGIS the value is Null and that Allow NULL in properties is unchecked.)
Screenshots / screencast
---
Author of the original task:
Herman Snevajs
Original tags:
migrate to github
Original task URL: https://app.clickup.com/t/862kfp29u
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 issue with the public Mergin project input-testing/tc05_decimals and verify the resulting field in QGIS, as described in the report. Trace the mobile app's handling of QGIS NULL constraints and default values; done means a record cannot be saved or uploaded when a constrained field remains NULL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100