On Mon, 2006-03-06 at 12:59 +0300, Ivan Sagalaev wrote: > Malcolm Tredinnick wrote: > > >In a correct SQL implementation, NULL is not comparable to anything, > > > > > Yes... It should be :-). And as you said implementation is the whole > another businness. johnsu01 talked about MySQL and given its history of > not very strong adherence to standard but preferring pratical aspects of > doing things I supposed that it's not working like that. The problem > description made it look like that for me. So forgive me for sounding > like some kinf of authority on the matter of uniqueness!
I should apologise: I did not mean to come across as slamming your contribution. After I pressed send, I realised my mail was more abrupt than necessary. To the problem at hand: John's problem is not actually about NULLs being non-distinct. He has bumped into the design decision in Django that says CharFields will always have empty values stored as empty strings, not NULLs. Even if null=True is set on that field (this is documented, but you have to read it carefully). > But since things work so different may be custom validator is not a bad > idea after all... Yes. A custom validator is one solution. Again, my apologies for sounding rude and dismissive. Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
