


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!

Absolute session timeout starts at the time of session creation, while an idle session timeout starts at the time of user's no operation. Absolute session timeout is suitable for scenarios where strict control of the session life cycle is required, such as financial applications; idle session timeout is suitable for applications that want users to keep their session active for a long time, such as social media.

The server session failure can be solved through the following steps: 1. Check the server configuration to ensure that the session is set correctly. 2. Verify client cookies, confirm that the browser supports it and send it correctly. 3. Check session storage services, such as Redis, to ensure that they are running normally. 4. Review the application code to ensure the correct session logic. Through these steps, conversation problems can be effectively diagnosed and repaired and user experience can be improved.

session_start()iscrucialinPHPformanagingusersessions.1)Itinitiatesanewsessionifnoneexists,2)resumesanexistingsession,and3)setsasessioncookieforcontinuityacrossrequests,enablingapplicationslikeuserauthenticationandpersonalizedcontent.

Setting the httponly flag is crucial for session cookies because it can effectively prevent XSS attacks and protect user session information. Specifically, 1) the httponly flag prevents JavaScript from accessing cookies, 2) the flag can be set through setcookies and make_response in PHP and Flask, 3) Although it cannot be prevented from all attacks, it should be part of the overall security policy.

PHPsessionssolvetheproblemofmaintainingstateacrossmultipleHTTPrequestsbystoringdataontheserverandassociatingitwithauniquesessionID.1)Theystoredataserver-side,typicallyinfilesordatabases,anduseasessionIDstoredinacookietoretrievedata.2)Sessionsenhances

PHPsessionscanstorestrings,numbers,arrays,andobjects.1.Strings:textdatalikeusernames.2.Numbers:integersorfloatsforcounters.3.Arrays:listslikeshoppingcarts.4.Objects:complexstructuresthatareserialized.

TostartaPHPsession,usesession_start()atthescript'sbeginning.1)Placeitbeforeanyoutputtosetthesessioncookie.2)Usesessionsforuserdatalikeloginstatusorshoppingcarts.3)RegeneratesessionIDstopreventfixationattacks.4)Considerusingadatabaseforsessionstoragei

Session regeneration refers to generating a new session ID and invalidating the old ID when the user performs sensitive operations in case of session fixed attacks. The implementation steps include: 1. Detect sensitive operations, 2. Generate new session ID, 3. Destroy old session ID, 4. Update user-side session information.


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

mPDF
mPDF is a PHP library that can generate PDF files from UTF-8 encoded HTML. The original author, Ian Back, wrote mPDF to output PDF files "on the fly" from his website and handle different languages. It is slower than original scripts like HTML2FPDF and produces larger files when using Unicode fonts, but supports CSS styles etc. and has a lot of enhancements. Supports almost all languages, including RTL (Arabic and Hebrew) and CJK (Chinese, Japanese and Korean). Supports nested block-level elements (such as P, DIV),

Zend Studio 13.0.1
Powerful PHP integrated development environment

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

SublimeText3 Linux new version
SublimeText3 Linux latest version

PhpStorm Mac version
The latest (2018.2.1) professional PHP integrated development tool
