Debugging methods you must master when using ThinkPHP_PHP Tutorial

I often see people asking questions such as what is the return data type of findAll, and the reasons why an error occurs. In fact, I am still not familiar with the built-in debugging methods and methods of ThinkPHP, regardless of the IDE itself. Not to mention the built-in debugging methods, if you are using or planning to use ThinkPHP to develop, then you should understand and master the following methods related to debugging Thinkphp programs.

1. Turn on the debugging mode DEBUG_MODE in the project configuration file, which will allow you to find most of the causes of errors. It may affect the output of verification code.

2. If you don’t want to use debugging mode, you can turn on page Trace display separately. I found that the reason why many people don’t want to use debug mode is actually because of the output of page trace information. In fact, there is a misunderstanding in this, thinking that debug mode must have page trace, but in fact, debug mode and page trace are not necessarily related, just because After turning on debugging mode, the system's default debugging configuration file will enable page Trace display, so you can define a separate debugging configuration file for the project.

3. Use the system-defined dump function. This method can output any type of variable information like var_dump, and is more convenient for viewing in the browser, for example:

$User=D("User");
$list=$User->findAll();
dump($list);

4. The page Trace information can only display the sql statements executed on the current page, but it cannot view the sql statements in the background operations executed in ajax mode, so you can also enable sql logging SQL_DEBUG_LOG to record each executed sql statement, and the execution time of each sql statement can be viewed. The sql log file is located under the Logs directory, and daily sql logs are automatically distinguished by date.

5. Another is if you suspect there is an error in SQL execution after performing a certain data operation, you can use the getLastSql method of the model class to view the last executed SQL statement in order to analyze the specific cause of the error. For example:

$User=D("User");
$User->id=3;
$User->name='ThinkPHp';
$User->save();
echo $User->getLastSql();
//输出结果将为：update think_user set name='ThinkPHP' where id=3;

6. When you need to debug the running time of a certain piece of code, you can use the debug_start($label) and debug_end($label) methods provided by the system, for example:

debug_start('demo');
//这里是你的代码段.......debug_end('demo');

Articles you may be interested in

• The last record of judging volist loop in thinkphp template
• How to set the jump waiting time for thinkphp page jump (successerror)
• thinkphp prints the last sql statement
• Solution to the invalid automatic verification and automatic filling of thinkphp
• Summary of system constants in thinkphp’s Action controller
• Summary of query techniques in ThinkPHP
• Summary of how to use ThinkPHP’s built-in template engine
• How to turn off caching in thinkphp

http://www.bkjia.com/PHPjc/764142.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/764142.htmlTechArticleI often see people asking questions such as what is the return data type of findAll, and I don’t know what went wrong. The reason is that I am still not familiar with ThinkPHP’s built-in debugging methods and...