#13295: alternate name sequence for postgresql in class meta db_seq
---------------------------------------------------+------------------------
Reporter: smglab | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: 1.1
Resolution: | Keywords: sequence
last_id postgresql
Stage: Accepted | Has_patch: 1
Needs_docs: 1 | Needs_tests: 1
Needs_better_patch: 1 |
---------------------------------------------------+------------------------
Changes (by russellm):
* needs_better_patch: 0 => 1
* stage: Unreviewed => Accepted
Comment:
It's an edge case, but one that's probably worth supporting.
Regarding the patch --
* it obviously needs tests.
* It seems to ignore the creation of sequence names in the first place
* It seems to be appending "_seq" to the name of the provided sequence
name. Why? If I manually specify a sequence name, shouldn't it be used
verbatim?
* _meta.db_seq should always return the correctly constructed sequence
name; we shoulnd't need to use 'if pk_name' or similiar tricks to work out
if the sequence has been manually specified.
--
Ticket URL: <http://code.djangoproject.com/ticket/13295#comment:2>
Django <http://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 django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
