-
Notifications
You must be signed in to change notification settings - Fork 227
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
DB migrations are being cached even after using setting migrations timeout to zero #465
Comments
You need to be more specific in what you are doing and what you are getting. I.e. specific commands, code changes and error messages. For now it's totally puzzling for me what it is this about. |
I am using Cacheops = 6.1 and Django = 3.1.5 , I haven’t initialised Cacheops with wildcard or neither have used any models with django prefix but despite it I suspect it's caching Django migrations table because whenever we add any field in the models that we are caching it throws an error (1054, "Unknown column 'portfolio_programme.course_sub_category' in 'field list'") |
What makes you believe cacheops has anything to do with this? Especially if you didn't even cache anything. |
As we disabled cacheops it worked fine. |
Ok, you still need to be more specific. Like what actually you doing: commands, code changes, errors with stack traces. Including how do you disable cacheops. |
Also did you try updating cacheops to the latest version? |
If we add a new column in a table and then try ti run server or makemigrations or to migrate it shows key not available in query list . After looking we found out about db migrations being cached but when we tried to set the migration timeout to zero still the same issue persists.
The text was updated successfully, but these errors were encountered: