On Fri, Mar 2, 2012 at 12:15 AM,  <jirka.vejra...@gmail.com> wrote:
> Hi Marc,
>
>  if I remember correctly (can't check now), the documentation clearly states 
> that you should avoid using null=True on CharField unless you have a good 
> reason. Your example is a textbook reason why is it recommended - having two 
> distinct states for "empty string" (i.e. "blank" and "null") leads to 
> inconsistencies and confusion.
>

Hi Jirka, thanks for the answer!! you're totally right :) I've missed
this pice of documentation
thanks again.
-- 
Marc

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to