If you need to set automatic verification or automatic completion before version 3.1, it is generally necessary to define it in the model or use the setProperty method to dynamically set attributes. The disadvantage is that it is not convenient to dynamically change and adjust attributes. However, version 3.1 adds two coherent operations: auto and validate in the model class, which are used to dynamically set automatic completion and automatic verification rules. Currently, they can be used in Action: Before version 3.1, if you need to set automatic verification or automatic completion, it must be defined in the model or set attributes dynamically using the setProperty method. The disadvantage is that it is not convenient to dynamically change and adjust attributes.
However, version 3.1 is added to the model class.
Auto and validateTwo coherent operations are used to dynamically set automatic completion and automatic verification rules. now you can use the following operations in Action:
- $ Validate = array (
- Array ('verify ', 'require', 'verification code is required! '),
- Array ('name', '', 'account name already exists! ', 0, 'Unique', 1 ),
- );
- $ Auto = array (
- Array ('password', 'md5', 1, 'Function '),
- Array ('create _ time', 'time', 2, 'Function '),
- );
- M ('user')-> auto ($ auto)-> validate ($ validate)-> create ();
Copy the code where the $ auto and $ validate variables are consistent with the definition rules of the _ auto and _ validate attributes of the model class, and function calling is also supported (due to PHP restrictions, you cannot call a function in the attribute definition of a class ).
The auto and validate methods must be called before the create method.
With this improvement, you can use the M method to instantiate the model class and then use dynamic settings to complete automatic verification and operations without relying on the D method.
