Hi Collin,
Thanks. That's perfect.
Regards,
Carlton
--
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
case.
> (i.e. this should already be the behaviour.)
>
> *Are there any reasons we can't adjust `empty_value_display` to also be
> used for empty strings?*
>
> Original Issue: https://code.djangoproject.com/ticket/28404
> PR: https://github.com/django/django/pull/9391
>
&
already
* The empty string is just how text-type fields handle the `null` case.
(i.e. this should already be the behaviour.)
*Are there any reasons we can't adjust `empty_value_display` to also be
used for empty strings?*
Original Issue: https://code.djangoproject.com/ticket/28404
PR: https://github.c
:01:22 PM UTC-4, Georgiy Nazarov wrote:
>>
>> Hello!
>>
>> Was there any consensus does ticket 28404
>> <https://code.djangoproject.com/ticket/28404> need to be fixed? And how
>> should it be fixed, just by showing empty_value_display in case of empty
>
No, there hasn't been any discussion about it. Do you have a use case for
solving the ticket that might inform the decision?
On Saturday, November 4, 2017 at 1:01:22 PM UTC-4, Georgiy Nazarov wrote:
>
> Hello!
>
> Was there any consensus does ticket 28404
> <https://code
Hello!
Was there any consensus does ticket 28404
<https://code.djangoproject.com/ticket/28404> need to be fixed? And how
should it be fixed, just by showing empty_value_display in case of empty
(not None) string or by separating cases of empty and None values?
--
Georgiy Nazarov
-
