#30644: Postgres introspection don't filter on visible objects.
-------------------------------------+-------------------------------------
Reporter: Georgi Yanchev | Owner: Georgi
Type: | Yanchev
Cleanup/optimization | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: Postgres schemas | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* status: new => assigned
* version: 2.2 => master
* owner: nobody => Georgi Yanchev
* type: Bug => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
Thanks for this report. I agree that we can use `pg_table_is_visible` and
remove filtering by `public` schema in `get_sequences()` and
`get_constraints()`. Django doesn't support schema so it's rather a
cleanup to me.
[https://github.com/django/django/pull/11511 PR]
Comment: `get_sequences()` will return sequences only from public schema.
--
Ticket URL: <https://code.djangoproject.com/ticket/30644#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/072.d6f3a00f8f9e4ee97c181302b8df6995%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
