Linus Nikander wrote:
Whilst trying to figure out why one of my queries wasn't working I ran into
the following phenomenon which I'd be grateful if someone could explain.
(I'm running mySQL 4.0.17 on a win2003 server, querying using the 0.9.4
mysql control center)
The following query returns the
Whilst trying to figure out why one of my queries wasn't working I ran into
the following phenomenon which I'd be grateful if someone could explain.
(I'm running mySQL 4.0.17 on a win2003 server, querying using the 0.9.4
mysql control center)
The following query returns the expected result
SELECT
Hello, folks,
I've got an issue with a query. It's returning 95 rows, when there are only
3 that should be returned. Actually, it's returning many many copies of
each of the rows that are supposed to be returned, and nothing that
shouldn't be, so at least it's grabbing the correct information, b
select count(*) from members where country_id = 1 and read_array is NULL ;
Daren Cotter wrote:
> can anybody explain this to me?
>
> mysql> select count(*) from members where country_id = 1 and read_array not
> like '%20270%';
> +--+
> | count(*) |
> +--+
> |34884 |
> +-
I would have to guess that you have a broken index.
bill
-Original Message-
From: Daren Cotter [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 24, 2001 3:50 PM
To: [EMAIL PROTECTED]
Subject: very strange query behavior
can anybody explain this to me?
mysql> select count(*) f
can anybody explain this to me?
mysql> select count(*) from members where country_id = 1 and read_array not
like '%20270%';
+--+
| count(*) |
+--+
|34884 |
+--+
mysql> select count(*) from members where country_id = 1 and read_array like
'%20270%';
+--+
| coun
