#25476: bug in array handling hit in get_constraints() for psycopg2?
-------------------------------------+-------------------------------------
Reporter: heasus | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: psycopg2 fetchall | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by heasus):
Updating postgres to 9.4.5 did not change the behavior for me.
I reduced the schema to just the minimum to replicate the issue, and
indeed there are no default primary keys on table things but is one on
children (the object of the foreign keys). However, this does not matter;
the problem is in parsing the last field of the foreign keys as in the
previous comment in this ticket.
Hmmm; I'm not sure how to proceed to debug this. Same environment,
different results. The problem does appear to be within Django. Advice?
--
Ticket URL: <https://code.djangoproject.com/ticket/25476#comment:14>
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.ea14731f7a54d2f89d88f55b78c2e422%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
