-
Notifications
You must be signed in to change notification settings - Fork 18
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
Duplicate migration when migrating in Rails 3.2.20 #26
Comments
Are you getting this when trying to develop something for queue_classic_admin or when using it in your project? Just to be sure. If this is in one of your app, which is what I assume, how do you proceed to get it installed? |
I also got this same weird error in a Rails 4.2 app in my development environment. I was able to get the migrations to run on my test environment by recreating the test database with |
Interesting. If you could give some repro steps or app, it would be great. |
Sure, the main thing is you need to have some migrations that already exist in the database. Starting from a fresh database doesn't seem to trigger it. Here's some exact repro steps:
|
I don't know if it would fix it or not, but if it's the |
Hey, I don't have too much experience with Queue Classic. Hope not to be misleading. The error doesn't seem to be related to SQL and just to the mere fact that the migration is duplicated. The rake task copies the files to the rails application migration folder. Also, exists an initializer in /lib/queue_classic_admin/engine.rb that adds the migrations of this folder to the app folder. Aren't this two steps somehow incompatible?. When applying the migrations, rails will look in this two places, the rails application migrations folder and also the gem migrations folder, throwing the error. Pretty sure that I'm missing something, but I'd be very grateful if somebody can help me to understand better. Thanks to @abevoelker for the repro steps. |
I ran into the same issue with Rails 7. What's interesting is that once the queue_classic_admin gem is installed, rake db:migrate fails. That is without calling the rake task. I'm guessing that the duplication is self inflicted. The install rake task copies the internal AddIdToLater migration to the local migration directory. For some reason the source directory is also in the path for possible migration files.
|
Hey,
I'm using the support-v2 branch, creating the migrations for a rails 3.2.20 app.
Creation works fine, but migrating doesnt work:
I dont use the queue-classic-later gem and there are no duplicate migrations with this names.. but i still get this exception:
Any hints?
The text was updated successfully, but these errors were encountered: