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
in
the new table, and although it still doesn't work natively, a FORCE KEY correctly
selects and uses the corresponding index.
Downside is I lose 1 minute of data but... what gives.
Cheers
Peter
On Fri, Oct 03, 2003 at 04:13:51AM -0500, Peter Rabbitson wrote:
> Hello all,
>
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
ill help?
>
> -James
>
> Peter Rabbitson wrote:
> >Hello all,
> >I am trying to set up a complete trraffic accounting using Ulogd-mysql.
> >Since the whole idea of the project is to be able to select rows based on
> >the timestamp value indexing is a must.
Hello all,
I am trying to set up a complete trraffic accounting using Ulogd-mysql. Since the
whole idea of the project is to be
able to select rows based on the timestamp value indexing is a must. The index files
get created with no problem at
all. However explain select refuses to use the ind
