propelorm/Propel2 — Issue #145: [RFC] Migrations
Author: havvg
Created: 2012-02-27 10:29:18+00:00
State: open

A main issue I see with the current implementation of the migration: they are streamlined, not allowing branching.

Each migration should be tracked separately, so one could branch the source add migrations to it, merge it back and run all migrations. This should also work when merging more than two branches!

The migration table should only insert every migration that has been done (up) and remove its entry if reverted (down).
In addition, it could be nice to know, when a certain migration has been done by adding a `created_at` column to the table.