Malcolm Tredinnick wrote: > Think about how the data is entered: through a web form (the admin > interface, or a custom form). Now, how do you differentiate between an > explicit empty string and a "no data entered and so it should be NULL" > field? With web entry, you can't, so Django chooses to default to using > empty strings everywhere.
So I understand that Django made the choice to default to empty strings, but what I am really trying to learn is why. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
