In the practice of MySQL Support Engineers the trickiest problem of an application is not a crash or something absolutely bad, but wrong logic in tackling a problem. Sometimes, a problem looks simple, but developers could spend several hours to find what is wrong and why. Some of such problems with MySQL occur because of some misunderstanding of MySQL behavior. We’ll present some of the most interesting cases.
Every problem would be examined with its components::
We will show cases affecting different parts of MySQL server, touching several difficult areas of using MySQL features in the wrong way.
Practice shows some MySQL features are more difficult to understand than others. For such features we will show more than one example.
You will know
All our examples come from real cases. Fortunately the Support practics provides lots of such examples. Of course, some of them have been polished on purpose to hide private data or to make the case more clear or to show additional examples of MySQL usage. But every single problem has really occurred in the practice of MySQL Support engineers.
At the end of the presentation we will provide several tips on how to find what is wrong in user application. Especially for complicated features.
I work in MySQL Bugs Group Support since May, 2006. Before I worked as web developer on different projects including web sites and local web-based CRM systems.
Morgan currently works in MySQL Training Team. Before he worked as Support Engineer.
For information on exhibition and sponsorship opportunities at the conference, contact Sharon Cordesse at email@example.com
Download the MySQL Sponsor/Exhibitor Prospectus
For media-related inquiries, contact Maureen Jennings at firstname.lastname@example.org
To stay abreast of conference news and to receive email notification when registration opens, please sign up for the MySQL Conference newsletter.
View a complete list of MySQL contacts.