#26154: Deprecate CommaSeparatedIntegerField
-------------------------------------+-------------------------------------
Reporter: timgraham | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database | Version: master
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
As [https://groups.google.com/d/topic/django-
developers/wfp9qNpNpaQ/discussion proposed on django-developers],
`CommaSeparatedIntegerField` could be replaced with
`CharField(validators=[validate_comma_separated_integer_list])`.
The only database storage difference is on Oracle:
{{{
'CharField': 'NVARCHAR2(%(max_length)s)',
'CommaSeparatedIntegerField': 'VARCHAR2(%(max_length)s)',
}}}
There are some upgrade considerations described on the mailing list
that'll need to be mentioned for Oracle users.
See [https://docs.djangoproject.com/en/dev/topics/migrations
/#considerations-when-removing-model-fields the migration topic guide] for
an explanation of how to deprecate the field, as well as the
[https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
/submitting-patches/#deprecating-a-feature deprecating a feature guide].
--
Ticket URL: <https://code.djangoproject.com/ticket/26154>
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/052.5866007a922f8758421cf064bdb28856%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
