# Circumventing migrations **URL:** \ **Category:** Rails\ **Created:** [May 18, 2007, 5:07am UTC](https://www.ruby-forum.com/t/circumventing-migrations/104451 "2007-05-18T05:07:08Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![em00guy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/0ea827/32.png) [@em00guy](https://www.ruby-forum.com/u/em00guy)\ **Post date:** [May 18, 2007, 5:07am UTC](https://www.ruby-forum.com/t/circumventing-migrations/104451/1 "2007-05-18T05:07:08Z")
Hello everyone. I’m just beginning my journey with rails and I have many questions though I’ll start with just one. I was wondering what happens if you undermine a migration by changing the database schema manually. For example. I generate a model and in the first migration I create a table with an fname and lname column. I then manually remove the lname column using my favorite SQL administration tool. Forgetting that I’ve made that manual alteration I then create a second migration that adds and email column. When i apply that migration will the model be aware that the db structure was modified outside of the migration sequence and re-apply the missing column? Thanks much. ---
**Author:** ![em00guy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/0ea827/32.png) [@em00guy](https://www.ruby-forum.com/u/em00guy)\ **Post date:** [May 18, 2007, 5:24am UTC](https://www.ruby-forum.com/t/circumventing-migrations/104451/2 "2007-05-18T05:24:10Z")
> I was wondering what happens if you undermine a migration by > changing the database schema > manually. Don’t do that. You’ll be happier. ---
**Author:** ![em00guy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/0ea827/32.png) [@em00guy](https://www.ruby-forum.com/u/em00guy)\ **Post date:** [May 18, 2007, 7:09am UTC](https://www.ruby-forum.com/t/circumventing-migrations/104451/3 "2007-05-18T07:09:16Z")
No it won’t.