Looking at post by Konstantin Osipov we should finally get Query Cache working with prepared statements in MySQL 5.1
The interesting thing Konstantin notes it just took few days to fix it – I believe MySQL Support Team alone spent much more times explaining customers why is it not done or troubleshooting cases with wrong customer assumptions regarding this problems. I think I alone spent tens of hours in various cases related to this problem.
This is one thing MySQL Development Management could consider – if the thing is annoying and it does not take a long to fix it why not to go ahead and make it done instead of spending longer time explaining over and over again why this stuff is not high priority
This feature should help MySQL getting even better results in SpecJAppServer benchmarks as previously it was hard choice – if you want to have fast prepared statements without query cache or no prepared statements with it.
Would this make me use/advice Query Cache more ? Not really. There are enough of over limits with Query Cache which makes it best for small simple applications.
Percona’s widely read Percona Data Performance blog highlights our expertise in enterprise-class software, support, consulting and managed services solutions for both MySQL® and MongoDB® across traditional and cloud-based platforms. The decades of experience represented by our consultants is found daily in numerous and relevant blog posts.
Besides specific database help, the blog also provides notices on upcoming events and webinars.
Want to get weekly updates listing the latest blog posts? Subscribe to our blog now! Submit your email address below and we’ll send you an update every Friday at 1pm ET.