Re: django.contrib.admin and null=True

On Dec 9, 1:57 pm, schinckel wrote: > On Dec 8, 2:02 pm, nasp wrote: > > > You might consider > > readinghttp://docs.djangoproject.com/en/dev/ref/models/fields/#null. > > Thanks: that was the link I needed. > > However, I do take exception with the

Re: django.contrib.admin and null=True

On Dec 8, 9:24 pm, -RAX- wrote: > By default Admin saves an empty string in those TextFields and > CharFields defined as null = True. > > Whatever the semantic reasons are, this default behavior creates > problems in those fields which are both unique = True and null =

Re: django.contrib.admin and null=True

On Dec 8, 2:02 pm, nasp wrote: > You might consider > readinghttp://docs.djangoproject.com/en/dev/ref/models/fields/#null. Thanks: that was the link I needed. However, I do take exception with the comment: If a string-based field has null=True, that means it has two

Re: django.contrib.admin and null=True

On Dec 8, 9:28 pm, Andrew Godwin wrote: > On 07/12/10 23:26, schinckel wrote: > > > > > > > I haven't been able to find any documentation about this, but would be > > happy to be pointed in the right direction. > > > When you use null=True in a field, and then use that model

Re: django.contrib.admin and null=True

By default Admin saves an empty string in those TextFields and CharFields defined as null = True. Whatever the semantic reasons are, this default behavior creates problems in those fields which are both unique = True and null = True because by saving an empty string they do not respect that null

Re: django.contrib.admin and null=True

On 07/12/10 23:26, schinckel wrote: I haven't been able to find any documentation about this, but would be happy to be pointed in the right direction. When you use null=True in a field, and then use that model in the admin, it will not save NULL to the database, but will instead save an empty

Re: django.contrib.admin and null=True

On Tue, Dec 7, 2010 at 4:26 PM, schinckel wrote: > I think this is broken behaviour: NULL values are semantically > different to empty strings, and in certain cases (I think it was > IPAddressField, but I will have another look later), it would fail to > write to the database.

Re: django.contrib.admin and null=True

You might consider reading http://docs.djangoproject.com/en/dev/ref/models/fields/#null. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this

django.contrib.admin and null=True

I haven't been able to find any documentation about this, but would be happy to be pointed in the right direction. When you use null=True in a field, and then use that model in the admin, it will not save NULL to the database, but will instead save an empty string (or attempt to). I think this