As always… the devil is in the details….

Never pretended to be an expert of mysql, but going deeper into the mysql api… hm…. I have never seen sthg. as primitive as that. Not primitive as primitive as in “C”, but primitive as in written by primitive people. How the hell can you design an api for prepared statements, where these statements might return randomly 0 to 4294967295 bytes of data, but you will find out only at the end the real length of the data. So what strategy, what memory allocation policy would you use? You keep always hundreds of megabyte of data allocated, in order to be sure that your libmysqclient will not crash your application, as you were too selfish with memory allocation?

And … the big noise lib drizzle. The big thing for the cloud and for the web. And if you read the first lines of specs, you find out that they support almost everything, but nothing from myqsl protocol, including prepared statements. Including in the nothing…