jfield,
Thursday, October 10, 2002, 1:33:10 AM, you wrote:
jazdc> >Description:
jazdc> After adding a key to a nullable column, null values will
jazdc> successfully join through to null values in other tables.
jazdc> This only seems to happen when the index is added after
jazdc> the row contains
jfield,
Thursday, October 10, 2002, 1:33:10 AM, you wrote:
jazdc> After adding a key to a nullable column, null values will
jazdc> successfully join through to null values in other tables.
jazdc> This only seems to happen when the index is added after
jazdc> the row contains null values. This af
PROTECTED]
Subject: NULL sometimes joins to NULL
>Description:
After adding a key to a nullable column, null values will
successfully join through to null values in other tables.
This only seems to happen when the index is added after
the row contains null values. This affects both MyISAM
: Thursday, October 10, 2002 9:45 AM
To: [EMAIL PROTECTED]
Subject: Re: NULL sometimes joins to NULL
>From: [EMAIL PROTECTED]
>
>After adding a key to a nullable column, null values will
>successfully join through to null values in other tables.
And this is a problem because? :-)
Seriously,
>From: [EMAIL PROTECTED]
>
>After adding a key to a nullable column, null values will
>successfully join through to null values in other tables.
And this is a problem because? :-)
Seriously, it may be a bug, but IMHO it is a design flaw to index a NULL field.
Indexed fields should always be NOT
>Description:
After adding a key to a nullable column, null values will
successfully join through to null values in other tables.
This only seems to happen when the index is added after
the row contains null values. This affects both MyISAM
and InnoDB table types and both binary versions 3.23.42
