#36598: Django migrations is unable to find remove constraints from non-public
schema for Postgres
-------------------------------------+-------------------------------------
Reporter: Salaah Amin | Owner: (none)
Type: Bug | Status: new
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: postgres, db, orm | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tanishq):
Hi Salaah,
I agree with your finding that the issue is due to
{{{pg_table_is_visible}}}filtering out the{{{analytics}}} schema, and
your suggestion to adjust the {{{search_path}}} during migrations makes
sense. Dynamically setting {{{search_path}}}
(e.g., SET {{{search_path}}}TO {{{public,analytics}}}) in the migration
session should resolve the constraint visibility problem without affecting
other operations, as long as it’s scoped to the migration context.
So, I say go ahead with the solution.
--
Ticket URL: <https://code.djangoproject.com/ticket/36598#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701993c34036d-7fa5af03-59c2-416b-aafb-919733a4b1e0-000000%40eu-central-1.amazonses.com.
