Db::FETCH_LAZY

integer FETCH_LAZY

Tutorial 3: Securing INVO

In this chapter, we continue explaining how INVO is structured, we’ll talk about the implementation of authentication, authorization using events and plugins and an access control list (ACL) managed by Phalcon. Log into the Application A “log in” facility will allow us to work on backend controllers. The separation between backend controllers and frontend ones is only logical. All controllers are located in the same directory (app/controllers/). To enter the system, users must have a valid user

Mvc\Model\MetaData\Session::MODELS_DATA_TYPES

integer MODELS_DATA_TYPES

Mvc\Model\MetaData\Files::MODELS_NON_PRIMARY_KEY

integer MODELS_NON_PRIMARY_KEY

Text::RANDOM_NUMERIC

integer RANDOM_NUMERIC

Tag::textArea

public static string textArea (array $parameters) Builds a HTML TEXTAREA tag echo Phalcon\Tag::textArea(array("comments", "cols" => 10, "rows" => 4)) Volt syntax: {{ text_area("comments", "cols": 10, "rows": 4) }}

Mvc\Micro::get

public Phalcon\Mvc\Router\RouteInterface get (string $routePattern, callable $handler) Maps a route to a handler that only matches if the HTTP method is GET

Mvc\Model\Transaction\Manager::notifyCommit

public notifyCommit (Phalcon\Mvc\Model\TransactionInterface $transaction) Notifies the manager about a committed transaction

Session\AdapterInterface::remove

abstract public remove (mixed $index) ...

Db\Dialect\Postgresql::describeIndexes

public describeIndexes (mixed $table, [mixed $schema]) Generates SQL to query indexes on a table