Hello,
Storing a comma-separated list of integers in a text field in a SQL database is
a really bad anti-pattern. That's a sufficient reason for Django to stop
condoning it, which it did by providing that functionality out of the box.
It was widely accepted (at least among the core team) that
I agree with the removal, it wasn't providing much value and was making it
unclear as to what it actually aws. It could easily be mistaken by a
beginner for a performant alternative to M2M models or something like
django.contrib.postgres' ArrayField. Additionally it was weird that Django
would offe
The CharField(validators=[validate_comma_separated_integer_list]) version
is more explicit about how the database stores the data. In my mind, having
a separate field could give the impression that the database uses a special
field type or validation. Also, I think
CommaSeparatedIntegerField is
I see that CommaSeparatedIntegerField is being deprecated, but I don't see
why. I know I'm apparently late to the discussion, but after it 16 months I
don't see any actual reasoning.
I recognize that a CharField with the validator is functionally equivalent,
but it takes a very handy field type
