#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 cjerdonek):
Another thought: more generally, it might be good to think about whether
the backends can be made more friendly to subclassing for cases like this.
That way the whole backend doesn't need to be forked just to change one
aspect. It's also good design in general.
I don't whether this is already easy or doable for the case at hand. It
would also reduce the importance / need for Django to "take a stance" in
cases where the best implementation is unknown or unclear, etc.
--
Ticket URL: <https://code.djangoproject.com/ticket/27090#comment:11>
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.8924c66d3bb0311725c91b355bfadb9c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
