On Dec 8, 9:24 pm, -RAX- <[email protected]> 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 = True > because by saving an empty string they do not respect that null != > null.
Exactly! > A work around of would be to override the form used by the admin > interface replacing the empty strings with None. Yeah, that's what I was doing. I do like Andrew's solution more though: a global pre_save hook. Matt. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
