Ruby on Rails
Saturday, December 5, 2015
Hi there,
I did the following using git in my rails application:
- creating branch a from master
- creating a migration
- using it on development
- creating a branch b from master
- making fixes whih include a new migration (the migration number is higher than on branch a)
- using it on development
- merging b to masster
- using master on production
- migrate on master works fine
-> everything fine till here
- merging master to branch a because of this important changes, so a is ahead of master not just a fork.
- now I put a copy of the production database to the development database
of course now the migration first created in a is not there, because it never reached master, but because it has a lower number than the last migration in master, rake db:migrate does not do anything.
now I tried to give the migration file a newer number, but then rake db:migrate tells me the table created in the migration would be allready there. but looking directly inside the database it is not there.
What do I miss and how can I fix this?
note: it could also be because i just changed the db schema from sqlite to mysql2.
it seems that rake db:migrate works on the sqlite, not on thy msql table?
Thanks for help,
Martin
-- I did the following using git in my rails application:
- creating branch a from master
- creating a migration
- using it on development
- creating a branch b from master
- making fixes whih include a new migration (the migration number is higher than on branch a)
- using it on development
- merging b to masster
- using master on production
- migrate on master works fine
-> everything fine till here
- merging master to branch a because of this important changes, so a is ahead of master not just a fork.
- now I put a copy of the production database to the development database
of course now the migration first created in a is not there, because it never reached master, but because it has a lower number than the last migration in master, rake db:migrate does not do anything.
now I tried to give the migration file a newer number, but then rake db:migrate tells me the table created in the migration would be allready there. but looking directly inside the database it is not there.
What do I miss and how can I fix this?
note: it could also be because i just changed the db schema from sqlite to mysql2.
it seems that rake db:migrate works on the sqlite, not on thy msql table?
Thanks for help,
Martin
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/e67aa271-e89d-447a-b58b-e6f467237527%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment