Migrations works if you skip numbers, you can add your stuff with a really high number like '050_create_calendar' and you should be safe, from future radiant migration conflicts...
>
> 2. Currently I'm handling migrations on my own models by just
> generating them directly in the Radiant app. I figure I'll have to
> do some migration re-numbering when a new Radiant release includes
> it's own migrations. Anybody have a better solution for handling
> migrations of custom models from within a plugin or without
> interfering with the Radiant installation?
>
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
