Even if the backend is storing using an ascii backed data type, it should
still return unicode data to Django anyway, so I'm not sure there would be
a difference.

Marc

On 6 November 2014 01:18, Michael Manfre <mman...@gmail.com> wrote:

>
>
> On Wed, Nov 5, 2014 at 7:53 PM, Shai Berger <s...@platonix.com> wrote:
>
>> 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.
>>
>
> Constructing the schema is only one part of the process. The main bit I am
> concerned about is how the ORM will translate the data. There are several
> methods on DatabaseOperatoins that exist to act based upon a field's
> internal type string. E.g. get_db_converters, field_cast_sql.
>
> --
> 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/CAGdCwBtW2qXdR5vm8g6Trwp7_aMY9GRfHUSeCjONz10W7audpw%40mail.gmail.com
> <https://groups.google.com/d/msgid/django-developers/CAGdCwBtW2qXdR5vm8g6Trwp7_aMY9GRfHUSeCjONz10W7audpw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAMwjO1Gb0TtDUdZQ0Yj2yRr2AfweRG-VJxaUqJd-ucic%3D50jyA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to