On Monday, June 18, 2012 5:59:27 PM UTC-6, André Pang wrote: > > What I'd like to do is (1) disallow NULLs, and (2) disallow empty strings. > It looks like there's no current way to do this with Oracle since the > backend overrides null to always be True, and blank is an admin validation > thing only. >
There's also no current way* to do this AFAIK with postgresql, mysql, or sqlite. I'm not opposed to the feature request, but if we're going to do it, then I think it should be universal, not just for Oracle. For the other backends I suppose a CHECK constraint would be required. Cheers, Ian * Of course with any backend there is the option of writing custom DDL and running it instead of or in addition to syncdb. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/GbrE1zMU3N4J. 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.
