change gpkg schema without users having to delete and re-download project

Open
#34 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend, databases

Research direction

The issue describes changing GeoPackage project schemas without requiring users to delete and re-download projects, but names no files, tests, or entry points. Start by tracing how the server handles project downloads and schema changes. Done means supported table or field changes propagate without the current delete-and-redownload workflow.

Written by the indexing model from the issue text.

Description

enhancement

--Feature request--
It would be great to be able to add tables and/or change/add fields in gpkg's without the user having to delete and re download projects.

Currenty we let our users know well in advance via whatsapp and email that we are planning a major project change and that they will have to delete and redownload projects on a certain date. we then remind them on a daily basis and come the specified date... more than half of them did not do it and we have conflicts everywhere.

So if possible this would be a game changer. 🤙🏻💪🏻

Dominant language
Python
Stars
179
Forks
71
Avg merge
1d 4h
Merged PRs (30d)
10

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MerginMaps/server

All issues in MerginMaps/server

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.