#27452: Add Postgres serial field to contrib.postgres
-------------------------------------+-------------------------------------
Reporter: Johannes Maron | Owner: Csirmaz
| Bendegúz
Type: New feature | Status: assigned
Component: contrib.postgres | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Csirmaz Bendegúz):
Replying to [comment:28 Florian Apolloner]:
> Hi folks, I am wondering if we really want & need something like this in
Django. What are the arguments that this has to be in Django as opposed to
a third party library. The issue exists since 8 years with little to no
comments so I would argue that using multiple serial fields on a model or
having explicit access to a serial field is not a feature that is needed
often. So even if this is suggested for contrib I kinda wonder if we have
to support every postgresql feature out there.
My goal with this one is to have a field that can be used as a ''surrogate
key'' in composite primary keys
([https://code.djangoproject.com/ticket/373 #373]), when/if that feature
lands.
If we can't have AutoFields in composite primary keys
([https://code.djangoproject.com/ticket/8576#comment:10 #8576]), then it
would be nice to have SerialFields at least.
--
Ticket URL: <https://code.djangoproject.com/ticket/27452#comment:30>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701902b2bc120-7c710dab-37d6-4776-8dee-3e081c47755e-000000%40eu-central-1.amazonses.com.
