On 11/15/06, Stefan Foulis <[EMAIL PROTECTED]> wrote: > > Hi > > Starting with a empty database and running syncdb does not set the > fields in the resulting tables to allow NULL values on any fields > (not even the ones with blank=True) on my installation. > django correctly allows empty fields in the admin interface, but of > course the db backend complains as soon as django tries to save to > the db. > > Is this a known issue? Or is something bogus with my installation? > (I tried this with postgres and sqlite and had this problem with > Integer-, String- and ForeignKey-Fields. Manually changing the fields > in the db solved the problem.)
blank=True is *only* for admin level validation, it has no effect on the db. You want null=True Jay P. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
