#27090: pg_get_serial_sequence is broken on postgres, use a lookup in
information_schema.columns instead
-------------------------------------+-------------------------------------
Reporter: hmpf | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution:
Keywords: postgres sequence | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by hmpf):
Replying to [comment:4 timgraham]:
> Is there an open issue to correct the behavior in PostgreSQL? I found
[https://www.postgresql.org/message-
id/flat/4800.1445898830%40sss.pgh.pa.us#[email protected]
#13735] but the reply looks like the behavior is expected (again, I'm not
an expert on PG behavior, so I may have misunderstood).
That something works as documented doesn't necessarily mean that it is
useful :)
Interesting that it checks owner, with an inherited table only the
ancestor can be the owner of an inherited sequence so
pg_get_serial_sequence() cannot ever work on them as it is defined today.
I'm guessing what would be useful is a new postgres function that always
picks the currently in use sequence.
--
Ticket URL: <https://code.djangoproject.com/ticket/27090#comment:6>
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/062.560fcfb75c114abb2ac2868edf98dd67%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
