MySQL trigger Management

MySQL does not have a client like MSSQL to manage, so with phpMyAdmin, managing MySQL does not rely solely on command lines, but phpMyAdmin does not seem to be so omnipotent and occasionally

MySQL does not have a client like MSSQL to manage, so with phpMyAdmin, managing MySQL does not rely solely on command lines, but phpMyAdmin does not seem to be so omnipotent and occasionally

MySQL does not have a client like MSSQL to manage, so with phpMyAdmin, managing MySQL does not rely solely on command lines. However, phpMyAdmin does not seem to be so omnipotent, and occasionally plays tricks on version details.

I recently used a MySQL trigger and didn't want to use the command line to edit it. However, phpMyAdmin debugging is not difficult. I originally wanted to create an empty trigger and then modify it, later, I found that there were many problems with migration modification. With the help of Old Wang, I worked hard several nights to sort out some rules.

When debugging, you can add a statement one by one on an empty trigger and debug it at. This makes it easy to locate the problem and modify it quickly.

During the migration, you cannot directly edit the code in the trigger copy. The phpMyAdmin version I used is 2.11.9 *. Although the generated code is recognized by him, a migration problem occurs, I haven't read the phpMyAdmin code yet. I don't know how to generate the code, but the content in the begin end is roughly the same. The difference is the auxiliary statements at both ends.

The content at both ends is closely related to the version. You can use MySQLdump to export the statement as a template and add the process to it. Basically, there is no problem.

The syntaxes of different versions are slightly different and are not summarized in detail. After mastering the debugging method, the problem solving speed will be improved.

After the trigger is used, a dozen interactions can be solved at a time. I tried the provisioner and stored procedure and found that the development cost was similar and the complexity was similar, so no stored procedure was used.