About the difference between ThinkPHP5.0 version and ThinkPHP3.2 version

This article mainly introduces the difference between ThinkPHP5.0 version and ThinkPHP3.2 version. It has a certain reference value. Now I share it with you. Friends in need can refer to

5.0 version and previous versions. The versions are quite different. This article gives some of the main differences in 5.0 for users who are familiar with version 3.2.

URL and routing

5.0 URL access no longer supports ordinary URL mode, routing does not support regular routing definitions, but all changes How to match variable rules (regular definitions) for rule routing:

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 routing definition;
Support URL routing rule anti-parsing;

Request object and response object

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

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 of the controller;

Database

5.0's database query function is enhanced, and the chain that originally needed to be used through the model The query can be called directly through the Db class. The original M function call can be changed to the db function, for example:

3.2 version

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

The main improvements are as follows:Support chained query operations;

Data set queries support returning arrays and Collection objects;
Add query constructor , query syntax changes;
supports closure query;
supports block query;
supports view query;
adds SQL listening events;

5.0’s 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, and is directly distinguished by the namespace. The original The D function call is changed to the model function, and the corresponding model class must be created, for example:

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

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

##Main improvements include:

Reconstruct the association model; Support the aggregation model; Abolish the view model (change to the view query method of the database);

Add access Modifiers and modifiers;
Add automatic writing of timestamps;
Add type field conversion;
Array access support;
JSON serialization support;



Automatic verification and automatic completion

The automatic verification and automatic completion of data in 5.0 are quite different from those in version 3.2. The data verification in 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 and will throw exceptions for any level of errors by default (but can be used in application public files Set the error level in), and the exception page has been redesigned to display detailed error information for easy debugging.

Debugging and logging

5.0 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, and the rest of the constants can be used Use the relevant attributes or methods of the App class or Request class to complete, 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

The 5.0 version of the core framework does not rely on any custom functions, but it still encapsulates some common functions into helper functions. You can redefine or add helper functions at will.

The above is the entire content of this article. I hope it will be helpful to everyone's study. For more related content, please pay attention to the PHP Chinese website!

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