I agree with Lee. There should be a way for a developer to store NULL into a char field. At the moment null flag has no effect for a CharField. Generally saying an empty string is not the same a not defined value = NULL. It's pity that the according ticket is closed with won't fix http://code.djangoproject.com/ticket/9590
Magus On Feb 13, 2:31 pm, Lee Braiden <[email protected]> wrote: > 2009/2/13 Praveen <[email protected]>: > > > Avoid usingnullon string-based fields such as CharField and > > TextField unless you have an excellent reason. > > What exactly is the reasoning behind this advice? It seems to me that > one would very rarely want to store an empty string. For example, if > a user doesn't enter a surname, that does not mean that their surname > is "", unless they're Cher. > > -- > Lee --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
