Re: Weird behavior with date(null) and if

Baron Schwartz schrieb: On Dec 13, 2007 4:18 PM, Daniel Mikic [EMAIL PROTECTED] wrote: Baron Schwartz wrote: Hi, On Dec 13, 2007 3:53 PM, Daniel Mikic [EMAIL PROTECTED] wrote: Hi, i hit a weird behavior: select date(null); #result is null select if(date(null) is null, 1, 2

Weird behavior with date(null) and if

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

Re: Weird behavior with date(null) and if

Hi, On Dec 13, 2007 3:53 PM, Daniel Mikic [EMAIL PROTECTED] 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

Re: Weird behavior with date(null) and if

Baron Schwartz wrote: Hi, On Dec 13, 2007 3:53 PM, Daniel Mikic [EMAIL PROTECTED] 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

Re: Weird behavior with date(null) and if

On Dec 13, 2007 4:18 PM, Daniel Mikic [EMAIL PROTECTED] wrote: Baron Schwartz wrote: Hi, On Dec 13, 2007 3:53 PM, Daniel Mikic [EMAIL PROTECTED] 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