#34131: Postgres AutoField change from serial to identity
-------------------------------------+-------------------------------------
Reporter: Marco Glauser | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Glad to hear the workaround worked!
> We originally chose to misuse the AutoField because Django doesn't offer
any SERIAL field and it's easier to patch the default value than to create
the sequences and everything that goes with it ourselves.
I think this the crux of the issue. Given #27452 already tracks the lack
of proper support for serial fields, which is something you would have
used if it was available, I'm also convinced that this issue should be
closed as it's not actionable.
--
Ticket URL: <https://code.djangoproject.com/ticket/34131#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070184580ff415-b30f32c0-1e50-4354-921f-04b97c1fd880-000000%40eu-central-1.amazonses.com.
