Before reading this section, it is wise to read the section which explains why Phalcon uses service location and dependency injection. Phalcon\Di is a component implementing Dependency Injection and Location of services and it’s itself a container for them. Since Phalcon is highly decoupled, Phalcon\Di is essential to integrate the different components of the framework. The developer can also use this component to inject dependencies and manage global instances of the different classes used i

Mvc\ModelInterface::setReadConnectionService

abstract public setReadConnectionService (mixed $connectionService) ...

Db\ColumnInterface::__set_state

abstract public static __set_state (array $data) ...

Mvc\Collection\ManagerInterface::getConnection

abstract public getConnection (Phalcon\Mvc\CollectionInterface $model) ...

Mvc\View::start

public start () Starts rendering process enabling the output buffering

Mvc\Model\MetaData\Strategy\Annotations::getColumnMaps

final public getColumnMaps (Phalcon\Mvc\ModelInterface $model, Phalcon\DiInterface $dependencyInjector) Read the model’s column map, this can’t be inferred

DispatcherInterface::setParams

abstract public setParams (mixed $params) ...

Db\Column::getDefault

public getDefault () Default column value

Mvc\Collection::setDI

public setDI (Phalcon\DiInterface $dependencyInjector) Sets the dependency injection container

Db\AdapterInterface::dropForeignKey

abstract public dropForeignKey (mixed $tableName, mixed $schemaName, mixed $referenceName) ...