Based on my master class on PHPConf 2009 (
http://phpconf.ru ), I wrote a guide for those who need to catch an error in the SQL application. It would be more correct to call it in the MySQL application, but I still think that the general principles are the same for everyone. Ideally, I would like the text to cover the main cases of misbehavior. I’ll make a reservation that by misbehaving I understand logical errors, not performance problems. Performance issues are a separate topic, by the way, fairly well represented on the network.
The book consists of 4 parts, below you can see a summary:
Part 1. Single requests.Cases when the error repeats for one client-stream are considered.
')
Part 2. Competitive requests.Cases where the error is repeated only in cases where several clients work with the database at the same time.
Part 3. Other cases.Cases that do not fit the previous definitions.
Part 4. Techniques used for debugging Production applications.A short list of what needs to be done if you have to test on a production server.
The text turned out to be quite voluminous, so I thought it necessary to give a link to an external resource, and not to lay out here, as it turned out quite a lot of bukaf, and several posts in a row on one topic can be tiring.
Please read and criticize. Your opinion is very interesting. Comments leave here :)
You can
read here:
sql-error.microbecal.com