Rails migrations issue

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

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

Hello,

I am a new developer at www.clickcaster.com and we’re having some
trouble with migrations.

When I tried to run the migrations on our database (which previously
hadn’t used migrations), nothing happens, it stops before it runs any
of the migrations.
However, when I try this on a blank database that is separate from
our main server the way our production stuff is setup, the migrations
run just fine.

Is there something in databases (mysql in these examples) that would
cause migrations to work like this?

iD8DBQFErtoOrXJnpd8Tr7MRAk3nAJ9IDmn4z207kKgHIIMf70NUkVBBRwCfTTOC
2Ooq2sYvJd08fuiLehOxFsE=
=AYiS

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

iD8DBQFErtpcrXJnpd8Tr7MRAlSvAKCpe6MQWRRh+O1g+lD1Cia2SHNwngCePVFE
XQloGn2BuQAB3P2KoDfvNNc=
=GuHO
-----END PGP SIGNATURE-----

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

trouble with migrations.

When I tried to run the migrations on our database (which previously
hadn’t used migrations), nothing happens, it stops before it runs any
of the migrations.
However, when I try this on a blank database that is separate from
our main server the way our production stuff is setup, the migrations
run just fine.

Is there something in databases (mysql in these examples) that would
cause migrations to work like this?


try adding --trace to your migration statement for a ‘verbose’ display
of what is happening but I am guessing that your database doesn’t have a
‘schema_info’ table that clues it in as to which migration it currently
resides at.

Craig

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