On 07.01-09:47, Malcolm Tredinnick wrote: [ ... ] > This thread is about whether blank=True, null=False (the fourth > possibility) ever makes sense for non-text fields.
answer is yes for any field type that accepts an empty string as having a meaning. i currently use this for a couple of custom fields that are autogenerated but can be set manually, if desired. it could also happen for innumerate other reasons. or put more simply '-1' for me. as i stated previously it seems unwise to speculate what may be needed, particularly because the current distinction is clear and valid, however, i would still be in favour of a change in conventions that will hide this issue/oddity from most implementations. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
