Hi, i hit a weird behavior:

select date(null); #result is null
select if(date(null) is null, 1, 2); #result is 2 (not null)
select if(date(null) is not null, 1, 2); #result is 1

I use mysql version 5.0.32-Debian_7etch1-log.

Is this a bug and if not, can anyone explain why?

Thanks,

Daniel

Hi,

On Dec 13, 2007 3:53 PM, Daniel Mikic <daniel.mikic@logical-line.de> wrote:
> Hi, i hit a weird behavior:
>
> select date(null); #result is null
> select if(date(null) is null, 1, 2); #result is 2 (not null)
> select if(date(null) is not null, 1, 2); #result is 1
>
> I use mysql version 5.0.32-Debian_7etch1-log.
>
> Is this a bug and if not, can anyone explain why?

Seems to be a bug, but I can't reproduce on
5.0.45-Debian_1ubuntu3-log, where it works correctly.

What do you get from this?

mysql> select date(null) is null;
+--------------------+
| date(null) is null |
+--------------------+
| 1 |
+--------------------+
1 row in set (0.00 sec)

Baron Schwartz wrote:
> Hi,
>
> On Dec 13, 2007 3:53 PM, Daniel Mikic <daniel.mikic@logical-line.de> wrote:
>
>> Hi, i hit a weird behavior:
>>
>> select date(null); #result is null
>> select if(date(null) is null, 1, 2); #result is 2 (not null)
>> select if(date(null) is not null, 1, 2); #result is 1
>>
>> I use mysql version 5.0.32-Debian_7etch1-log.
>>
>> Is this a bug and if not, can anyone explain why?
>>
>
> Seems to be a bug, but I can't reproduce on
> 5.0.45-Debian_1ubuntu3-log, where it works correctly.
>
> What do you get from this?
>
> mysql> select date(null) is null;
> +--------------------+
> | date(null) is null |
> +--------------------+
> | 1 |
> +--------------------+
> 1 row in set (0.00 sec)
>
>
Hi, here is the result:

db2:~# mysql
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1909348
Server version: 5.0.32-Debian_7etch1-log Debian etch distribution

Type ';' or '\h' for . Type '\c' to clear the buffer.

mysql> select date(null) is null;
+--------------------+
| date(null) is null |
+--------------------+
| 0 |
+--------------------+
1 row in set (0.00 sec)

Thanks

Daniel

On Dec 13, 2007 4:18 PM, Daniel Mikic <daniel.mikic@logical-line.de> wrote:
>
> Baron Schwartz wrote:
>
> Hi,
>
> On Dec 13, 2007 3:53 PM, Daniel Mikic <daniel.mikic@logical-line.de> wrote:
>
>
> Hi, i hit a weird behavior:
>
> select date(null); #result is null
> select if(date(null) is null, 1, 2); #result is 2 (not null)
> select if(date(null) is not null, 1, 2); #result is 1
>
> I use mysql version 5.0.32-Debian_7etch1-log.
>
> Is this a bug and if not, can anyone explain why?
>
> Seems to be a bug, but I can't reproduce on
> 5.0.45-Debian_1ubuntu3-log, where it works correctly.
>
> What do you get from this?
>
> mysql> select date(null) is null;
> +--------------------+
> | date(null) is null |
> +--------------------+
> | 1 |
> +--------------------+
> 1 row in set (0.00 sec)
>
>
> Hi, here is the result:
>
> db2:~# mysql
> Welcome to the MySQL monitor. Commands end with ; or \g.
> Your MySQL connection id is 1909348
> Server version: 5.0.32-Debian_7etch1-log Debian etch distribution
>
> Type ';' or '\h' for . Type '\c' to clear the buffer.
>
> mysql> select date(null) is null;
> +--------------------+
> | date(null) is null |
> +--------------------+
> | 0 |
> +--------------------+
> 1 row in set (0.00 sec)
>

Definitely a bug. I'd see if it's been reported at
http://bugs.mysql.com/ and if not, report it anyway. If it has been
fixed "accidentally" there may not be a test case to prevent it from
happening in the future.

Baron Schwartz schrieb:
> On Dec 13, 2007 4:18 PM, Daniel Mikic <daniel.mikic@logical-line.de> wrote:
>
>> Baron Schwartz wrote:
>>
>> Hi,
>>
>> On Dec 13, 2007 3:53 PM, Daniel Mikic <daniel.mikic@logical-line.de> wrote:
>>
>>
>> Hi, i hit a weird behavior:
>>
>> select date(null); #result is null
>> select if(date(null) is null, 1, 2); #result is 2 (not null)
>> select if(date(null) is not null, 1, 2); #result is 1
>>
>> I use mysql version 5.0.32-Debian_7etch1-log.
>>
>> Is this a bug and if not, can anyone explain why?
>>
>> Seems to be a bug, but I can't reproduce on
>> 5.0.45-Debian_1ubuntu3-log, where it works correctly.
>>
>> What do you get from this?
>>
>> mysql> select date(null) is null;
>> +--------------------+
>> | date(null) is null |
>> +--------------------+
>> | 1 |
>> +--------------------+
>> 1 row in set (0.00 sec)
>>
>>
>> Hi, here is the result:
>>
>> db2:~# mysql
>> Welcome to the MySQL monitor. Commands end with ; or \g.
>> Your MySQL connection id is 1909348
>> Server version: 5.0.32-Debian_7etch1-log Debian etch distribution
>>
>> Type ';' or '\h' for . Type '\c' to clear the buffer.
>>
>> mysql> select date(null) is null;
>> +--------------------+
>> | date(null) is null |
>> +--------------------+
>> | 0 |
>> +--------------------+
>> 1 row in set (0.00 sec)
>>
>>
>
> Definitely a bug. I'd see if it's been reported at
> http://bugs.mysql.com/ and if not, report it anyway. If it has been
> fixed "accidentally" there may not be a test case to prevent it from
> happening in the future.
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=d...ogical-line.de
>
>
>
Hi, this bug was fixed with version 5.0.36.

http://bugs.mysql.com/bug.php?id=23938

Thanks

Daniel

--

Mit freundlichen Grüßen

Daniel Mikic
IT-Leiter / CIO

logical line GmbH
Hamburger Allee 23
30161 Hannover
HRB 56320/AG Hannover
Geschäftsführer: Dr. Rüdiger Lemke
www.logicalline.com
Fon: +49 511 936 208 - 32
Fax: +49 511 936 208 - 11