#25476: Use pg_catalog tables to introspect constraints
-------------------------------------+-------------------------------------
Reporter: heasus | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: psycopg2 fetchall | Triage Stage: Accepted
inspectdb permissions |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"d6b9aab37c41a772e5519e46b42b39958f99cadd" d6b9aab]:
{{{
#!CommitTicketReference repository=""
revision="d6b9aab37c41a772e5519e46b42b39958f99cadd"
Fixed #25476 -- Allowed PostgreSQL introspection to work regardless of
table owner.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25476#comment:29>
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/064.7d0f0a01fd7f7f7a465e93210f23da38%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
