Hi.  Hopefully this has a quick answer; I tried searching the list but
didn't come up with an answer.

Context:
I'm extending django.contrib.auth.models.User with some extra fields,
for instance IntegerField() and ForeignKey().

For non-string fields, whenever you use blank=True you also currently
need null=True.  (null=True causes django to insert a null instead of
an empty string)

If the type is not a string, and blank=True is set, shouldn't
null=True be implied?

Thanks,
Mike

--~--~---------~--~----~------------~-------~--~----~
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