integer TYPE_RESULT_FULL

Hydration Modes As mentioned previously, resultsets are collections of complete objects, this means that every returned result is an object representing a row in the database. These objects can be modified and saved again to persistence: use Store\Toys\Robots; $robots = Robots::find(); // Manipulating a resultset of complete objects foreach ($robots as $robot) { $robot->year = 2000; $robot->save(); } Sometimes records are obtained only to be presented to a user in read-only mo

public string | array getLimit () Returns the current LIMIT clause

public string getAfterPosition () Check whether field absolute to position in table

public path ([mixed $path]) Generates a local path

Source on GitHub Methods abstract public setForm (Phalcon\Forms\Form $form) ... abstract public getForm () ... abstract public setName (mixed $name) ... abstract public getName () ... abstract public setFilters (mixed $filters) ... abstract public addFilter (mixed $filter) ... abstract public getFilters () ... abstract public addValidators (array $validators, [mixed $merge]) ... abstract public addValidator (Phalcon\Validation\ValidatorInterface $validator) ... abstract public getValidators ()

public escapeCss (mixed $css) Escape CSS strings by replacing non-alphanumeric chars by their hexadecimal escaped representation

The session component provides object-oriented wrappers to access session data. Reasons to use this component instead of raw-sessions: You can easily isolate session data across applications on the same domain Intercept where session data is set/get in your application Change the session adapter according to the application needs Starting the Session Some applications are session-intensive, almost any action that performs requires access to session data. There are others who access session da

public getLimit () Get current rows limit

abstract public getControllerName () ...