#16448: Single sequence for every table
-------------------------------------+-------------------------------------
Reporter: wiesiek@… | Owner: nobody
Type: New | Status: closed
feature | Component: Database layer
Milestone: | (models, ORM)
Version: 1.3 | Severity: Normal
Resolution: duplicate | Keywords:
Triage Stage: Design | Has patch: 0
decision needed | Needs tests: 0
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by jacob):
* status: new => closed
* resolution: => duplicate
Comment:
As aaugustin says, this was just a decision we made years ago. I don't see
that there's a great advantage either way: each option has its pros and
cons. I think #13295 is the answer here: let users decide if they feel
strongly. Thus, I'm marking this closed as a duplicate of #13295.
Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/16448#comment:4>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
