#26154: Deprecate CommaSeparatedIntegerField
-------------------------------------+-------------------------------------
Reporter: timgraham | Owner: Brobin
Type: | Status: assigned
Cleanup/optimization |
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Brobin):
In the docs for deprecating the field it asks me to pick a unique id for
the field.
`'id': 'fields.W900', # pick a unique ID for your field.`
Is there a convention I should follow, or do I just pick a number that
doesn't already exist with another field?
--
Ticket URL: <https://code.djangoproject.com/ticket/26154#comment:2>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.a24a47288a013ae1b70d1b6f27587e62%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
