public execute () Allows to execute the statement again. Some database systems don’t support scrollable cursors, So, as cursors are forward only, we need to execute the cursor again to fetch rows from the begining

abstract public create ([mixed $data], [mixed $whiteList]) ...

public validate (Phalcon\Validation $validation, mixed $field) Executes the validation

public array getArguments () Returns the expression arguments

integer BELONGS_TO

extends abstract class Phalcon\Validation\Validator implements Phalcon\Validation\ValidatorInterface Source on GitHub Checks if a value has a correct file use Phalcon\Validation\Validator\File as FileValidator; $validator->add('file', new FileValidator([ 'maxSize' => '2M', 'messageSize' => ':field exceeds the max filesize (:max)', 'allowedTypes' => array('image/jpeg', 'image/png'), 'messageType' => 'Allowed file types are :types', 'maxResolution' =>

public validate (Phalcon\Validation $validation, mixed $field) Executes the validation

public validate (Phalcon\Validation $validation, mixed $field) Executes the validation

public getScheme () Gets HTTP schema (http/https)

The following example is a bit lengthy, but it attempts to explain why Phalcon uses service location and dependency injection. First, let’s pretend we are developing a component called SomeComponent. This performs a task that is not important now. Our component has some dependency that is a connection to a database. In this first example, the connection is created inside the component. This approach is impractical; due to the fact we cannot change the connection parameters or the type of databa