[MDEV-6977] SET STATEMENT query_cache_type apparently has no effect and hence should be disallowed Created: 2014-10-29 Updated: 2015-05-19 Resolved: 2014-11-05 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Admin statements |
| Affects Version/s: | N/A |
| Fix Version/s: | 10.1.2 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Elena Stepanova | Assignee: | Oleksandr Byelkin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
From all I see, SET STATEMENT ... FOR SELECT queries are not put in the query cache and do not use it, whatever parameters are. Then, SET STATEMENT query_cache_type = ... can't have any effect, and thus should be disabled with ER_SET_STATEMENT_NOT_SUPPORTED. Same is probably true for other query_cache_* variables potentially changeable in SET STATEMENT context (query_cache_strip_comments? query_cache_wlock_invalidate?). In Percona server it looks even worse, SET STATEMENT .. queries are put into the query cache, but never hit it. |
| Comments |
| Comment by Oleksandr Byelkin [ 2014-11-05 ] |
|
the variable is prohibited |