Re: [Django] #25476: Use pg_catalog tables to introspect constraints

2016-09-02 Thread Django
#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 ):

 * 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: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
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.


Re: [Django] #25476: Use pg_catalog tables to introspect constraints

2016-08-18 Thread Django
#25476: Use pg_catalog tables to introspect constraints
-+-
 Reporter:  heasus   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 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
-+-

Comment (by socram):

 I've tweaked a bit the PR to support unique_together, too. Seems to be
 working fine on every case now.

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.50211e8b470b61a18fd5f4fc6f43e9cd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #25476: Use pg_catalog tables to introspect constraints (was: bug in array handling hit in get_constraints() for psycopg2?)

2016-08-17 Thread Django
#25476: Use pg_catalog tables to introspect constraints
-+-
 Reporter:  heasus   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 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 timgraham):

 * needs_better_patch:  0 => 1
 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 I'm not an expert there, but tentatively accepting, although the tests are
 passing with the proposed PR. That might just be a mistake rather than
 something that can't be fixed though.

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.afcb65a5741791500154fdc540bb5554%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.