On 29 May 2014, at 10:23, Roberto Spadim <roberto@spadim.com.br> wrote:

> Hi guys! I'm with a doubt, spider engine don't allow query cache right? But does it use sql_cache sql_no_cache when possible?
>

spider has a table parameter called query_cache that sends query from spider to remote server - see: https://mariadb.com/kb/en/spider-table-system-variables/#query_cache
Default is 0, that is no query cache when a select is issued on a remote server
=1 passes sql_cache - result can be cached
=2 sql_no_cache is passed - query result not cached
that's all documented: http://dev.mysql.com/doc/refman/5.5/en/query-cache-in-select.html

I notice that in this article, https://mariadb.com/kb/en/query-cache/, the limitations do state: "      • The query cache is not used by the Spider storage engine (amongst others)."

And then we have this article, https://mariadb.com/kb/en/spider-feature-matrix/ that also states spider supports the query cache - "Query Cache tuning per table of the on remote backend" - Yes

So, docs need to be clearer/in sync, since spider can't use the query cache on a spider node, but it can on a remote server
--
Colin Charles, Chief Evangelist, SkySQL - The MariaDB Company
blog: http://bytebot.net/blog/| t: +6-012-204-3201 | Skype: colincharles