List:General Discussion« Previous MessageNext Message »
From:Johan De Meersman Date:September 30 2010 6:50am
Subject:Re: ENGINE=ARCHIVE doesn't support INDEX!!??
View as plain text  
Correct. I assume the thinking behind it, is that you use that kind of table
for huge amounts of inactive data, so it doesn't matter if your selects are
a bit slower. Also, keep in mind that because it is a compressed file
format, you will be scanning much more data per physical read than with a
regular table, and so the table scan will be quite a bit faster, too.

If there are specific values you tend to use in where clauses all the time,
though, you can always consider partitioning the archived table.

On Thu, Sep 30, 2010 at 1:22 AM, Daevid Vincent <daevid@stripped> wrote:

> I gotta ask...
>
> http://dev.mysql.com/doc/refman/5.1/en/archive-storage-engine.html#c11511
>
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:    http://lists.mysql.com/mysql?unsub=1
>
>


-- 
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel

Thread
ENGINE=ARCHIVE doesn't support INDEX!!??Daevid Vincent30 Sep
  • Re: ENGINE=ARCHIVE doesn't support INDEX!!??Johan De Meersman30 Sep