Timeline for General error 1651 after a mysql migration
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 19, 2013 at 16:34 | vote | accept | Sebas | ||
| May 19, 2013 at 16:00 | answer | added | ypercubeᵀᴹ | timeline score: 2 | |
| May 19, 2013 at 15:57 | comment | added | Sebas |
@ypercube that was it. Please add your comment as an answer and I'll accept it. Changing it to SET ... = 0 does not change anything, removing totally the setting does. I agree that it is overkill to double specify the parameter on server and client's sessions, but to me it should not behave like this anyway.
|
|
| May 19, 2013 at 15:50 | comment | added | ypercubeᵀᴹ |
And since the server starts with query_cache_type = 0, I don't think there is any reason to use that SET.
|
|
| May 19, 2013 at 15:47 | comment | added | ypercubeᵀᴹ |
I think the SET SESSION query_cache_type = OFF is causing this. Have you read (in the Query Cache Configuration page) that: "If you set query_cache_type at server startup (rather than at runtime with a SET statement), only the numeric values are permitted."
|
|
| May 19, 2013 at 15:36 | history | asked | Sebas | CC BY-SA 3.0 |