Mvc\Model\MetaDataInterface::hasAttribute

abstract public hasAttribute (Phalcon\Mvc\ModelInterface $model, mixed $attribute) ...

Mvc\Model\CriteriaInterface::getModelName

abstract public getModelName () ...

Version::VERSION_SPECIAL_NUMBER

integer VERSION_SPECIAL_NUMBER

Mvc\View\Simple::cache

public cache ([mixed $options]) Cache the actual view render to certain level $this->view->cache(['key' => 'my-key', 'lifetime' => 86400]);

Mvc\Model\Query::setType

public setType (mixed $type) Sets the type of PHQL statement to be executed

Working with Namespaces

Namespaces can be used to avoid class name collisions; this means that if you have two controllers in an application with the same name, a namespace can be used to differentiate them. Namespaces are also useful for creating bundles or modules. Setting up the framework Using namespaces has some implications when loading the appropriate controller. To adjust the framework behavior to namespaces is necessary to perform one or all of the following tasks: Use an autoload strategy that takes into acc

Registry::offsetSet

final public offsetSet (mixed $offset, mixed $value) Sets an element in the registry

Translate\Interpolator\AssociativeArray

implements Phalcon\Translate\InterpolatorInterface Source on GitHub Methods public replacePlaceholders (mixed $translation, [mixed $placeholders]) Replaces placeholders by the values passed

Cli\Router::getParams

public array getParams () Returns processed extra params

Mvc\Model::getOperationMade

public getOperationMade () Returns the type of the latest operation performed by the ORM Returns one of the OP_* class constants