News for hackers. Stuff that matters.
Re:MySQL is bazillion times faster than MemSQL by jakejake on Tuesday June 26, 2012 @04:15PM (#4163889)
That's why prepared statements are preferable because those two statements have to be parsed as unique queries. They are actually the same query with different parameters.

As far as I know that's the same on just about all databases.

Re:MySQL is bazillion times faster than MemSQL by bazzargh on Tuesday June 26, 2012 @07:53PM (#4164793)
At least some databases I've used have parsed out constants in the client library code and submitted prepared statements to the server, passing those constants in. That meant that the server got better use out of its query cache; on the server side, those are the same query.

Not sure which ones if any do this today, the optimisation might no longer be relevant - I spotted DBs doing this 10 years ago when CGIs that didn't bother with prepared statements were rife.

Re:MySQL is bazillion times faster than MemSQL by dhruvbird on Tuesday June 26, 2012 @05:12PM (#4164157)
@nikita I see: http://developers.memsql.com/docs/1b/faq.html#does-this-mean...

Do you mean you determine placeholders without actually parsing the SQL?

@jakejake The docs. seem to suggest that the benefits of prepared statements are won without using prepared statements in MemSQL.

Re:MySQL is bazillion times faster than MemSQL by nikita on Tuesday June 26, 2012 @04:58PM (#4164086)
Not every parsing is equal. MySQL and other databases produce a tree as they parse a query. If you just want to match parameters you can avoid memory allocations and just replace parameters with ^ or @ signed in place in the query string.

http://developers.memsql.com/docs/1b/faq.html gives some more details.