On Tue, Aug 11, 2009 at 8:25 AM, gentlestone<tibor.b...@hotmail.com> wrote: > > On 11. Aug, 15:01 h., Gustavo Henrique <gustavo...@gmail.com> wrote: >> Try also: null=True, blank=True >> >> -- >> Gustavo Henriquehttp://www.gustavohenrique.nethttp://blog.gustavohenrique.net > > blank=True ... I have had, but this one doesn't solve the problem, > maybe the problem is in postgresql, the associated SQL code for > postgresql is > > CREATE TABLE ... > ... > UNIQUE ("some_fk_field_id", "some_plain_field"), > > and this apparently doesn't work > > >
You are talking about in the forms/admin validation correct? Thinking to how this is implemented there likely is a bug where this doesn't use the SQL concept of NULL != NULL and uses the Python None == None instead, which of these behaviors is correct I'm not sure of (though I lean towards the SQL interpretation). Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Voltaire "The people's good is the highest law." -- Cicero "Code can always be simpler than you think, but never as simple as you want" -- Me --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
