Skip to content
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

Closed
shivambalwani0704 opened this issue Oct 22, 2023 · 6 comments

Comments

@shivambalwani0704
Copy link

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.

@Suor
Copy link
Owner

Suor commented Oct 22, 2023

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.

@shivambalwani0704
Copy link
Author

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'")
And then to make migration I need to disabled cache and then perform it

@Suor
Copy link
Owner

Suor commented Oct 23, 2023

What makes you believe cacheops has anything to do with this? Especially if you didn't even cache anything.

@shivambalwani0704
Copy link
Author

As we disabled cacheops it worked fine.

@Suor
Copy link
Owner

Suor commented Oct 23, 2023

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.

@Suor
Copy link
Owner

Suor commented Oct 23, 2023

Also did you try updating cacheops to the latest version?

@Suor Suor closed this as completed Nov 25, 2023
This issue was closed.
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