List:General Discussion« Previous MessageNext Message »
From:Michael Widenius Date:January 4 2000 11:56pm
Subject:setting DATE field to NULL yields inconsistent behavior
View as plain text  
Hi!

>>>>> "tbrannon" == tbrannon  <tbrannon@stripped> writes:

>> Description:
tbrannon> The same command applied to 2 different records of a table yields
tbrannon> different results.
>> How-To-Repeat:
tbrannon> use UPDATE to bind the DATE field to NULL. In one application you
tbrannon> get back a NULL. On another, you get '0000-00-00'.
>> Fix:
tbrannon> Wish I knew :-)

<cut>

The problem is that check if the row did change failed in MySQL
3.23.3. This is fixed in MySQL 3.23.8.

Regards,
Monty
Thread
setting DATE field to NULL yields inconsistent behaviortbrannon5 Jan
  • Re: setting DATE field to NULL yields inconsistent behaviorBenjamin Pflugmann5 Jan
  • setting DATE field to NULL yields inconsistent behaviorMichael Widenius5 Jan
RE: setting DATE field to NULL yields inconsistent behaviortbrannon5 Jan
  • Re: setting DATE field to NULL yields inconsistent behaviorBenjamin Pflugmann5 Jan