Security::isLegacyHash

public isLegacyHash (mixed $passwordHash) Checks if a password hash is a valid bcrypt’s hash

FilterInterface::sanitize

abstract public sanitize (mixed $value, mixed $filters) ...

Validation\Validator\InclusionIn

extends abstract class Phalcon\Validation\Validator implements Phalcon\Validation\ValidatorInterface Source on GitHub Check if a value is included into a list of values use Phalcon\Validation\Validator\InclusionIn; $validator->add('status', new InclusionIn([ 'message' => 'The status must be A or B', 'domain' => array('A', 'B') ])); $validator->add(['status', 'type'], new InclusionIn([ 'message' => [ 'status' => 'The status must be A or B',

Mvc\Model\Query\Builder::rightJoin

public Phalcon\Mvc\Model\Query\Builder rightJoin (string $model, [string $conditions], [string $alias]) Adds a RIGHT join to the query $builder->rightJoin('Robots', 'r.id = RobotsParts.robots_id', 'r');

Mvc\Model\Validator\Regex

extends abstract class Phalcon\Mvc\Model\Validator implements Phalcon\Mvc\Model\ValidatorInterface Source on GitHub Allows validate if the value of a field matches a regular expression use Phalcon\Mvc\Model\Validator\Regex as RegexValidator; class Subscriptors extends \Phalcon\Mvc\Model { public function validation() { $this->validate(new RegexValidator(array( "field" => 'created_at', 'pattern' => '/^[0-9]{4}[-\/](0[1-9]|1[12])[-\/](0[1-9]|[12][0-9]|3[01

Understanding How Phalcon Applications Work

If you’ve been following the tutorial or have generated the code using Phalcon Devtools, you may recognize the following bootstrap file: use Phalcon\Mvc\Application; // Register autoloaders // ... // Register services // ... // Handle the request $application = new Application($di); try { $response = $application->handle(); $response->send(); } catch (\Exception $e) { echo "Exception: ", $e->getMessage(); } The core of all the work of the controller occurs when handle

Mvc\Model\Query\Lang

Source on GitHub PHQL is implemented as a parser (written in C) that translates syntax in that of the target RDBMS. It allows Phalcon to offer a unified SQL language to the developer, while internally doing all the work of translating PHQL instructions to the most optimal SQL instructions depending on the RDBMS type associated with a model. To achieve the highest performance possible, we wrote a parser that uses the same technology as SQLite. This technology provides a small in-memory parser wi

Acl\AdapterInterface::deny

abstract public deny (mixed $roleName, mixed $resourceName, mixed $access, [mixed $func]) ...

Mvc\Model\Query\BuilderInterface::orWhere

abstract public orWhere (mixed $conditions, [mixed $bindParams], [mixed $bindTypes]) ...

Cache\Multiple

Source on GitHub Allows to read to chained backend adapters writing to multiple backends use Phalcon\Cache\Frontend\Data as DataFrontend, Phalcon\Cache\Multiple, Phalcon\Cache\Backend\Apc as ApcCache, Phalcon\Cache\Backend\Memcache as MemcacheCache, Phalcon\Cache\Backend\File as FileCache; $ultraFastFrontend = new DataFrontend(array( "lifetime" => 3600 )); $fastFrontend = new DataFrontend(array( "lifetime" => 86400 )); $slowFront