#25476: bug in array handling hit in get_constraints() for psycopg2?
-------------------------------------+-------------------------------------
     Reporter:  heasus               |                    Owner:  nobody
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  1.9
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  needsinfo
     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 xlotlu):

 This is most likely caused to by an import by a different user, with
 incomplete privileges (pg_dump -O maybe?). For example:

 {{{
 $ psql -qU user testdb
 testdb=> select count(*) from information_schema.constraint_column_usage;
  count
 -------
      0
 (1 row)
 }}}

 as opposed to

 {{{
 $ psql -qU superuser testdb
 testdb=# select count(*) from information_schema.constraint_column_usage;
  count
 -------
    219
 (1 row)
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/25476#comment:23>
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.123633f6010063398396adf6f0b96474%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to