-
Notifications
You must be signed in to change notification settings - Fork 28
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
Using django-flags with migrate_schemas #85
Comments
Hi @Vinci08. I'm not familiar with django-tenant-schema, so I don't know right off what it's doing that might be different from Django's standard I wonder, where do you have the "flags" app included in the various I will note too, if there are particular changes that would make django-flags work with multi-tenancy Django, we'd happily accept them! |
Hi @willbarton , thank you for taking your time and looking into this issue! I included flags in both shared_app and installed_app, but the problem remained the same. Even though django would say flags being migrated with 00012 and 00013 migration files, no table was actually created in the database. Would this be something to do with the Middleware? Edit: i double checked django-migration tables in both production and public database. Neither showed any row with app_name = flags. Run migration will just show no migration to run or no change in the app "flags". |
Hi,
Our django app uses django-tenant-schemas, thus we need to use migrate_schemas instead of migrate. I followed your user guide except for the migrate step, and always got the error below when click flagstate in django admin panel. I have researched this issue for couple hours, but there was very little info on this. I'd like to know if django-flags support migrate_schemas? That way I can understand the source of our problem.
Thank you!
`
ProgrammingError at /admin/flags/flagstate/add/
The text was updated successfully, but these errors were encountered: