Tickets :: Comment on [#9342] using an index on horde

* Your Email Address
* Spam protection	Enter the letters below: . .__ .___. . __. \| [ __[__ \|\/\|(__ \|___[_./\| \| \|.__)
Comment	> i suggest a primary key index on 'cache_id' > > and my optimizer tool also suggest: > > > ./qot --input-file=input.sql --input-query="SELECT cache_data FROM > horde_cache WHERE cache_id = '7af43c8a03e4cb392e9798b9c259e9d5' AND > cache_timestamp >= 1287901202;" --info --propose=index > /* Output produced by qot 0.0.4 GPL / > / > Query: SELECT cache_data FROM horde_cache WHERE cache_id = > '7af43c8a03e4cb392e9798b9c259e9d5' AND cache_timestamp >= 1287901202 > > selectivity: > zero or one row > > used tables: > horde_cache (zero or one row) > > ordering: > no ordering > > existing lookup indexes: > horde_cache.PRIMARY(cache_id) > > existing covering indexes: > (none) > / > / additional lookup indexes that can be created to improve query > performance */ > CREATE UNIQUE INDEX index0 ON `qot_test`.`horde_cache` ( > cache_id, > cache_timestamp); > > > > the tool i used is QOT http://ritmark.com/, perhaps you can verify the result
Attachment
Watch this ticket