-
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Relation "custom_filters" does not exist #8007
Comments
Workaround: |
For me the fix was to first upgrade to v2.4.1 and then from v2.4.1 to v2.4.3 |
Yeah, the migration scripts use the |
I was having the same problem (updating from v2.4.0 to v2.4.3), and @progval's solution worked for me. Thanks ! |
I was having this problem too but @progval's workaround did the trick 👍 One note, if you're on Docker like I am, you have to run the mv db/migrate/20180628181026_create_custom_filters.rb db/migrate/20180528141302_create_custom_filters.rb
docker-compose build
docker-compose run --rm web rails db:migrate Thanks again @progval ! |
Include a dummy Account class in the migration script containing only the attributes relevant to the migration in order to not rely as much on the codebase being in sync with the database schema.
…n#8170) Include a dummy Account class in the migration script containing only the attributes relevant to the migration in order to not rely as much on the codebase being in sync with the database schema.
…n#8170) Include a dummy Account class in the migration script containing only the attributes relevant to the migration in order to not rely as much on the codebase being in sync with the database schema.
Does the OTOH I tried cherry-picking the "official" fix instead (cbc2e6b) and the migration failed:
|
@nolanlawson once the migrations have run, they don't run again as long as you have your database (ActiveRecord keeps a table of which migrations it's run before), so those files are essentially just ignored for your instance from here on out. |
@nolanlawson no, there shouldn't be any downside to it. |
…n#8170) Include a dummy Account class in the migration script containing only the attributes relevant to the migration in order to not rely as much on the codebase being in sync with the database schema.
…n#8170) Include a dummy Account class in the migration script containing only the attributes relevant to the migration in order to not rely as much on the codebase being in sync with the database schema.
…n#8170) Include a dummy Account class in the migration script containing only the attributes relevant to the migration in order to not rely as much on the codebase being in sync with the database schema.
…n#8170) Include a dummy Account class in the migration script containing only the attributes relevant to the migration in order to not rely as much on the codebase being in sync with the database schema.
…n#8170) Include a dummy Account class in the migration script containing only the attributes relevant to the migration in order to not rely as much on the codebase being in sync with the database schema.
While running
db:migrate
for v2.4.3, I'm getting this error:master
(If you're a user, don't worry about this).The text was updated successfully, but these errors were encountered: