#13295: Add a Meta.sequence option to models
-------------------------------------+-------------------------------------
Reporter: Max Shabalihin | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 1.1
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: sequence last_id | Triage Stage:
postgresql | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* needs_better_patch: 1 => 0
* needs_tests: 1 => 0
* needs_docs: 1 => 0
* has_patch: 1 => 0
* resolution: => wontfix
* stage: Accepted => Unreviewed
Comment:
Replying to [comment:11 Claude Paroz]:
> Should this be closed now that #30511 was merged?
There are still scenarios that could be covered by `Meta.sequence`, e.g.
common sequence for multiple tables. However, since we are using identity
columns on PostgreSQL and Oracle it becomes much more complicated or even
not feasible. I don't think there is a way to move it forward. Closing as
"wontfix".
--
Ticket URL: <https://code.djangoproject.com/ticket/13295#comment:12>
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/010701802b751c9c-f089bc29-1b18-49d2-95fc-cce1b75bb40e-000000%40eu-central-1.amazonses.com.
