[TYPO3-team-core-v5] Migrations in FLOW3

[Tim Eilers]

Hi Karsten,

just said that on IRC but here it is more "persistent":

Migrations are a really cool idea, it seems like that FLOW3 and all it's
"children" take the best concepts of nearly everything :D

Karsten Dambekalns schrieb:
> Since a migration has up and down parts for going forth and back in
> time, it's easy to revert most things (see the ChangeAlbumYearToInteger
> migration example in the article linked above). Anyway, some stuff is
> irreversible, they say: really deleting stuff with drop_table and
> remove_column. Is it?

In Rails you can mark a migration as irreversible, is there a
possibility to add something like that to the FLOW3 solution, too?

A quote from IRC:
> k-fish: timdeluxe: yeah, you can throw an exception on going down -
> but then the data is already gone...

There should be a step before that, isn't that possible?

> This is where TYPO3 was right for quite some time, renaming things to
> zzz_deleted_foobar instead of dropping right away. Now, if we would
> rename them and include the timestamp from the migration file, we could
> even restore such stuff.

That is good if someone forces a irreversible migration.



Cheers,
Tim.