migrate away from vdm
Open
Core CKAN
technical debt
- Dominant language
- No language data
- Stars
- 39
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
IIUC vdm is holding us back from upgrading to a more recent SQLAlchemy. Its revision tables also denormalize our data and make writing efficient queries difficult.
Is anyone familiar with alternate revisions-in-the-database projects? Can we integrate revisions into activities somehow?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing how vdm's revision tables currently denormalize data and constrain the SQLAlchemy upgrade. Investigate alternate revisions-in-the-database projects and whether revisions can integrate with activities. Done would be a decided migration approach with its query and data-model implications documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlalchemy
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100