Relationships between Models There are four types of relationships: one-on-one, one-to-many, many-to-one and many-to-many. The relationship may be unidirectional or bidirectional, and each can be simple (a one to one model) or more complex (a combination of models). The model manager manages foreign key constraints for these relationships, the definition of these helps referential integrity as well as easy and fast access of related records to a model. Through the implementation of relations, i

public getControllerName () Gets the name of the controller rendered

integer CRITICAL

All the hard work behind orchestrating the operation of MVC in Phalcon is normally done by Phalcon\Mvc\Application. This component encapsulates all the complex operations required in the background, instantiating every component needed and integrating it with the project, to allow the MVC pattern to operate as desired. Single or Multi Module Applications With this component you can run various types of MVC structures: Single Module Single MVC applications consist of one module only. Namespaces

public getCompiler () Returns the Volt’s compiler

public getEventsManager () Returns the internal event manager

public slice (mixed $value, [mixed $start], [mixed $end]) Extracts a slice from a string/array/traversable object value

extends class Phalcon\Exception implements Throwable Source on GitHub Methods final private Exception __clone () inherited from Exception Clone the exception public __construct ([string $message], [int $code], [Exception $previous]) inherited from Exception Exception constructor public __wakeup () inherited from Exception ... final public string getMessage () inherited from Exception Gets the Exception message final public int getCode () inherited from Exception Gets the Exception code fin

public setNamespaceName (mixed $namespaceName) Sets the namespace where the controller class is

public getDefaultAction () Returns the default ACL access level