On Wednesday 05 November 2014 17:29:20 Michael Manfre wrote: > We can change the internal type of SlugField for option 1 based upon > whether or not the field should be unicode. Whether or not an existing > backend stores SlugField in an ascii char datatype shouldn't dictate > whether we go with SlugField(unicode=True) or UnicodeSlugField(). Let me > rephrase the question as, Do we want to provide backends enough information > so that they can decide to store an ascii slug field in an ascii char field > (e.g. varchar) and a unicode slug field in a unicode char field (e.g > nvarchar)? >
Could you please clarify the question? As far as I understand, schema editors get all the information anyway. Shai. -- 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/201411060253.31712.shai%40platonix.com. For more options, visit https://groups.google.com/d/optout.
