Arjen Lentz wrote:
[...]
While we're at it: the term "non-zero"... what does it mean? As we all
know, NULL != 0, and 0 == zero, consequently NULL must be non-zero.
Flawed logic.
Yes, I used flawed logic to illustrate my point: "non-zero" is a bad
term to use in this context.
The text from the
Hi Roger, Michael, Vlad,
Let me just follow up on this old thread, as it may clarify some things.
On Fri, 2004-12-03 at 02:00, Roger Baklund wrote:
> Michael Stassen wrote:
> > You are overthinking the issue.
>
> Probably. :)
>
> > mysql> SELECT VERSION();
> > +---+
> > | VERSION() |
>
Hi Vlad !
Why not using
select (select min( a ) is null from a) or null;
as a workaround ?
Regards,
Jocelyn
- Original Message -
From: "Vlad Shalnev" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, December 03, 2004 7:01 AM
Subject: Re:
Sergei Golubchik wrote:
Hi!
On Dec 02, Vlad Shalnev wrote:
Looks like a bug.
Could you submit a bugreport at http://bugs.mysql.com ?
I've submitted a bugreport.
Downgrade to 3.23 and wait for this problem solving.
Thanks for all
It happens after upgrade from 3.23.46.
mysql> create table a ( a i
At 11:42 -0500 12/2/04, Michael Stassen wrote:
Roger Baklund wrote:
This is (as I see it) a documentation issue, I was not trying to
say that Vlad was "wrong".
Right, that's why I'm copying the docs list.
I updated the description to account for the cases when there are 1 or 2
NULL operands. It
I upgraded from 5.01 to 5.02 and now I am getting the error localhost is not
allowed to connect to this MySQL server. What should I do, root cannot
connect a well. I'm currently using win32 and have old-passwords in my.cnf
Thanks
--
MySQL General Mailing List
For list archives: http://lists.mys
Roger Baklund wrote:
This is (as I see it) a documentation issue, I was not trying to say
that Vlad was "wrong".
Right, that's why I'm copying the docs list.
While we're at it: the term "non-zero"... what does it mean? As we
all know, NULL != 0, and 0 == zero, consequently NULL must be non-zero
> -Original Message-
> From: Roger Baklund [mailto:[EMAIL PROTECTED]
> This definition (from the manual) is self-contradicting: 1 OR NULL
> should evaluate to 1 because "any operand is non-zero", but it should
> also evaluate to NULL because "any operand is NULL".
>
> http://dev.mysql.c
Michael Stassen wrote:
You are overthinking the issue.
Probably. :)
mysql> SELECT VERSION();
+---+
| VERSION() |
+---+
| 4.1.7 |
+---+
1 row in set (0.00 sec)
mysql> SELECT 1 OR NULL;
+---+
| 1 OR NULL |
+---+
| 1 |
+---+
1 row in set (0.0
You are overthinking the issue.
mysql> SELECT VERSION();
+---+
| VERSION() |
+---+
| 4.1.7 |
+---+
1 row in set (0.00 sec)
mysql> SELECT 1 OR NULL;
+---+
| 1 OR NULL |
+---+
| 1 |
+---+
1 row in set (0.00 sec)
We do not need to know x to d
Vlad Shalnev wrote:
* from the manual:
>> Logical OR. Evaluates to 1 if any operand is non-zero, to NULL if any
>> operand is NULL, otherwise 0 is returned.
* Roger Baklund:
This definition (from the manual) is self-contradicting: 1 OR NULL
should evaluate to 1 because "any operand is non-zero", bu
Hi!
On Dec 02, Vlad Shalnev wrote:
Looks like a bug.
Could you submit a bugreport at http://bugs.mysql.com ?
> It happens after upgrade from 3.23.46.
>
> mysql> create table a ( a int not null );
> Query OK, 0 rows affected (0.00 sec)
>
> mysql> select min( a ) is null or null from a;
> +
Vlad Shalnev wrote:
[...]
OR
||
Logical OR. Evaluates to 1 if any operand is non-zero, to NULL if any
operand is NULL, otherwise 0 is returned.
This definition (from the manual) is self-contradicting: 1 OR NULL
should evaluate to 1 because "any operand is non-zero", but it should
also evaluate t
Bernard Clement wrote:
Hello Vlad,
The reason is: "If one or both arguments are NULL, the result of the
comparison is NULL, except for the NULL-safe <=> equality comparison
operator.
Thereore, "or NULL" in your select statement will always returned NULL.
You can find all the rules for comparai
Hello Vlad,
The reason is: "If one or both arguments are NULL, the result of the
comparison is NULL, except for the NULL-safe <=> equality comparison
operator.
Thereore, "or NULL" in your select statement will always returned NULL.
You can find all the rules for comparaison at URL:
http://de
15 matches
Mail list logo
