>> It's an edge case, either way (who puts hundreds of numbers in such a field?)
I'm not saying it's good or right, but I can easily see how people would store hundreds of comma separated values as a poor version of a m2m table. I'm not sure that the difference between NVARCHAR2 and VARCHAR2 would be meaningful to that use case, but it's something to consider. I'm in favour of making the change, just call it out as a backwards compatibility. -- 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/ae40baed-a8cf-480f-b2c4-e63ce0db7237%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
