won't use an index if it thinks it will
> find more than about 30% of all rows?
>
> What happens after you run ANALYZE TABLE? It doesn't appear that you've
> done so since your index cardinality is NULL.
>
>
> Matt
>
>
> - Original Message
f all rows?
What happens after you run ANALYZE TABLE? It doesn't appear that you've
done so since your index cardinality is NULL.
Matt
- Original Message -
From: "Peter Rabbitson"
Sent: Sunday, October 12, 2003 10:42 PM
Subject: Re: unexpected index behaviour...
>
G you guys are very helpful... Anyway posting a reply to my own question. There is
no way to use a timestamp as an
index in a relatively large table. MySQL just does not take it even with explicit
FORCE KEY. Why? - I have no idea.
A workaround I found for this is running a script every minu
Hello all,
I asked a similar question earlier. Then I went and did tons of tests... but I am back
where I started. Basicly I am trying
to store pretty high volume of data (ip traffic) in a mysql database. The only choidce
for an engine is MyIsam because I
need the advantage of compressed table
