# Segregated migrations?

**URL:** <https://www.ruby-forum.com/t/segregated-migrations/101132>\
**Category:** Radiant CMS\
**Created:** [August 3, 2006, 1:09pm UTC](https://www.ruby-forum.com/t/segregated-migrations/101132 "2006-08-03T13:09:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![James\_MacAulay](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/4af34b/32.png) [@James\_MacAulay](https://www.ruby-forum.com/u/James_MacAulay)\
**Post date:** [August 3, 2006, 1:09pm UTC](https://www.ruby-forum.com/t/segregated-migrations/101132/1 "2006-08-03T13:09:47Z")

</div>

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  
this?

Thanks,  
James

---

<div class="post-metadata">

**Author:** ![James\_MacAulay](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/4af34b/32.png) [@James\_MacAulay](https://www.ruby-forum.com/u/James_MacAulay)\
**Post date:** [August 3, 2006, 1:11pm UTC](https://www.ruby-forum.com/t/segregated-migrations/101132/2 "2006-08-03T13:11:47Z")

</div>

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

Josh

---

<div class="post-metadata">

**Author:** ![James\_MacAulay](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/4af34b/32.png) [@James\_MacAulay](https://www.ruby-forum.com/u/James_MacAulay)\
**Post date:** [August 3, 2006, 2:23pm UTC](https://www.ruby-forum.com/t/segregated-migrations/101132/3 "2006-08-03T14:23:20Z")

</div>

Awesome, thanks.

James