Home  >  Article  >  Backend Development  >  Detailed explanation of the difference between ThinkPHP5.0 and ThinkPHP3.2 versions

Detailed explanation of the difference between ThinkPHP5.0 and ThinkPHP3.2 versions

小云云
小云云Original
2018-02-12 14:25:421776browse

The 5.0 version is quite different from the previous version. This article gives some of the main differences in 5.0 for users who are familiar with version 3.2. This article mainly shares with you the differences between ThinkPHP5.0 version and ThinkPHP3.2 version. The editor thinks it is quite good, so I will share it with you now and give it as a reference for everyone. Let’s follow the editor to take a look, I hope it can help everyone.

URL and routing

5.0’s URL access no longer supports ordinary URL mode, and routing does not support regular routing definitions. Instead, it is all changed to rule routing with variable rules (regular definitions). :

The main improvements are as follows:

Add routing variable rules;
Add combination variable support;
Add resource routing;
Add routing grouping;
Add closure Definition support;
Add MISS route definition;
Support URL routing rule anti-parsing;

Request object and response object

5.0 adds request object Request and response object Response. Request uniformly processes requests and obtains request information, and the Response object is responsible for outputting the client or browser response.

Modules and Controllers

The namespace of the controller has been adjusted, and there is no need to inherit any controller class.

The application namespace is unified as app (definable) instead of module name;
The class name of the controller does not have the Controller suffix by default. You can configure the use_controller_suffix parameter to enable the controller class suffix;
Control The controller operation method uses the return method to return data instead of direct output;
Abolish the original pre- and post-operation methods;
Add the beforeActionList attribute to define the pre-operation;
Support any level of controller definition and access;
URL access supports automatic positioning controller;

Database

The database query function of 5.0 has been enhanced. The chain query that originally needed to be used through the model can be called directly through the Db class. The original M function You can use the db function instead, for example:

3.2 version

M('User')->where(['name'=>'thinkphp'])->find ();

5.0 version

db('User')->where('name','thinkphp')->find();

The main improvements are as follows:

Support chained query operations;
Data query supports returning objects, arrays and PDOStatement objects;
Data set query supports returning arrays and Collection objects;
Add query Constructor, query syntax changes;
Support closure query;
Support block query;
Support view query;
Add SQL listening events;

Model

5.0 model changes are the biggest. Basically, the model is a completely object-oriented concept, including associated models. The suffix of the model class no longer carries Model, but is directly distinguished by the namespace. The original D function call is changed to the model function, and must Create the corresponding model class, for example:

3.2 version

D('User')->where(['name'=>'thinkphp'])->find( );

5.0 version

model('User')->where('name','thinkphp')->find();

Main improvements include:

Reconstruct the association model;
Support aggregation model;
Abolish the view model (changed to the view query method of the database);
The extension of the model adopts the Trait mechanism;
Add getters and modifiers;
Add timestamp automatic writing;
Add type field conversion;
Array access support;
JSON serialization support;

Automatic verification And automatic completion

The automatic data verification and automatic completion of 5.0 are quite different from the 3.2 version. The data verification of 5.0 adopts the validator definition and performs unified verification through the think\Validate class. Automatic completion is accomplished by defining modifiers in the model.

Exceptions

5.0 has zero tolerance for errors. By default, exceptions will be thrown for any level of error (but the error level can be set in the application public file), and the exception page has been redesigned , showing detailed error information for easy debugging.

Debugging and logging

5.0’s page Trace enhancement supports browser console viewing of Trace information.

5.0’s log driver adds Socket mode and uses SocketLog to support remote debugging.

Constant

The 5.0 version abandoned most of the original constant definitions, only retaining the framework's path constant definitions. The remaining constants can be completed using the relevant attributes or methods of the App class or Request class. , or redefine the required constants yourself.

The deprecated constants include:

REQUEST_METHOD IS_GET IS_POST IS_PUT IS_DELETE IS_AJAX __EXT__ COMMON_MODULE MODULE_NAME CONTROLLER_NAME ACTION_NAME APP_NAMESPACE APP_DEBUG MODULE_PATH

Function

5.0 version core framework does not depend on Any custom function, but still encapsulates some common functions into helper functions, you can redefine or add helper functions at will.

Related recommendations:

ThinkPHP5.0 implementation of image upload plug-in example sharing

Recommended 10 articles about thinkPHP5.0 framework

thinkPHP5.0 framework simple configuration scope code example

The above is the detailed content of Detailed explanation of the difference between ThinkPHP5.0 and ThinkPHP3.2 versions. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn