A proposal has been raised to change the validation for
CommaSeparatedIntegerField to allow negative numbers [1]. This is obviously
backwards-incompatible, so I don't think it'll fly without some option to
control the behavior, however, I wanted to ask if there's any reason not to
deprecate the field at this point. From a quick glance, I believe it 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)',
Is this difference meaningful? Are there any third-party database backends
that provide a special storage type for comma-separated integers such that
it deserves a separate field?
[1] https://code.djangoproject.com/ticket/26107#ticket
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" 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].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/f575b8f7-95e1-49af-9676-57b011a72d02%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
