Provide a way to manage and migrate database schemas
Bug #250412 reported by
James Henstridge
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Storm |
Fix Released
|
Low
|
Free Ekanayaka | ||
Bug Description
In a way, this bug is in competition with bug 136559.
Storm should provide a way to manage the database schema, and move the schema forward as the code changes.
Both Launchpad and Landscape have developed infrastructure to do this (one based purely on SQL patches and the other on Python or SQL patches), so it'd be good to add this functionality to Storm directly.
It'd also be worth considering the schema migration support from Ruby on Rails for ideas.
Related branches
lp://staging/~free.ekanayaka/storm/schema-support
- Gustavo Niemeyer: Approve
- Jamu Kakar (community): Approve
-
Diff: 978 lines (+942/-0)7 files modifiedstorm/schema/__init__.py (+21/-0)
storm/schema/patch.py (+197/-0)
storm/schema/schema.py (+108/-0)
storm/zope/schema.py (+43/-0)
tests/schema/__init__.py (+20/-0)
tests/schema/patch.py (+383/-0)
tests/schema/schema.py (+170/-0)
| Changed in storm: | |
| importance: | Undecided → Low |
| status: | New → Confirmed |
Revision history for this message
| Free Ekanayaka (free.ekanayaka) wrote | #1 |
| Changed in storm: | |
| status: | Confirmed → In Progress |
| assignee: | nobody → Free Ekanayaka (free.ekanayaka) |
| Changed in storm: | |
| milestone: | none → 0.18 |
| Changed in storm: | |
| status: | In Progress → Fix Committed |
| Changed in storm: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
There is indeed some competition between this and Bug 136559, however I feel that they are orthogonal in principle. Ideally support for Bug 136559 should be built on top of this bug?