Hi Shai, On 22 sept. 2015, at 04:22, Shai Berger <s...@platonix.com> wrote:
> I'd solve the "need to specify" issue by setting a default that is > intentionally smaller than the smallest (core) backend limitation, say 128. I would pick the highest value supported by all core backends (probably 255 for MySQL, unless there’s something about indexes and multi-byte encodings that I forget) in order to minimize the need to increase it. If we go for a lower value, I suggest to pick something totally arbitrary like 100 to make it clear that it isn't a technical limitation. > I"d make an "unlimited length text field" a new type of field, explicitly not > supported on MySql and Oracle; and I'd suggest that it can live outside core > for a while. so we may get an impression of how popular it really is. The main use case seems to be “VARCHAR() on PostgreSQL”. What about defining a slight variant of CharField in django.contrib.postgres that merely makes the max_length argument default to None? -- Aymeric. -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/17C37814-E6A8-4E27-B590-BF9FFF42CB20%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
