On Tue, 2009-01-06 at 08:03 -0800, dchandek wrote: [...] > The only gotcha I've encountered here is that practically speaking > null=True requires blank=True.
That isn't always valid and it's not the direction that's being proposed in this thread. One of the design goals of Django is to work relatively smoothly with databases that aren't necessarily solely populated or created by the Django libraries. Thus, you might well have a situation where the web interface is provided through Django code and, for that situation, it would never make sense to supply empty data (hence blank=False). However, some external process or entirely different web interface might also be providing data that does contain NULL values. Or you might be using a pre-existing database that contains NULL values in the column. Hence null=True. So null=True, blank=False is a sensible set up, although less common than null=True, blank=True and null=False, blank=False. This thread is about whether blank=True, null=False (the fourth possibility) ever makes sense for non-text fields. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
