Segregated migrations?

Hi all,

If I want to put extra tables or columns into my Radiant app, can I
set up a separate line of migrations to take care of that without
mucking up future svn updates? I’m just thinking of all those
numbered migration scripts conflicting with each other if I make a
010_james_migration.rb and then svn update gives me
010_fancy_trunk_migration.rb. I’m assuming there’s a standard
solution here that I’m not aware of; what do people generally do for


Probably best to use the engines plugin and keep your migrations by
themselves in your own engine directory.


Awesome, thanks.


This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs