When editing / updating a GPKG `last_change` column in gpkg_contents isn't correctly upheld
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by running the merger on a GeoPackage and inspect the gpkg_contents last_change value before and after an update. Review the GeoPackage specification and the merger entry point to determine which timestamp behavior is intended; done means the chosen behavior is implemented and the updated value can be verified after a write.
Written by the indexing model from the issue text.
Description
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Run the merger on any geopackage to update it. The last_change field won't be updated.
Expected behavior
Either update last_change to be the time of the last write to the table, or to be the data's original creation date.
Additional context
The last_change column as described in geopackage spec:
The last_change SHOULD contain the timestamp of when the content in the referenced table was last updated, in ISO8601 format. Note that since it is not practical to ensure that this value is maintained properly in all cases, this value should be treated as informative.
- Dominant language
- C#
- Stars
- 1
- Forks
- 2
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
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.
More from MapColonies/GpkgMerger
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 25/100
MapColonies/GpkgMerger#172 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 42/100
MapColonies/GpkgMerger#169 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
MapColonies/GpkgMerger#159 ·
-
enhancement
MapColonies/GpkgMerger#155 · 1 assignee ·
-
Feature Testing
Difficulty 4/5 3-5 days Newbie friendliness 25/100
MapColonies/GpkgMerger#151 ·
All issues in MapColonies/GpkgMerger
Similar issues
-
core dependencies
Difficulty 1/5 Under an hour Newbie friendliness 80/100
-
bug frontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
NavigationViewItemAutomationPeer implements IInvokeProvider but never advertises the Invoke pattern Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
unoplatform/uno#24629 ·
-
agentic-workflows Needs: Triage :mag: State: In-PR
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Down / Waiting for removal
Difficulty 2/5 1-3 hours Newbie friendliness 70/100