Skip to content

running migrations after conversion? #37

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
josh-m-sharpe opened this issue Oct 3, 2011 · 2 comments
Closed

running migrations after conversion? #37

josh-m-sharpe opened this issue Oct 3, 2011 · 2 comments

Comments

@josh-m-sharpe
Copy link

I've converted using file and then importing as well as directly into postgres.

After quickly poking around, I see my tables/columns are present, but running 'rake db:migrate' wants to run every migration in my app.

There are two odd things about this:

  1. It's as if the mySQL table schema_migrations didn't get converted to however postgres manages schema state.

  2. rake db:migrate -- about half of my migrations run fine. This is incredibly odd my first migration creates the "events" table, but that table already exists -- postgres doesn't blow up on that?

Anyways, I would expect that db:migrate would have to do nothing after converting the DBs -- did I skip something?

@josh-m-sharpe
Copy link
Author

Sorry, no idea why I assumed the context of ruby on rails -- let me dig a bit more as I bet the problem is with rails and not with your script.

@paazmaya
Copy link
Contributor

Closing as an old issue, that would seem to be out of date.
Feel free to re-open and update with comments against the master branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants