ENGINE=ARCHIVE doesn"t support INDEX!!??

ENGINE=ARCHIVE doesn"t support INDEX!!??

am 30.09.2010 01:22:39 von Daevid Vincent

I gotta ask...

http://dev.mysql.com/doc/refman/5.1/en/archive-storage-engin e.html#c11511



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

Re: ENGINE=ARCHIVE doesn"t support INDEX!!??

am 30.09.2010 08:50:19 von Johan De Meersman

--0016e6d36948cb12ea0491747dd5
Content-Type: text/plain; charset=ISO-8859-1

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 wrote:

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


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

--0016e6d36948cb12ea0491747dd5--