Provide a way to manage and migrate database schemas

Bug #250412 reported by James Henstridge on 2008-07-21
Affects Status Importance Assigned to Milestone
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

Changed in storm:
importance: Undecided → Low
status: New → Confirmed
Free Ekanayaka (free.ekanayaka) wrote :

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?

Changed in storm:
status: Confirmed → In Progress
assignee: nobody → Free Ekanayaka (free.ekanayaka)
Jamu Kakar (jkakar) on 2010-08-16
Changed in storm:
milestone: none → 0.18
Changed in storm:
status: In Progress → Fix Committed
Gary Poster (gary) on 2010-10-26
Changed in storm:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers