On Sep 25, 2008, at 00:14, Karen Tracey wrote:
> On Wed, Sep 24, 2008 at 4:49 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]
> > wrote:
>
> I'll go upload a fix now, the current behavior doesn't make sense,
> since the SQL spec says that NULL != NULL, does anyone know if there
> are any dbs for which
On Wed, Sep 24, 2008 at 4:49 PM, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:
>
> I'll go upload a fix now, the current behavior doesn't make sense,
> since the SQL spec says that NULL != NULL, does anyone know if there
> are any dbs for which this isn't true?
>
There are a couple of oddball DB
Thanks Alex! You get one virtual beer...
shannon
On Sep 24, 3:49 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> I'll go upload a fix now, the current behavior doesn't make sense,
> since the SQL spec says that NULL != NULL, does anyone know if there
> are any dbs for which this isn't true
I'll go upload a fix now, the current behavior doesn't make sense,
since the SQL spec says that NULL != NULL, does anyone know if there
are any dbs for which this isn't true?
On Sep 19, 11:10 am, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> On Fri, Sep 19, 2008 at 10:51 AM, smcoll <[EMAIL PROTECTE
i think this has to be fixed in the current code. i wish i knew how
to fix it, or i'd close #9062. The ticket hasn't gotten any
attention, but i feel like it's a biggie. i'm surprised it's not
breaking other people's apps.
shannon
On Sep 19, 10:10 am, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
On Fri, Sep 19, 2008 at 10:51 AM, smcoll <[EMAIL PROTECTED]> wrote:
>
> Take this model as an example:
>
> -
> from django.db import models
> from django.contrib.auth.models import User
>
> class Contact(models.Model):
>user = models.ForeignKey(User, unique=True, null=True, blank=T
Take this model as an example:
-
from django.db import models
from django.contrib.auth.models import User
class Contact(models.Model):
user = models.ForeignKey(User, unique=True, null=True, blank=True)
-
No more than one Contact can be saved with a Null fk on 'user',
