# Re: Rails migration issue

**URL:** <https://www.ruby-forum.com/t/re-rails-migration-issue/97570>\
**Category:** Rails\
**Created:** [July 8, 2006, 12:25am UTC](https://www.ruby-forum.com/t/re-rails-migration-issue/97570 "2006-07-08T00:25:46Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![sgoodwin](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/f05b48/32.png) [@sgoodwin](https://www.ruby-forum.com/u/sgoodwin)\
**Post date:** [July 8, 2006, 12:25am UTC](https://www.ruby-forum.com/t/re-rails-migration-issue/97570/1 "2006-07-08T00:25:46Z")

</div>

-----BEGIN PGP SIGNED MESSAGE-----  
Hash: SHA1

Ok, so rake migrate --trace gets you this:

Khavi:~/Documents/WebCode/rails/clickcaster sgoodwin$ rake migrate –  
trace  
(in /Users/sgoodwin/Documents/WebCode/rails/clickcaster)  
\*\* Invoke migrate (first\_time)  
\*\* Invoke db:migrate (first\_time)  
\*\* Invoke environment (first\_time)  
\*\* Execute environment  
\*\* Execute db:migrate  
\*\* Execute migrate

then it stops, heh.  
-----BEGIN PGP SIGNATURE-----  
Version: GnuPG v1.4.3 (Darwin)

iD8DBQFErt9QrXJnpd8Tr7MRAuS0AJ9cw2B/07x2TJWR17W5Ku3mXjIXEwCgi+zM  
9Kp2HHd7dvfDXT565751yqg=  
=8TpW  
-----END PGP SIGNATURE-----

---

<div class="post-metadata">

**Author:** ![sgoodwin](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/f05b48/32.png) [@sgoodwin](https://www.ruby-forum.com/u/sgoodwin)\
**Post date:** [July 8, 2006, 12:32am UTC](https://www.ruby-forum.com/t/re-rails-migration-issue/97570/2 "2006-07-08T00:32:02Z")

</div>

On Fri, 2006-07-07 at 17:25 -0500, Samuel Goodwin wrote:

> \*\* Invoke db:migrate (first\_time)  
> \*\* Invoke environment (first\_time)  
> \*\* Execute environment  
> \*\* Execute db:migrate  
> \*\* Execute migrate
> 
> then it stops, heh.

* * *

what’s the value in the schema\_info table?

Craig

---

<div class="post-metadata">

**Author:** ![sgoodwin](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/f05b48/32.png) [@sgoodwin](https://www.ruby-forum.com/u/sgoodwin)\
**Post date:** [July 8, 2006, 12:56am UTC](https://www.ruby-forum.com/t/re-rails-migration-issue/97570/3 "2006-07-08T00:56:37Z")

</div>

Since it’s version=0, it won’t be able to create tables in migrations  
that already exist and you can manually change it to where it should be  
but recognize that if you migrate backwards, you lose data. HINT - back  
up entire database before doing anything destructive.

Craig

---

<div class="post-metadata">

**Author:** ![sgoodwin](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/f05b48/32.png) [@sgoodwin](https://www.ruby-forum.com/u/sgoodwin)\
**Post date:** [July 8, 2006, 12:41am UTC](https://www.ruby-forum.com/t/re-rails-migration-issue/97570/4 "2006-07-08T00:41:14Z")

</div>

-----BEGIN PGP SIGNED MESSAGE-----  
Hash: SHA1

Schema info version=0

- –Samuel

On Jul 7, 2006, at 5:29 PM, Craig W. wrote:

> > \*\* Invoke migrate (first\_time)  
> > Craig
> 
> * * *
> 
> Rails mailing list  
> removed\_email\_address@domain.invalid  
> [http://lists.rubyonrails.org/mailman/listinfo/rails](http://lists.rubyonrails.org/mailman/listinfo/rails)

-----BEGIN PGP SIGNATURE-----  
Version: GnuPG v1.4.3 (Darwin)

iD8DBQFEruKrrXJnpd8Tr7MRAonqAKDb0Iw4/kICojRZrEHDKUV1mRuRywCeKxjO  
cFidMjpEoFqgNnn6zwbNMKs=  
=aJkc  
-----END PGP SIGNATURE-----

---

<div class="post-metadata">

**Author:** ![sgoodwin](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/f05b48/32.png) [@sgoodwin](https://www.ruby-forum.com/u/sgoodwin)\
**Post date:** [July 8, 2006, 1:08am UTC](https://www.ruby-forum.com/t/re-rails-migration-issue/97570/5 "2006-07-08T01:08:57Z")

</div>

I would swear that we are talking the same language anyway…good luck

Craig

---

<div class="post-metadata">

**Author:** ![sgoodwin](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/f05b48/32.png) [@sgoodwin](https://www.ruby-forum.com/u/sgoodwin)\
**Post date:** [July 8, 2006, 1:02am UTC](https://www.ruby-forum.com/t/re-rails-migration-issue/97570/6 "2006-07-08T01:02:48Z")

</div>

-----BEGIN PGP SIGNED MESSAGE-----  
Hash: SHA1

I wrote the migrations to check the database in question first and  
only try to add columns/tables when that column/table wasn’t there  
already. I’ve tested this on snapshots of our production database  
numerous times. The problem now is that when I try to run these  
migrations for our production server (database is on another box)  
stops before it does anything, as you can see from the pasted output  
I gave earlier.

- -Samuel

On Jul 7, 2006, at 5:54 PM, Craig W. wrote:

> > -----BEGIN PGP SIGNED MESSAGE-----
> > 
> > > > Hash: SHA1  
> > > > \*\* Invoke environment (first\_time)
> > > 
> > > * * *
> > 
> > -----END PGP SIGNATURE-----
> > 
> > * * *
> > 
> > Rails mailing list  
> > removed\_email\_address@domain.invalid  
> > [http://lists.rubyonrails.org/mailman/listinfo/rails](http://lists.rubyonrails.org/mailman/listinfo/rails)
> 
> * * *
> 
> Rails mailing list  
> removed\_email\_address@domain.invalid  
> [http://lists.rubyonrails.org/mailman/listinfo/rails](http://lists.rubyonrails.org/mailman/listinfo/rails)

-----BEGIN PGP SIGNATURE-----  
Version: GnuPG v1.4.3 (Darwin)

iD8DBQFErud2rXJnpd8Tr7MRAjloAKDs/IaVceYeIb9BMCIk0SpqaxWjzACgkDnz  
8+HBLdx3NHIZjNIqRJSl0+k=  
=gKTw  
-----END PGP SIGNATURE-----