MySQL存储过程调试（国外英文资料）.doc

MySQL存储过程调试（国外英文资料） Stored procedure is performed for the database server program, they often use database language such as PL/SQL or ANSI SQL: 2003 the SQL/PSM writing (writing some database also supports Java stored procedure, but Im here does not carry on the analysis), currently on the market also has a lot of learning to write books stored procedure, the author recommended reading Guy Harrison MySQL stored procedure programming, and Jonathan Gennick and Tom Luers co-authored the 21 days self-study PL/SQL, why to write a stored procedure, sums up about three reasons: 1, the logic may be the database logic is implemented, so using database language easier than using conventional programming languages such as Java to solve the problem; Stored procedures are much faster than Java, and can be more often called by the database; Stored procedures are safer. Whatever the reason for writing the stored procedure, the question now is how to debug it. The wrong way In debugging SQL stored procedure: suppose the main logic is your stored procedure DDL and DML operation, this method can work, in other words, only statements, such as query, insert, and assuming that other stored procedure mainly undertake the support database operations, in most cases this assumption is true, after all, if a stored procedure is not operation database, you probably would not specially write a stored procedure. There is no doubt that no matter how much the SQL stored procedure included code, you need to validate the SQL itself, especially because this level of testing is relatively simple, only need to start the database command line tools or query browser GUI, paste in the SQL statements executed once know whether it is right: no, of course, this is beyond the simple grammatical correctness check, you must personally verify the correctness of the syntax. But in some cases its as simple as it might be, for two reasons. First of all, your SQL code can (usually will) rely on stored procedures and