


Briefly introduce the specific differences between ThinkPHP5.0 and ThinkPHP3.2
The editor will bring you a brief discussion on the difference between ThinkPHP5.0 version and ThinkPHP3.2 version. The editor thinks it’s pretty good, so I’ll share it with you now and give it as a reference. Let’s follow the editor and take a look.
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 the 3.2 version.
URL and routing
5.0 URL access no longer supports ordinary URL mode, routing does not support regular routing definitions, but all changes The way to match variable rules (regular definition) 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 definitionAnd access;
URL access supports automatic positioning of the controller;
Database
The database query function of 5.0 has been enhanced, which originally required passing The chain query that can only be used by the model 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
M('User')->where(['name'=>'thinkphp'])->find();
5.0 version
db('User')->where('name','thinkphp')->find();
The main improvements are as follows:
Support chain query operations;
Data query supports returning objects, arrays and PDOStatement objects;
Data set queries support returning arrays and Collection objects;
Add query constructor, query syntax changes;
Support closure query;
Support block query;
Support view query;
Add SQL listening event;
Model
The model change of 5.0 is 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 represented by Namespace distinction, the original D function call is changed to the model function, and the corresponding model class must be created, 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 the aggregation model;
Abolish the view model (change 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 serializationSupport;
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 uses verification. Device definition and unified verification through 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 redesigned the exception page to display detailed error information to facilitate 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, 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 core framework does not rely on any custom functions, but still encapsulates some common functions into helper functions, and you can redefine them at will. Define or add helper functions.
The above is the detailed content of Briefly introduce the specific differences between ThinkPHP5.0 and ThinkPHP3.2. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

JWT is an open standard based on JSON, used to securely transmit information between parties, mainly for identity authentication and information exchange. 1. JWT consists of three parts: Header, Payload and Signature. 2. The working principle of JWT includes three steps: generating JWT, verifying JWT and parsing Payload. 3. When using JWT for authentication in PHP, JWT can be generated and verified, and user role and permission information can be included in advanced usage. 4. Common errors include signature verification failure, token expiration, and payload oversized. Debugging skills include using debugging tools and logging. 5. Performance optimization and best practices include using appropriate signature algorithms, setting validity periods reasonably,

Session hijacking can be achieved through the following steps: 1. Obtain the session ID, 2. Use the session ID, 3. Keep the session active. The methods to prevent session hijacking in PHP include: 1. Use the session_regenerate_id() function to regenerate the session ID, 2. Store session data through the database, 3. Ensure that all session data is transmitted through HTTPS.

The enumeration function in PHP8.1 enhances the clarity and type safety of the code by defining named constants. 1) Enumerations can be integers, strings or objects, improving code readability and type safety. 2) Enumeration is based on class and supports object-oriented features such as traversal and reflection. 3) Enumeration can be used for comparison and assignment to ensure type safety. 4) Enumeration supports adding methods to implement complex logic. 5) Strict type checking and error handling can avoid common errors. 6) Enumeration reduces magic value and improves maintainability, but pay attention to performance optimization.

The application of SOLID principle in PHP development includes: 1. Single responsibility principle (SRP): Each class is responsible for only one function. 2. Open and close principle (OCP): Changes are achieved through extension rather than modification. 3. Lisch's Substitution Principle (LSP): Subclasses can replace base classes without affecting program accuracy. 4. Interface isolation principle (ISP): Use fine-grained interfaces to avoid dependencies and unused methods. 5. Dependency inversion principle (DIP): High and low-level modules rely on abstraction and are implemented through dependency injection.

Static binding (static::) implements late static binding (LSB) in PHP, allowing calling classes to be referenced in static contexts rather than defining classes. 1) The parsing process is performed at runtime, 2) Look up the call class in the inheritance relationship, 3) It may bring performance overhead.

RESTAPI design principles include resource definition, URI design, HTTP method usage, status code usage, version control, and HATEOAS. 1. Resources should be represented by nouns and maintained at a hierarchy. 2. HTTP methods should conform to their semantics, such as GET is used to obtain resources. 3. The status code should be used correctly, such as 404 means that the resource does not exist. 4. Version control can be implemented through URI or header. 5. HATEOAS boots client operations through links in response.

In PHP, exception handling is achieved through the try, catch, finally, and throw keywords. 1) The try block surrounds the code that may throw exceptions; 2) The catch block handles exceptions; 3) Finally block ensures that the code is always executed; 4) throw is used to manually throw exceptions. These mechanisms help improve the robustness and maintainability of your code.

The main function of anonymous classes in PHP is to create one-time objects. 1. Anonymous classes allow classes without names to be directly defined in the code, which is suitable for temporary requirements. 2. They can inherit classes or implement interfaces to increase flexibility. 3. Pay attention to performance and code readability when using it, and avoid repeatedly defining the same anonymous classes.
