#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:5 timgraham]:
> I also found some possibly related Django tickets (e.g.
ticket:8901#comment:25) that were closed as a duplicate of #13295. Maybe
that would address this?
That would also solve the problem but I think the solution I'm working on
involves less code. On the other hand, explicit is better than implicit...
This ticket would make more postgres databases just work out of the box.
Ticket #13295 could use the lookup in information_schema as part of its
own solution. Seen that way, #13295 depends on this one.
--
Ticket URL: <https://code.djangoproject.com/ticket/27090#comment:8>
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.2ff9c9ae26fc70fa59b40a448c6439d9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
