My MySQL musings, sometimes code snippets and commentry.
Hi Antony.I am very much interested.Provided that you don't come up with some unpleasant discovery the day of your session.:)Giuseppe
This would be a great topic. There are many questions people have about whether they should use stored procedures in MySQL or not (unlike Oracle and MSSQL, where procedures are de rigeur).This talk should not only give tips on how to write good-performing procedures, but also give guidelines for when it's appropriate to write a procedure all, or just use plain SQL.Include techniques for measuring performance of a stored proc versus a set of direct SQL queries to accomplish the same task. You can show improvements only by measuring and then comparing performance of two different solutions.
I think it would be *very interesting* to see benchmarks of programming logic implemented in* 'stored programs'* application (most important C/C++, Perl, JAVA, C#/.NET) code.* a combination of thoseBasically we all ask ourselves all the time: shall we use 'stored programs' or not? And when and when not? And where and where not!
Sounds like I would attend that one
Sounds like fantasy to me. :)How about "how to use stored procedures and not kill your database?"Or actually one that might be nice -- "using views and stored procedures instead of ORM's for a programming interface into the database."that title's not so catchy. But I'm wary of "high performance stored procedures" because procedural code is probably *medium* performance at best.
Post a Comment