# 使用模型（Working with Models）[](# "永久链接至标题")
模型代表了应用程序中的信息（数据）和处理数据的规则。模型主要用于管理与相应数据库表进行交互的规则。大多数情况中，在应用程序中，数据库中每个表将对应一个模型。应用程序中的大部分业务逻辑都将集中在模型里。
[*Phalcon\Mvc\Model*](#) 是 Phalcon 应用程序中所有模型的基类。它保证了数据库的独立性，基本的 CURD 操作，高级的查询功能，多表关联等功能。[*Phalcon\Mvc\Model*](#) 不需要直接使用 SQL 语句，因为它的转换方法，会动态的调用相应的数据库引擎进行处理。
> 模型是数据库的高级抽象层。如果您想进行低层次的数据库操作，您可以查看[*Phalcon\Db*](#) 组件文档。
### 创建模型[](# "永久链接至标题")
模型是一个继承自 [*Phalcon\Mvc\Model*](#) 的一个类。 它必须放到 models 文件夹。一个模型文件必须包含一个类，同时它的类名必须符合驼峰命名法：
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
}
~~~
上面的例子显示了 “Robots” 模型的实现。 需要注意的是 Robots 继承自 [*Phalcon\Mvc\Model*](#) 。因此，Robots 模型拥有了大量继承自该组件功能，包括基本的数据库 CRUD (Create, Read, Update, Delete) 操作，数据验证以及复杂的搜索支持，并且可以同时关联多个模型。
> 如果使用 PHP 5.4/5.5 建议在模型中预先定义好所有的列，这样可以减少模型内存的开销以及内存分配。
默认情况下，模型 “Robots” 对应的是数据库表 “robots”， 如果想映射到其他数据库表，可以使用 getSource() 方法：
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public function getSource()
{
return "the_robots";
}
}
~~~
模型 Robots 现在映射到了 “the_robots” 表。initialize() 方法可以帮助在模型中建立自定义行为，例如指定不同的数据库表。initialize() 方法在请求期间只被调用一次。
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public function initialize()
{
$this->setSource("the_robots");
}
}
~~~
initialize() 方法在请求期间仅会被调用一次，目的是为应用中所有该模型的实例进行初始化。如果需要为每一个实例在创建的时候单独进行初始化，可以使用 ‘onConstruct' 事件：
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public function onConstruct()
{
// ...
}
}
~~~
### 公共属性对比设置与取值 Setters/Getters（Public properties vs. Setters/Getters）[](# "永久链接至标题")
模型可以通过公共属性的方式实现，意味着模型的所有属性在实例化该模型的地方可以无限制的读取和更新。
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public $id;
public $name;
public $price;
}
~~~
通过使用 getters/setters 方法，可以控制哪些属性可以公开访问，并且对属性值执行不同的形式的转换，同时可以保存在模型中的数据添加相应的验证规则。
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
protected $id;
protected $name;
protected $price;
public function getId()
{
return $this->id;
}
public function setName($name)
{
// The name is too short?
if (strlen($name) < 10) {
throw new \InvalidArgumentException('The name is too short');
}
$this->name = $name;
}
public function getName()
{
return $this->name;
}
public function setPrice($price)
{
// Negative prices aren't allowed
if ($price < 0) {
throw new \InvalidArgumentException('Price can\'t be negative');
}
$this->price = $price;
}
public function getPrice()
{
// Convert the value to double before be used
return (double) $this->price;
}
}
~~~
公共属性的方式可以在开发中降低复杂度。而 getters/setters 的实现方式可以显著的增强应用的可测试性、扩展性和可维护性。开发人员可以自己决定哪一种策略更加适合自己开发的应用。ORM同时兼容这两种方法。
### 模型放入命名空间（Models in Namespaces）[](# "永久链接至标题")
命名空间可以用来避免类名的冲突。ORM通过类名来映射相应的表名。比如 ‘Robots'：
~~~
<?php
namespace Store\Toys;
use Phalcon\Mvc\Model;
class Robots extends Model
{
// ...
}
~~~
Namespaces make part of model names when they are within strings:
~~~
<?php
namespace Store\Toys;
use Phalcon\Mvc\Model;
class Robots extends Model
{
public $id;
public $name;
public function initialize()
{
$this->hasMany('id', 'Store\Toys\RobotsParts', 'robots_id');
}
}
~~~
### 理解记录对象（Understanding Records To Objects）[](# "永久链接至标题")
每个模型的实例对应一条数据表中的记录。可以方便的通过读取对象的属性来访问相应的数据。比如，一个表 “robots” 有如下数据：
~~~
mysql> select * from robots;
+----+------------+------------+------+
| id | name | type | year |
+----+------------+------------+------+
| 1 | Robotina | mechanical | 1972 |
| 2 | Astro Boy | mechanical | 1952 |
| 3 | Terminator | cyborg | 2029 |
+----+------------+------------+------+
3 rows in set (0.00 sec)
~~~
你可以通过主键找到某一条记录并且打印它的名称：
~~~
<?php
// Find record with id = 3
$robot = Robots::findFirst(3);
// Prints "Terminator"
echo $robot->name;
~~~
一旦记录被加载到内存中之后，你可以修改它的数据并保存所做的修改：
~~~
<?php
$robot = Robots::findFirst(3);
$robot->name = "RoboCop";
$robot->save();
~~~
如上所示，不需要写任何SQL语句。[*Phalcon\Mvc\Model*](#) 为web应用提供了高层数据库抽象。
### 查找记录（Finding Records）[](# "永久链接至标题")
[*Phalcon\Mvc\Model*](#) 为数据查询提供了多种方法。下面的例子将演示如何从一个模型中查找一条或者多条记录：
~~~
<?php
// How many robots are there?
$robots = Robots::find();
echo "There are ", count($robots), "\n";
// How many mechanical robots are there?
$robots = Robots::find("type = 'mechanical'");
echo "There are ", count($robots), "\n";
// Get and print virtual robots ordered by name
$robots = Robots::find(
array(
"type = 'virtual'",
"order" => "name"
)
);
foreach ($robots as $robot) {
echo $robot->name, "\n";
}
// Get first 100 virtual robots ordered by name
$robots = Robots::find(
array(
"type = 'virtual'",
"order" => "name",
"limit" => 100
)
);
foreach ($robots as $robot) {
echo $robot->name, "\n";
}
~~~
> If you want find record by external data (such as user input) or variable data you must use [`Binding Parameters`_](#).
你可以使用 findFirst() 方法获取第一条符合查询条件的结果：
~~~
<?php
// What's the first robot in robots table?
$robot = Robots::findFirst();
echo "The robot name is ", $robot->name, "\n";
// What's the first mechanical robot in robots table?
$robot = Robots::findFirst("type = 'mechanical'");
echo "The first mechanical robot name is ", $robot->name, "\n";
// Get first virtual robot ordered by name
$robot = Robots::findFirst(
array(
"type = 'virtual'",
"order" => "name"
)
);
echo "The first virtual robot name is ", $robot->name, "\n";
~~~
find() 和 findFirst() 方法都接受关联数组作为查询条件：
~~~
<?php
$robot = Robots::findFirst(
array(
"type = 'virtual'",
"order" => "name DESC",
"limit" => 30
)
);
$robots = Robots::find(
array(
"conditions" => "type = ?1",
"bind" => array(1 => "virtual")
)
);
~~~
可用的查询选项如下：
如果你愿意，除了使用数组作为查询参数外，还可以通过一种面向对象的方式来创建查询：
~~~
<?php
$robots = Robots::query()
->where("type = :type:")
->andWhere("year < 2000")
->bind(array("type" => "mechanical"))
->order("name")
->execute();
~~~
静态方法 query() 返回一个对IDE自动完成友好的 [*Phalcon\Mvc\Model\Criteria*](#) 对象。
所有查询在内部都以 [*PHQL*](#) 查询的方式处理。PHQL是一个高层的、面向对象的类SQL语言。通过PHQL语言你可以使用更多的比如join其他模型、定义分组、添加聚集等特性。
最后，还有一个 findFirstBy<property-name>() 方法。这个方法扩展了前面提及的 “findFirst()” 方法。它允许您利用方法名中的属性名称，通过将要搜索的该字段的内容作为参数传给它，来快速从一个表执行检索操作。
还是用上面用过的 Robots 模型来举例说明：
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public $id;
public $name;
public $price;
}
~~~
我们这里有3个属性：$id, $name 和 $price。因此，我们以想要查询第一个名称为 ‘Terminator' 的记录为例，可以这样写：
~~~
<?php
$name = "Terminator";
$robot = Robots::findFirstByName($name);
if ($robot) {
$this->flash->success("The first robot with the name " . $name . " cost " . $robot->price ".");
} else {
$this->flash->error("There were no robots found in our table with the name " . $name ".");
}
~~~
请注意我们在方法调用中用的是 ‘Name'，并向它传递了变量 $name，$name 的值就是我们想要找的记录的名称。另外注意，当我们的查询找到了符合的记录后，这个记录的其他属性也都是可用的。
### 模型结果集（Model Resultsets）[](# "永久链接至标题")
findFirst() 方法直接返回一个被调用对象的实例（如果有结果返回的话），而 find() 方法返回一个 [*Phalcon\Mvc\Model\Resultset\Simple*](#) 对象。这个对象也封装进了所有结果集的功能，比如遍历、查找特定的记录、统计等等。
这些对象比一般数组功能更强大。最大的特点是 [*Phalcon\Mvc\Model\Resultset*](#) 每时每刻只有一个结果在内存中。这对操作大数据量时的内存管理相当有帮助。
~~~
<?php
// Get all robots
$robots = Robots::find();
// Traversing with a foreach
foreach ($robots as $robot) {
echo $robot->name, "\n";
}
// Traversing with a while
$robots->rewind();
while ($robots->valid()) {
$robot = $robots->current();
echo $robot->name, "\n";
$robots->next();
}
// Count the resultset
echo count($robots);
// Alternative way to count the resultset
echo $robots->count();
// Move the internal cursor to the third robot
$robots->seek(2);
$robot = $robots->current();
// Access a robot by its position in the resultset
$robot = $robots[5];
// Check if there is a record in certain position
if (isset($robots[3])) {
$robot = $robots[3];
}
// Get the first record in the resultset
$robot = $robots->getFirst();
// Get the last record
$robot = $robots->getLast();
~~~
Phalcon 的结果集模拟了可滚动的游标，你可以通过位置，或者内部指针去访问任何一条特定的记录。注意有一些数据库系统不支持滚动游标，这就使得查询会被重复执行，以便回放光标到最开始的位置，然后获得相应的记录。类似地，如果多次遍历结果集，那么必须执行相同的查询次数。
将大数据量的查询结果存储在内存会消耗很多资源，正因为如此，分成每32行一块从数据库中获得结果集，以减少重复执行查询请求的次数，在一些情况下也节省内存。
注意结果集可以序列化后保存在一个后端缓存里面。 [*Phalcon\Cache*](#) 可以用来实现这个。但是，序列化数据会导致 [*Phalcon\Mvc\Model*](#)将从数据库检索到的所有数据以一个数组的方式保存，因此在这样执行的地方会消耗更多的内存。
~~~
<?php
// Query all records from model parts
$parts = Parts::find();
// Store the resultset into a file
file_put_contents("cache.txt", serialize($parts));
// Get parts from file
$parts = unserialize(file_get_contents("cache.txt"));
// Traverse the parts
foreach ($parts as $part) {
echo $part->id;
}
~~~
### 过滤结果集（Filtering Resultsets）[](# "永久链接至标题")
过滤数据最有效的方法是设置一些查询条件，数据库会利用表的索引快速返回数据。Phalcon 额外的允许你通过任何数据库不支持的方式过滤数据。
~~~
<?php
$customers = Customers::find()->filter(
function ($customer) {
// Return only customers with a valid e-mail
if (filter_var($customer->email, FILTER_VALIDATE_EMAIL)) {
return $customer;
}
}
);
~~~
### 绑定参数（Binding Parameters）[](# "永久链接至标题")
在 [*Phalcon\Mvc\Model*](#) 中也支持绑定参数。即使使用绑定参数对性能有一点很小的影响，还是强烈建议您使用这种方法，以消除代码受SQL注入攻击的可能性。绑定参数支持字符串和整数占位符。实现方法如下：
~~~
<?php
// Query robots binding parameters with string placeholders
$conditions = "name = :name: AND type = :type:";
// Parameters whose keys are the same as placeholders
$parameters = array(
"name" => "Robotina",
"type" => "maid"
);
// Perform the query
$robots = Robots::find(
array(
$conditions,
"bind" => $parameters
)
);
// Query robots binding parameters with integer placeholders
$conditions = "name = ?1 AND type = ?2";
$parameters = array(1 => "Robotina", 2 => "maid");
$robots = Robots::find(
array(
$conditions,
"bind" => $parameters
)
);
// Query robots binding parameters with both string and integer placeholders
$conditions = "name = :name: AND type = ?1";
// Parameters whose keys are the same as placeholders
$parameters = array(
"name" => "Robotina",
1 => "maid"
);
// Perform the query
$robots = Robots::find(
array(
$conditions,
"bind" => $parameters
)
);
~~~
When using numeric placeholders, you will need to define them as integers i.e. 1 or 2. In this case “1” or “2” are considered stringsand not numbers, so the placeholder could not be successfully replaced.
Strings are automatically escaped using [PDO](http://www.php.net/manual/en/pdo.prepared-statements.php). This function takes into account the connection charset, so its recommended to definethe correct charset in the connection parameters or in the database configuration, as a wrong charset will produce undesired effectswhen storing or retrieving data.
Additionally you can set the parameter “bindTypes”, this allows defining how the parameters should be bound according to its data type:
~~~
<?php
use Phalcon\Db\Column;
// Bind parameters
$parameters = array(
"name" => "Robotina",
"year" => 2008
);
// Casting Types
$types = array(
"name" => Column::BIND_PARAM_STR,
"year" => Column::BIND_PARAM_INT
);
// Query robots binding parameters with string placeholders
$robots = Robots::find(
array(
"name = :name: AND year = :year:",
"bind" => $parameters,
"bindTypes" => $types
)
);
~~~
> Since the default bind-type is \Phalcon\Db\Column::BIND_PARAM_STR, there is no need to specify the“bindTypes” parameter if all of the columns are of that type.
If you bind arrays in bound parameters, keep in mind, that keys must be numbered from zero:
~~~
<?php
$array = ["a","b","c"]; // $array: [[0] => "a", [1] => "b", [2] => "c"]
unset($array[1]); // $array: [[0] => "a", [2] => "c"]
// Now we have to renumber the keys
$array = array_values($array); // $array: [[0] => "a", [1] => "c"]
$robots = Robots::find(
array(
'letter IN ({letter:array})',
'bind' => array(
'letter' => $array
)
)
);
~~~
Bound parameters are available for all query methods such as find() and findFirst() but also the calculationmethods like count(), sum(), average() etc.
If you're using “finders”, bound parameters are automatically used for you:
~~~
<?php
// Explicit query using bound parameters
$robots = Robots::find(
array(
"name = ?0",
"bind" => ["Ultron"],
)
);
// Implicit query using bound parameters
$robots = Robots::findByName("Ultron");
~~~
### 获取记录的初始化以及准备（Initializing/Preparing fetched records）[](# "永久链接至标题")
May be the case that after obtaining a record from the database is necessary to initialise the data beforebeing used by the rest of the application. You can implement the method ‘afterFetch' in a model, this eventwill be executed just after create the instance and assign the data to it:
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public $id;
public $name;
public $status;
public function beforeSave()
{
// Convert the array into a string
$this->status = join(',', $this->status);
}
public function afterFetch()
{
// Convert the string to an array
$this->status = explode(',', $this->status);
}
}
~~~
If you use getters/setters instead of/or together with public properties, you can initialize the field once it isaccessed:
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public $id;
public $name;
public $status;
public function getStatus()
{
return explode(',', $this->status);
}
}
~~~
### 模型关系（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 beunidirectional 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 referentialintegrity as well as easy and fast access of related records to a model. Through the implementation of relations,it is easy to access data in related models from each record in a uniform way.
有四种关系类型：1对1,1对多，多对1，多对多。关系可以是单向或者双向的，每个关系可以是简单的（一个1对1的模型）也可以是复杂的（1组模型）。
### 单向关系（Unidirectional relationships）[](# "永久链接至标题")
Unidirectional relations are those that are generated in relation to one another but not vice versa.
### 双向关系（Bidirectional relations）[](# "永久链接至标题")
The bidirectional relations build relationships in both models and each model defines the inverse relationship of the other.
### 定义关系（Defining relationships）[](# "永久链接至标题")
In Phalcon, relationships must be defined in the initialize() method of a model. The methods belongsTo(), hasOne(),hasMany() and hasManyToMany() define the relationship between one or more fields from the current model to fields inanother model. Each of these methods requires 3 parameters: local fields, referenced model, referenced fields.
| Method | Description |
|-----|-----|
| hasMany | Defines a 1-n relationship |
| hasOne | Defines a 1-1 relationship |
| belongsTo | Defines a n-1 relationship |
| hasManyToMany | Defines a n-n relationship |
The following schema shows 3 tables whose relations will serve us as an example regarding relationships:
~~~
CREATE TABLE `robots` (
`id` int(10) unsigned NOT NULL AUTO_INCREMENT,
`name` varchar(70) NOT NULL,
`type` varchar(32) NOT NULL,
`year` int(11) NOT NULL,
PRIMARY KEY (`id`)
);
CREATE TABLE `robots_parts` (
`id` int(10) unsigned NOT NULL AUTO_INCREMENT,
`robots_id` int(10) NOT NULL,
`parts_id` int(10) NOT NULL,
`created_at` DATE NOT NULL,
PRIMARY KEY (`id`),
KEY `robots_id` (`robots_id`),
KEY `parts_id` (`parts_id`)
);
CREATE TABLE `parts` (
`id` int(10) unsigned NOT NULL AUTO_INCREMENT,
`name` varchar(70) NOT NULL,
PRIMARY KEY (`id`)
);
~~~
- The model “Robots” has many “RobotsParts”.
- The model “Parts” has many “RobotsParts”.
- The model “RobotsParts” belongs to both “Robots” and “Parts” models as a many-to-one relation.
- The model “Robots” has a relation many-to-many to “Parts” through “RobotsParts”.
Check the EER diagram to understand better the relations:
The models with their relations could be implemented as follows:
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public $id;
public $name;
public function initialize()
{
$this->hasMany("id", "RobotsParts", "robots_id");
}
}
~~~
~~~
<?php
use Phalcon\Mvc\Model;
class Parts extends Model
{
public $id;
public $name;
public function initialize()
{
$this->hasMany("id", "RobotsParts", "parts_id");
}
}
~~~
~~~
<?php
use Phalcon\Mvc\Model;
class RobotsParts extends Model
{
public $id;
public $robots_id;
public $parts_id;
public function initialize()
{
$this->belongsTo("robots_id", "Robots", "id");
$this->belongsTo("parts_id", "Parts", "id");
}
}
~~~
The first parameter indicates the field of the local model used in the relationship; the second indicates the nameof the referenced model and the third the field name in the referenced model. You could also use arrays to define multiple fields in the relationship.
Many to many relationships require 3 models and define the attributes involved in the relationship:
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public $id;
public $name;
public function initialize()
{
$this->hasManyToMany(
"id",
"RobotsParts",
"robots_id", "parts_id",
"Parts",
"id"
);
}
}
~~~
### 使用关系（Taking advantage of relationships）[](# "永久链接至标题")
When explicitly defining the relationships between models, it is easy to find related records for a particular record.
~~~
<?php
$robot = Robots::findFirst(2);
foreach ($robot->robotsParts as $robotPart) {
echo $robotPart->parts->name, "\n";
}
~~~
Phalcon uses the magic methods __set/__get/__call to store or retrieve related data using relationships.
By accessing an attribute with the same name as the relationship will retrieve all its related record(s).
~~~
<?php
$robot = Robots::findFirst();
$robotsParts = $robot->robotsParts; // All the related records in RobotsParts
~~~
Also, you can use a magic getter:
~~~
<?php
$robot = Robots::findFirst();
$robotsParts = $robot->getRobotsParts(); // All the related records in RobotsParts
$robotsParts = $robot->getRobotsParts(array('limit' => 5)); // Passing parameters
~~~
If the called method has a “get” prefix [*Phalcon\Mvc\Model*](#) will return afindFirst()/find() result. The following example compares retrieving related results with using magic methodsand without:
~~~
<?php
$robot = Robots::findFirst(2);
// Robots model has a 1-n (hasMany)
// relationship to RobotsParts then
$robotsParts = $robot->robotsParts;
// Only parts that match conditions
$robotsParts = $robot->getRobotsParts("created_at = '2015-03-15'");
// Or using bound parameters
$robotsParts = $robot->getRobotsParts(
array(
"created_at = :date:",
"bind" => array(
"date" => "2015-03-15"
)
)
);
$robotPart = RobotsParts::findFirst(1);
// RobotsParts model has a n-1 (belongsTo)
// relationship to RobotsParts then
$robot = $robotPart->robots;
~~~
Getting related records manually:
~~~
<?php
$robot = Robots::findFirst(2);
// Robots model has a 1-n (hasMany)
// relationship to RobotsParts, then
$robotsParts = RobotsParts::find("robots_id = '" . $robot->id . "'");
// Only parts that match conditions
$robotsParts = RobotsParts::find(
"robots_id = '" . $robot->id . "' AND created_at = '2015-03-15'"
);
$robotPart = RobotsParts::findFirst(1);
// RobotsParts model has a n-1 (belongsTo)
// relationship to RobotsParts then
$robot = Robots::findFirst("id = '" . $robotPart->robots_id . "'");
~~~
The prefix “get” is used to find()/findFirst() related records. Depending on the type of relation it will use‘find' or ‘findFirst':
| Type | Description | Implicit Method |
|-----|-----|-----|
| Belongs-To | Returns a model instance of the related record directly | findFirst |
| Has-One | Returns a model instance of the related record directly | findFirst |
| Has-Many | Returns a collection of model instances of the referenced model | find |
| Has-Many-to-Many | Returns a collection of model instances of the referenced model, it implicitly does ‘inner joins' with the involved models | (complex query) |
You can also use “count” prefix to return an integer denoting the count of the related records:
~~~
<?php
$robot = Robots::findFirst(2);
echo "The robot has ", $robot->countRobotsParts(), " parts\n";
~~~
### 定义关系（Aliasing Relationships）[](# "永久链接至标题")
To explain better how aliases work, let's check the following example:
The “robots_similar” table has the function to define what robots are similar to others:
~~~
mysql> desc robots_similar;
+-------------------+------------------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra |
+-------------------+------------------+------+-----+---------+----------------+
| id | int(10) unsigned | NO | PRI | NULL | auto_increment |
| robots_id | int(10) unsigned | NO | MUL | NULL | |
| similar_robots_id | int(10) unsigned | NO | | NULL | |
+-------------------+------------------+------+-----+---------+----------------+
3 rows in set (0.00 sec)
~~~
Both “robots_id” and “similar_robots_id” have a relation to the model Robots:
A model that maps this table and its relationships is the following:
~~~
<?php
class RobotsSimilar extends Phalcon\Mvc\Model
{
public function initialize()
{
$this->belongsTo('robots_id', 'Robots', 'id');
$this->belongsTo('similar_robots_id', 'Robots', 'id');
}
}
~~~
Since both relations point to the same model (Robots), obtain the records related to the relationship could not be clear:
~~~
<?php
$robotsSimilar = RobotsSimilar::findFirst();
// Returns the related record based on the column (robots_id)
// Also as is a belongsTo it's only returning one record
// but the name 'getRobots' seems to imply that return more than one
$robot = $robotsSimilar->getRobots();
// but, how to get the related record based on the column (similar_robots_id)
// if both relationships have the same name?
~~~
The aliases allow us to rename both relationships to solve these problems:
~~~
<?php
use Phalcon\Mvc\Model;
class RobotsSimilar extends Model
{
public function initialize()
{
$this->belongsTo(
'robots_id',
'Robots',
'id',
array(
'alias' => 'Robot'
)
);
$this->belongsTo(
'similar_robots_id',
'Robots',
'id',
array(
'alias' => 'SimilarRobot'
)
);
}
}
~~~
With the aliasing we can get the related records easily:
~~~
<?php
$robotsSimilar = RobotsSimilar::findFirst();
// Returns the related record based on the column (robots_id)
$robot = $robotsSimilar->getRobot();
$robot = $robotsSimilar->robot;
// Returns the related record based on the column (similar_robots_id)
$similarRobot = $robotsSimilar->getSimilarRobot();
$similarRobot = $robotsSimilar->similarRobot;
~~~
### 魔术方法 Getters 对比显示方法（Magic Getters vs. Explicit methods）[](# "永久链接至标题")
Most IDEs and editors with auto-completion capabilities can not infer the correct types when using magic getters,instead of use the magic getters you can optionally define those methods explicitly with the correspondingdocblocks helping the IDE to produce a better auto-completion:
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public $id;
public $name;
public function initialize()
{
$this->hasMany("id", "RobotsParts", "robots_id");
}
/**
* Return the related "robots parts"
*
* @return \RobotsParts[]
*/
public function getRobotsParts($parameters = null)
{
return $this->getRelated('RobotsParts', $parameters);
}
}
~~~
### 虚拟外键（Virtual Foreign Keys）[](# "永久链接至标题")
By default, relationships do not act like database foreign keys, that is, if you try to insert/update a value without having a validvalue in the referenced model, Phalcon will not produce a validation message. You can modify this behavior by adding a fourth parameterwhen defining a relationship.
The RobotsPart model can be changed to demonstrate this feature:
~~~
<?php
use Phalcon\Mvc\Model;
class RobotsParts extends Model
{
public $id;
public $robots_id;
public $parts_id;
public function initialize()
{
$this->belongsTo(
"robots_id",
"Robots",
"id",
array(
"foreignKey" => true
)
);
$this->belongsTo(
"parts_id",
"Parts",
"id",
array(
"foreignKey" => array(
"message" => "The part_id does not exist on the Parts model"
)
)
);
}
}
~~~
If you alter a belongsTo() relationship to act as foreign key, it will validate that the values inserted/updated on those fields have avalid value on the referenced model. Similarly, if a hasMany()/hasOne() is altered it will validate that the records cannot be deletedif that record is used on a referenced model.
~~~
<?php
use Phalcon\Mvc\Model;
class Parts extends Model
{
public function initialize()
{
$this->hasMany(
"id",
"RobotsParts",
"parts_id",
array(
"foreignKey" => array(
"message" => "The part cannot be deleted because other robots are using it"
)
)
);
}
}
~~~
A virtual foreign key can be set up to allow null values as follows:
~~~
<?php
use Phalcon\Mvc\Model;
class RobotsParts extends Model
{
public $id;
public $robots_id;
public $parts_id;
public function initialize()
{
$this->belongsTo(
"parts_id",
"Parts",
"id",
array(
"foreignKey" => array(
"allowNulls" => true,
"message" => "The part_id does not exist on the Parts model"
)
)
);
}
}
~~~
### 级联与限制动作（Cascade/Restrict actions）[](# "永久链接至标题")
Relationships that act as virtual foreign keys by default restrict the creation/update/deletion of recordsto maintain the integrity of data:
~~~
<?php
namespace Store\Models;
use Phalcon\Mvc\Model;
use Phalcon\Mvc\Model\Relation;
class Robots extends Model
{
public $id;
public $name;
public function initialize()
{
$this->hasMany(
'id',
'Store\\Models\\Parts',
'robots_id',
array(
'foreignKey' => array(
'action' => Relation::ACTION_CASCADE
)
)
);
}
}
~~~
The above code set up to delete all the referenced records (parts) if the master record (robot) is deleted.
### 生成运算（Generating Calculations）[](# "永久链接至标题")
Calculations (or aggregations) are helpers for commonly used functions of database systems such as COUNT, SUM, MAX, MIN or AVG.[*Phalcon\Mvc\Model*](#) allows to use these functions directly from the exposed methods.
Count examples:
~~~
<?php
// How many employees are?
$rowcount = Employees::count();
// How many different areas are assigned to employees?
$rowcount = Employees::count(
array(
"distinct" => "area"
)
);
// How many employees are in the Testing area?
$rowcount = Employees::count(
"area = 'Testing'"
);
// Count employees grouping results by their area
$group = Employees::count(
array(
"group" => "area"
)
);
foreach ($group as $row) {
echo "There are ", $row->rowcount, " in ", $row->area;
}
// Count employees grouping by their area and ordering the result by count
$group = Employees::count(
array(
"group" => "area",
"order" => "rowcount"
)
);
// Avoid SQL injections using bound parameters
$group = Employees::count(
array(
"type > ?0",
"bind" => array($type)
)
);
~~~
Sum examples:
~~~
<?php
// How much are the salaries of all employees?
$total = Employees::sum(
array(
"column" => "salary"
)
);
// How much are the salaries of all employees in the Sales area?
$total = Employees::sum(
array(
"column" => "salary",
"conditions" => "area = 'Sales'"
)
);
// Generate a grouping of the salaries of each area
$group = Employees::sum(
array(
"column" => "salary",
"group" => "area"
)
);
foreach ($group as $row) {
echo "The sum of salaries of the ", $row->area, " is ", $row->sumatory;
}
// Generate a grouping of the salaries of each area ordering
// salaries from higher to lower
$group = Employees::sum(
array(
"column" => "salary",
"group" => "area",
"order" => "sumatory DESC"
)
);
// Avoid SQL injections using bound parameters
$group = Employees::sum(
array(
"conditions" => "area > ?0",
"bind" => array($area)
)
);
~~~
Average examples:
~~~
<?php
// What is the average salary for all employees?
$average = Employees::average(
array(
"column" => "salary"
)
);
// What is the average salary for the Sales's area employees?
$average = Employees::average(
array(
"column" => "salary",
"conditions" => "area = 'Sales'"
)
);
// Avoid SQL injections using bound parameters
$average = Employees::average(
array(
"column" => "age",
"conditions" => "area > ?0",
"bind" => array($area)
)
);
~~~
Max/Min examples:
~~~
<?php
// What is the oldest age of all employees?
$age = Employees::maximum(
array(
"column" => "age"
)
);
// What is the oldest of employees from the Sales area?
$age = Employees::maximum(
array(
"column" => "age",
"conditions" => "area = 'Sales'"
)
);
// What is the lowest salary of all employees?
$salary = Employees::minimum(
array(
"column" => "salary"
)
);
~~~
### Hydration Modes[](# "永久链接至标题")
As mentioned above, resultsets are collections of complete objects, this means that every returned result is an objectrepresenting a row in the database. These objects can be modified and saved again to persistence:
~~~
<?php
// Manipulating a resultset of complete objects
foreach (Robots::find() as $robot) {
$robot->year = 2000;
$robot->save();
}
~~~
Sometimes records are obtained only to be presented to a user in read-only mode, in these cases it may be usefulto change the way in which records are represented to facilitate their handling. The strategy used to represent objectsreturned in a resultset is called ‘hydration mode':
~~~
<?php
use Phalcon\Mvc\Model\Resultset;
$robots = Robots::find();
// Return every robot as an array
$robots->setHydrateMode(Resultset::HYDRATE_ARRAYS);
foreach ($robots as $robot) {
echo $robot['year'], PHP_EOL;
}
// Return every robot as a stdClass
$robots->setHydrateMode(Resultset::HYDRATE_OBJECTS);
foreach ($robots as $robot) {
echo $robot->year, PHP_EOL;
}
// Return every robot as a Robots instance
$robots->setHydrateMode(Resultset::HYDRATE_RECORDS);
foreach ($robots as $robot) {
echo $robot->year, PHP_EOL;
}
~~~
Hydration mode can also be passed as a parameter of ‘find':
~~~
<?php
use Phalcon\Mvc\Model\Resultset;
$robots = Robots::find(
array(
'hydration' => Resultset::HYDRATE_ARRAYS
)
);
foreach ($robots as $robot) {
echo $robot['year'], PHP_EOL;
}
~~~
### 创建与更新记录（Creating Updating/Records）[](# "永久链接至标题")
The method Phalcon\Mvc\Model::save() allows you to create/update records according to whether they already exist in the tableassociated with a model. The save method is called internally by the create and update methods of [*Phalcon\Mvc\Model*](#).For this to work as expected it is necessary to have properly defined a primary key in the entity to determine whether a recordshould be updated or created.
Also the method executes associated validators, virtual foreign keys and events that are defined in the model:
~~~
<?php
$robot = new Robots();
$robot->type = "mechanical";
$robot->name = "Astro Boy";
$robot->year = 1952;
if ($robot->save() == false) {
echo "Umh, We can't store robots right now: \n";
foreach ($robot->getMessages() as $message) {
echo $message, "\n";
}
} else {
echo "Great, a new robot was saved successfully!";
}
~~~
An array could be passed to “save” to avoid assign every column manually. Phalcon\Mvc\Model will check if there are setters implemented forthe columns passed in the array giving priority to them instead of assign directly the values of the attributes:
~~~
<?php
$robot = new Robots();
$robot->save(
array(
"type" => "mechanical",
"name" => "Astro Boy",
"year" => 1952
)
);
~~~
Values assigned directly or via the array of attributes are escaped/sanitized according to the related attribute data type. So you can passan insecure array without worrying about possible SQL injections:
~~~
<?php
$robot = new Robots();
$robot->save($_POST);
~~~
> Without precautions mass assignment could allow attackers to set any database column's value. Only use this featureif you want to permit a user to insert/update every column in the model, even if those fields are not in the submittedform.
You can set an additional parameter in ‘save' to set a whitelist of fields that only must taken into account when doingthe mass assignment:
~~~
<?php
$robot = new Robots();
$robot->save(
$_POST,
array(
'name',
'type'
)
);
~~~
### 创建与更新结果判断（Create/Update with Confidence）[](# "永久链接至标题")
When an application has a lot of competition, we could be expecting create a record but it is actually updated. Thiscould happen if we use Phalcon\Mvc\Model::save() to persist the records in the database. If we want to be absolutelysure that a record is created or updated, we can change the save() call with create() or update():
~~~
<?php
$robot = new Robots();
$robot->type = "mechanical";
$robot->name = "Astro Boy";
$robot->year = 1952;
// This record only must be created
if ($robot->create() == false) {
echo "Umh, We can't store robots right now: \n";
foreach ($robot->getMessages() as $message) {
echo $message, "\n";
}
} else {
echo "Great, a new robot was created successfully!";
}
~~~
These methods “create” and “update” also accept an array of values as parameter.
### 自动生成标识列（Auto-generated identity columns）[](# "永久链接至标题")
Some models may have identity columns. These columns usually are the primary key of the mapped table. [*Phalcon\Mvc\Model*](#)can recognize the identity column omitting it in the generated SQL INSERT, so the database system can generate an auto-generated value for it.Always after creating a record, the identity field will be registered with the value generated in the database system for it:
~~~
<?php
$robot->save();
echo "The generated id is: ", $robot->id;
~~~
[*Phalcon\Mvc\Model*](#) is able to recognize the identity column. Depending on the database system, those columns may beserial columns like in PostgreSQL or auto_increment columns in the case of MySQL.
PostgreSQL uses sequences to generate auto-numeric values, by default, Phalcon tries to obtain the generated value from the sequence “table_field_seq”,for example: robots_id_seq, if that sequence has a different name, the method “getSequenceName” needs to be implemented:
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public function getSequenceName()
{
return "robots_sequence_name";
}
}
~~~
### 存储关系记录（Storing related records）[](# "永久链接至标题")
Magic properties can be used to store a records and its related properties:
~~~
<?php
// Create an artist
$artist = new Artists();
$artist->name = 'Shinichi Osawa';
$artist->country = 'Japan';
// Create an album
$album = new Albums();
$album->name = 'The One';
$album->artist = $artist; // Assign the artist
$album->year = 2008;
// Save both records
$album->save();
~~~
Saving a record and its related records in a has-many relation:
~~~
<?php
// Get an existing artist
$artist = Artists::findFirst('name = "Shinichi Osawa"');
// Create an album
$album = new Albums();
$album->name = 'The One';
$album->artist = $artist;
$songs = array();
// Create a first song
$songs[0] = new Songs();
$songs[0]->name = 'Star Guitar';
$songs[0]->duration = '5:54';
// Create a second song
$songs[1] = new Songs();
$songs[1]->name = 'Last Days';
$songs[1]->duration = '4:29';
// Assign the songs array
$album->songs = $songs;
// Save the album + its songs
$album->save();
~~~
Saving the album and the artist at the same time implicitly makes use of a transaction so if anythinggoes wrong with saving the related records, the parent will not be saved either. Messages arepassed back to the user for information regarding any errors.
Note: Adding related entities by overloading the following methods is not possible:
>
> - Phalcon\Mvc\Model::beforeSave()
> - Phalcon\Mvc\Model::beforeCreate()
> - Phalcon\Mvc\Model::beforeUpdate()
You need to overload PhalconMvcModel::save() for this to work from within a model.
### 验证信息（Validation Messages）[](# "永久链接至标题")
[*Phalcon\Mvc\Model*](#) has a messaging subsystem that provides a flexible way to output or store thevalidation messages generated during the insert/update processes.
Each message consists of an instance of the class [*Phalcon\Mvc\Model\Message*](#). The set ofmessages generated can be retrieved with the method getMessages(). Each message provides extended information like the field name thatgenerated the message or the message type:
~~~
<?php
if ($robot->save() == false) {
foreach ($robot->getMessages() as $message) {
echo "Message: ", $message->getMessage();
echo "Field: ", $message->getField();
echo "Type: ", $message->getType();
}
}
~~~
[*Phalcon\Mvc\Model*](#) can generate the following types of validation messages:
| Type | Description |
|-----|-----|
| PresenceOf | Generated when a field with a non-null attribute on the database is trying to insert/update a null value |
| ConstraintViolation | Generated when a field part of a virtual foreign key is trying to insert/update a value that doesn't exist in the referenced model |
| InvalidValue | Generated when a validator failed because of an invalid value |
| InvalidCreateAttempt | Produced when a record is attempted to be created but it already exists |
| InvalidUpdateAttempt | Produced when a record is attempted to be updated but it doesn't exist |
The method getMessages() can be overridden in a model to replace/translate the default messages generated automatically by the ORM:
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public function getMessages()
{
$messages = array();
foreach (parent::getMessages() as $message) {
switch ($message->getType()) {
case 'InvalidCreateAttempt':
$messages[] = 'The record cannot be created because it already exists';
break;
case 'InvalidUpdateAttempt':
$messages[] = 'The record cannot be updated because it already exists';
break;
case 'PresenceOf':
$messages[] = 'The field ' . $message->getField() . ' is mandatory';
break;
}
}
return $messages;
}
}
~~~
### 事件与事件管理器（Events and Events Manager）[](# "永久链接至标题")
Models allow you to implement events that will be thrown when performing an insert/update/delete. They help define business rules for acertain model. The following are the events supported by [*Phalcon\Mvc\Model*](#) and their order of execution:
| Operation | Name | Can stop operation? | Explanation |
|-----|-----|-----|-----|
| Inserting/Updating | beforeValidation | YES | Is executed before the fields are validated for not nulls/empty strings or foreign keys |
| Inserting | beforeValidationOnCreate | YES | Is executed before the fields are validated for not nulls/empty strings or foreign keys when an insertion operation is being made |
| Updating | beforeValidationOnUpdate | YES | Is executed before the fields are validated for not nulls/empty strings or foreign keys when an updating operation is being made |
| Inserting/Updating | onValidationFails | YES (already stopped) | Is executed after an integrity validator fails |
| Inserting | afterValidationOnCreate | YES | Is executed after the fields are validated for not nulls/empty strings or foreign keys when an insertion operation is being made |
| Updating | afterValidationOnUpdate | YES | Is executed after the fields are validated for not nulls/empty strings or foreign keys when an updating operation is being made |
| Inserting/Updating | afterValidation | YES | Is executed after the fields are validated for not nulls/empty strings or foreign keys |
| Inserting/Updating | beforeSave | YES | Runs before the required operation over the database system |
| Updating | beforeUpdate | YES | Runs before the required operation over the database system only when an updating operation is being made |
| Inserting | beforeCreate | YES | Runs before the required operation over the database system only when an inserting operation is being made |
| Updating | afterUpdate | NO | Runs after the required operation over the database system only when an updating operation is being made |
| Inserting | afterCreate | NO | Runs after the required operation over the database system only when an inserting operation is being made |
| Inserting/Updating | afterSave | NO | Runs after the required operation over the database system |
### 模型中自定义事件（Implementing Events in the Model's class）[](# "永久链接至标题")
The easier way to make a model react to events is implement a method with the same name of the event in the model's class:
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public function beforeValidationOnCreate()
{
echo "This is executed before creating a Robot!";
}
}
~~~
Events can be useful to assign values before performing an operation, for example:
~~~
<?php
use Phalcon\Mvc\Model;
class Products extends Model
{
public function beforeCreate()
{
// Set the creation date
$this->created_at = date('Y-m-d H:i:s');
}
public function beforeUpdate()
{
// Set the modification date
$this->modified_in = date('Y-m-d H:i:s');
}
}
~~~
### 使用自定义事件管理器（Using a custom Events Manager）[](# "永久链接至标题")
Additionally, this component is integrated with [*Phalcon\Events\Manager*](#),this means we can create listeners that run when an event is triggered.
~~~
<?php
use Phalcon\Mvc\Model;
use Phalcon\Events\Manager as EventsManager;
class Robots extends Model
{
public function initialize()
{
$eventsManager = new EventsManager();
// Attach an anonymous function as a listener for "model" events
$eventsManager->attach('model', function ($event, $robot) {
if ($event->getType() == 'beforeSave') {
if ($robot->name == 'Scooby Doo') {
echo "Scooby Doo isn't a robot!";
return false;
}
}
return true;
});
// Attach the events manager to the event
$this->setEventsManager($eventsManager);
}
}
~~~
In the example given above, the Events Manager only acts as a bridge between an object and a listener (the anonymous function).Events will be fired to the listener when ‘robots' are saved:
~~~
<?php
$robot = new Robots();
$robot->name = 'Scooby Doo';
$robot->year = 1969;
$robot->save();
~~~
If we want all objects created in our application use the same EventsManager, then we need to assign it to the Models Manager:
~~~
<?php
// Registering the modelsManager service
$di->setShared('modelsManager', function () {
$eventsManager = new \Phalcon\Events\Manager();
// Attach an anonymous function as a listener for "model" events
$eventsManager->attach('model', function ($event, $model) {
// Catch events produced by the Robots model
if (get_class($model) == 'Robots') {
if ($event->getType() == 'beforeSave') {
if ($model->name == 'Scooby Doo') {
echo "Scooby Doo isn't a robot!";
return false;
}
}
}
return true;
});
// Setting a default EventsManager
$modelsManager = new ModelsManager();
$modelsManager->setEventsManager($eventsManager);
return $modelsManager;
});
~~~
If a listener returns false that will stop the operation that is executing currently.
### 实现业务逻辑（Implementing a Business Rule）[](# "永久链接至标题")
When an insert, update or delete is executed, the model verifies if there are any methods with the names ofthe events listed in the table above.
We recommend that validation methods are declared protected to prevent that business logic implementationfrom being exposed publicly.
The following example implements an event that validates the year cannot be smaller than 0 on update or insert:
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public function beforeSave()
{
if ($this->year < 0) {
echo "Year cannot be smaller than zero!";
return false;
}
}
}
~~~
Some events return false as an indication to stop the current operation. If an event doesn't return anything, [*Phalcon\Mvc\Model*](#)will assume a true value.
### 验证数据完整性（Validating Data Integrity）[](# "永久链接至标题")
[*Phalcon\Mvc\Model*](#) provides several events to validate data and implement business rules. The special “validation”event allows us to call built-in validators over the record. Phalcon exposes a few built-in validators that can be used at this stage of validation.
The following example shows how to use it:
~~~
<?php
use Phalcon\Mvc\Model;
use Phalcon\Mvc\Model\Validator\Uniqueness;
use Phalcon\Mvc\Model\Validator\InclusionIn;
class Robots extends Model
{
public function validation()
{
$this->validate(
new InclusionIn(
array(
"field" => "type",
"domain" => array("Mechanical", "Virtual")
)
)
);
$this->validate(
new Uniqueness(
array(
"field" => "name",
"message" => "The robot name must be unique"
)
)
);
return $this->validationHasFailed() != true;
}
}
~~~
The above example performs a validation using the built-in validator “InclusionIn”. It checks the value of the field “type” in a domain list. Ifthe value is not included in the method then the validator will fail and return false. The following built-in validators are available:
| Name | Explanation | Example |
|-----|-----|-----|
| PresenceOf | Validates that a field's value isn't null or empty string. This validator is automatically added based on the attributes marked as not null on the mapped table | [*Example*](#) |
| Email | Validates that field contains a valid email format | [*Example*](#) |
| ExclusionIn | Validates that a value is not within a list of possible values | [*Example*](#) |
| InclusionIn | Validates that a value is within a list of possible values | [*Example*](#) |
| Numericality | Validates that a field has a numeric format | [*Example*](#) |
| Regex | Validates that the value of a field matches a regular expression | [*Example*](#) |
| Uniqueness | Validates that a field or a combination of a set of fields are not present more than once in the existing records of the related table | [*Example*](#) |
| StringLength | Validates the length of a string | [*Example*](#) |
| Url | Validates that a value has a valid URL format | [*Example*](#) |
In addition to the built-in validators, you can create your own validators:
~~~
<?php
use Phalcon\Mvc\Model\Validator;
use Phalcon\Mvc\Model\ValidatorInterface;
use Phalcon\Mvc\EntityInterface;
class MaxMinValidator extends Validator implements ValidatorInterface
{
public function validate(EntityInterface $model)
{
$field = $this->getOption('field');
$min = $this->getOption('min');
$max = $this->getOption('max');
$value = $model->$field;
if ($min <= $value && $value <= $max) {
$this->appendMessage(
"The field doesn't have the right range of values",
$field,
"MaxMinValidator"
);
return false;
}
return true;
}
}
~~~
> *NOTE* Up to version 2.0.4 $model must be \Phalcon\Mvc\ModelInterfaceinstance (public function validate(\Phalcon\Mvc\ModelInterface $model)).
Adding the validator to a model:
~~~
<?php
use Phalcon\Mvc\Model;
class Customers extends Model
{
public function validation()
{
$this->validate(
new MaxMinValidator(
array(
"field" => "price",
"min" => 10,
"max" => 100
)
)
);
if ($this->validationHasFailed() == true) {
return false;
}
}
}
~~~
The idea of creating validators is make them reusable between several models. A validator can also be as simple as:
~~~
<?php
use Phalcon\Mvc\Model;
use Phalcon\Mvc\Model\Message;
class Robots extends Model
{
public function validation()
{
if ($this->type == "Old") {
$message = new Message(
"Sorry, old robots are not allowed anymore",
"type",
"MyType"
);
$this->appendMessage($message);
return false;
}
return true;
}
}
~~~
### Avoiding SQL injections[](# "永久链接至标题")
Every value assigned to a model attribute is escaped depending of its data type. A developer doesn't need to escape manuallyeach value before storing it on the database. Phalcon uses internally the [bound parameters](http://php.net/manual/en/pdostatement.bindparam.php)capability provided by PDO to automatically escape every value to be stored in the database.
~~~
mysql> desc products;
+------------------+------------------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra |
+------------------+------------------+------+-----+---------+----------------+
| id | int(10) unsigned | NO | PRI | NULL | auto_increment |
| product_types_id | int(10) unsigned | NO | MUL | NULL | |
| name | varchar(70) | NO | | NULL | |
| price | decimal(16,2) | NO | | NULL | |
| active | char(1) | YES | | NULL | |
+------------------+------------------+------+-----+---------+----------------+
5 rows in set (0.00 sec)
~~~
If we use just PDO to store a record in a secure way, we need to write the following code:
~~~
<?php
$name = 'Artichoke';
$price = 10.5;
$active = 'Y';
$productTypesId = 1;
$sql = 'INSERT INTO products VALUES (null, :productTypesId, :name, :price, :active)';
$sth = $dbh->prepare($sql);
$sth->bindParam(':productTypesId', $productTypesId, PDO::PARAM_INT);
$sth->bindParam(':name', $name, PDO::PARAM_STR, 70);
$sth->bindParam(':price', doubleval($price));
$sth->bindParam(':active', $active, PDO::PARAM_STR, 1);
$sth->execute();
~~~
The good news is that Phalcon do this for you automatically:
~~~
<?php
$product = new Products();
$product->product_types_id = 1;
$product->name = 'Artichoke';
$product->price = 10.5;
$product->active = 'Y';
$product->create();
~~~
### 忽略指定列的数据（Skipping Columns）[](# "永久链接至标题")
To tell Phalcon\Mvc\Model that always omits some fields in the creation and/or update of records in orderto delegate the database system the assignation of the values by a trigger or a default:
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public function initialize()
{
// Skips fields/columns on both INSERT/UPDATE operations
$this->skipAttributes(
array(
'year',
'price'
)
);
// Skips only when inserting
$this->skipAttributesOnCreate(
array(
'created_at'
)
);
// Skips only when updating
$this->skipAttributesOnUpdate(
array(
'modified_in'
)
);
}
}
~~~
This will ignore globally these fields on each INSERT/UPDATE operation on the whole application.If you want to ignore different attributes on different INSERT/UPDATE operations, you can specify the second parameter (boolean) - truefor replacement. Forcing a default value can be done in the following way:
~~~
<?php
use Phalcon\Db\RawValue;
$robot = new Robots();
$robot->name = 'Bender';
$robot->year = 1999;
$robot->created_at = new RawValue('default');
$robot->create();
~~~
A callback also can be used to create a conditional assignment of automatic default values:
~~~
<?php
use Phalcon\Mvc\Model;
use Phalcon\Db\RawValue;
class Robots extends Model
{
public function beforeCreate()
{
if ($this->price > 10000) {
$this->type = new RawValue('default');
}
}
}
~~~
> Never use a \Phalcon\Db\RawValue to assign external data (such as user input)or variable data. The value of these fields is ignored when binding parameters to the query.So it could be used to attack the application injecting SQL.
### 动态更新（Dynamic Update）[](# "永久链接至标题")
SQL UPDATE statements are by default created with every column defined in the model (full all-field SQL update).You can change specific models to make dynamic updates, in this case, just the fields that had changedare used to create the final SQL statement.
In some cases this could improve the performance by reducing the traffic between the application and the database server,this specially helps when the table has blob/text fields:
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public function initialize()
{
$this->useDynamicUpdate(true);
}
}
~~~
### 删除记录（Deleting Records）[](# "永久链接至标题")
The method Phalcon\Mvc\Model::delete() allows to delete a record. You can use it as follows:
~~~
<?php
$robot = Robots::findFirst(11);
if ($robot != false) {
if ($robot->delete() == false) {
echo "Sorry, we can't delete the robot right now: \n";
foreach ($robot->getMessages() as $message) {
echo $message, "\n";
}
} else {
echo "The robot was deleted successfully!";
}
}
~~~
You can also delete many records by traversing a resultset with a foreach:
~~~
<?php
foreach (Robots::find("type='mechanical'") as $robot) {
if ($robot->delete() == false) {
echo "Sorry, we can't delete the robot right now: \n";
foreach ($robot->getMessages() as $message) {
echo $message, "\n";
}
} else {
echo "The robot was deleted successfully!";
}
}
~~~
The following events are available to define custom business rules that can be executed when a delete operation isperformed:
| Operation | Name | Can stop operation? | Explanation |
|-----|-----|-----|-----|
| Deleting | beforeDelete | YES | Runs before the delete operation is made |
| Deleting | afterDelete | NO | Runs after the delete operation was made |
With the above events can also define business rules in the models:
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public function beforeDelete()
{
if ($this->status == 'A') {
echo "The robot is active, it can't be deleted";
return false;
}
return true;
}
}
~~~
### 验证失败事件（Validation Failed Events）[](# "永久链接至标题")
Another type of events are available when the data validation process finds any inconsistency:
| Operation | Name | Explanation |
|-----|-----|-----|
| Insert or Update | notSaved | Triggered when the INSERT or UPDATE operation fails for any reason |
| Insert, Delete or Update | onValidationFails | Triggered when any data manipulation operation fails |
### 行为（Behaviors）[](# "永久链接至标题")
Behaviors are shared conducts that several models may adopt in order to re-use code, the ORM provides an API to implementbehaviors in your models. Also, you can use the events and callbacks as seen before as an alternative to implement Behaviors with more freedom.
A behavior must be added in the model initializer, a model can have zero or more behaviors:
~~~
<?php
use Phalcon\Mvc\Model;
use Phalcon\Mvc\Model\Behavior\Timestampable;
class Users extends Model
{
public $id;
public $name;
public $created_at;
public function initialize()
{
$this->addBehavior(
new Timestampable(
array(
'beforeCreate' => array(
'field' => 'created_at',
'format' => 'Y-m-d'
)
)
)
);
}
}
~~~
The following built-in behaviors are provided by the framework:
| Name | Description |
|-----|-----|
| Timestampable | Allows to automatically update a model's attribute saving the datetime when a record is created or updated |
| SoftDelete | Instead of permanently delete a record it marks the record as deleted changing the value of a flag column |
### 生成时间戳（Timestampable）[](# "永久链接至标题")
This behavior receives an array of options, the first level key must be an event name indicating when the column must be assigned:
~~~
<?php
use Phalcon\Mvc\Model\Behavior\Timestampable;
public function initialize()
{
$this->addBehavior(
new Timestampable(
array(
'beforeCreate' => array(
'field' => 'created_at',
'format' => 'Y-m-d'
)
)
)
);
}
~~~
Each event can have its own options, ‘field' is the name of the column that must be updated, if ‘format' is a string it will be usedas format of the PHP's function [date](http://php.net/manual/en/function.date.php), format can also be an anonymous function providing you the free to generate any kind timestamp:
~~~
<?php
use Phalcon\Mvc\Model\Behavior\Timestampable;
public function initialize()
{
$this->addBehavior(
new Timestampable(
array(
'beforeCreate' => array(
'field' => 'created_at',
'format' => function () {
$datetime = new Datetime(new DateTimeZone('Europe/Stockholm'));
return $datetime->format('Y-m-d H:i:sP');
}
)
)
)
);
}
~~~
If the option ‘format' is omitted a timestamp using the PHP's function [time](http://php.net/manual/en/function.time.php), will be used.
### 软删除（SoftDelete）[](# "永久链接至标题")
This behavior can be used in the following way:
~~~
<?php
use Phalcon\Mvc\Model;
use Phalcon\Mvc\Model\Behavior\SoftDelete;
class Users extends Model
{
const DELETED = 'D';
const NOT_DELETED = 'N';
public $id;
public $name;
public $status;
public function initialize()
{
$this->addBehavior(
new SoftDelete(
array(
'field' => 'status',
'value' => Users::DELETED
)
)
);
}
}
~~~
This behavior accepts two options: ‘field' and ‘value', ‘field' determines what field must be updated and ‘value' the value to be deleted.Let's pretend the table ‘users' has the following data:
~~~
mysql> select * from users;
+----+---------+--------+
| id | name | status |
+----+---------+--------+
| 1 | Lana | N |
| 2 | Brandon | N |
+----+---------+--------+
2 rows in set (0.00 sec)
~~~
If we delete any of the two records the status will be updated instead of delete the record:
~~~
<?php
Users::findFirst(2)->delete();
~~~
The operation will result in the following data in the table:
~~~
mysql> select * from users;
+----+---------+--------+
| id | name | status |
+----+---------+--------+
| 1 | Lana | N |
| 2 | Brandon | D |
+----+---------+--------+
2 rows in set (0.01 sec)
~~~
Note that you need to specify the deleted condition in your queries to effectively ignore them as deleted records, this behavior doesn't support that.
### 创建行为（Creating your own behaviors）[](# "永久链接至标题")
The ORM provides an API to create your own behaviors. A behavior must be a class implementing the [*Phalcon\Mvc\Model\BehaviorInterface*](#)Also, Phalcon\Mvc\Model\Behavior provides most of the methods needed to ease the implementation of behaviors.
The following behavior is an example, it implements the Blameable behavior which helps identify the userthat is performed operations over a model:
~~~
<?php
use Phalcon\Mvc\Model\Behavior;
use Phalcon\Mvc\Model\BehaviorInterface;
class Blameable extends Behavior implements BehaviorInterface
{
public function notify($eventType, $model)
{
switch ($eventType) {
case 'afterCreate':
case 'afterDelete':
case 'afterUpdate':
$userName = // ... get the current user from session
// Store in a log the username - event type and primary key
file_put_contents(
'logs/blamable-log.txt',
$userName . ' ' . $eventType . ' ' . $model->id
);
break;
default:
/* ignore the rest of events */
}
}
}
~~~
The former is a very simple behavior, but it illustrates how to create a behavior, now let's add this behavior to a model:
~~~
<?php
use Phalcon\Mvc\Model;
class Profiles extends Model
{
public function initialize()
{
$this->addBehavior(new Blameable());
}
}
~~~
A behavior is also capable of intercepting missing methods on your models:
~~~
<?php
use Phalcon\Tag;
use Phalcon\Mvc\Model\Behavior;
use Phalcon\Mvc\Model\BehaviorInterface;
class Sluggable extends Behavior implements BehaviorInterface
{
public function missingMethod($model, $method, $arguments = array())
{
// If the method is 'getSlug' convert the title
if ($method == 'getSlug') {
return Tag::friendlyTitle($model->title);
}
}
}
~~~
Call that method on a model that implements Sluggable returns a SEO friendly title:
~~~
<?php
$title = $post->getSlug();
~~~
### 使用 Traits 实现行为(Using Traits as behaviors)[](# "永久链接至标题")
Starting from PHP 5.4 you can use [Traits](http://php.net/manual/en/language.oop5.traits.php) to re-use code in your classes, this is another way to implementcustom behaviors. The following trait implements a simple version of the Timestampable behavior:
~~~
<?php
trait MyTimestampable
{
public function beforeCreate()
{
$this->created_at = date('r');
}
public function beforeUpdate()
{
$this->updated_at = date('r');
}
}
~~~
Then you can use it in your model as follows:
~~~
<?php
use Phalcon\Mvc\Model;
class Products extends Model
{
use MyTimestampable;
}
~~~
### 独立的列映射（Independent Column Mapping）[](# "永久链接至标题")
The ORM supports an independent column map, which allows the developer to use different column names in the model to the ones inthe table. Phalcon will recognize the new column names and will rename them accordingly to match the respective columns in the database.This is a great feature when one needs to rename fields in the database without having to worry about all the queriesin the code. A change in the column map in the model will take care of the rest. For example:
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public $code;
public $theName;
public $theType;
public $theYear;
public function columnMap()
{
// Keys are the real names in the table and
// the values their names in the application
return array(
'id' => 'code',
'the_name' => 'theName',
'the_type' => 'theType',
'the_year' => 'theYear'
);
}
}
~~~
Then you can use the new names naturally in your code:
~~~
<?php
// Find a robot by its name
$robot = Robots::findFirst("theName = 'Voltron'");
echo $robot->theName, "\n";
// Get robots ordered by type
$robot = Robots::find(
array(
'order' => 'theType DESC'
)
);
foreach ($robots as $robot) {
echo 'Code: ', $robot->code, "\n";
}
// Create a robot
$robot = new Robots();
$robot->code = '10101';
$robot->theName = 'Bender';
$robot->theType = 'Industrial';
$robot->theYear = 2999;
$robot->save();
~~~
Take into consideration the following the next when renaming your columns:
- References to attributes in relationships/validators must use the new names
- Refer the real column names will result in an exception by the ORM
The independent column map allow you to:
- Write applications using your own conventions
- Eliminate vendor prefixes/suffixes in your code
- Change column names without change your application code
### 在结果集中操作（Operations over Resultsets）[](# "永久链接至标题")
If a resultset is composed of complete objects, the resultset is in the ability to perform operations on the records obtained in a simple manner:
### 更新关联表记录（Updating related records）[](# "永久链接至标题")
Instead of doing this:
~~~
<?php
foreach ($robots->getParts() as $part) {
$part->stock = 100;
$part->updated_at = time();
if ($part->update() == false) {
foreach ($part->getMessages() as $message) {
echo $message;
}
break;
}
}
~~~
you can do this:
~~~
<?php
$robots->getParts()->update(
array(
'stock' => 100,
'updated_at' => time()
)
);
~~~
‘update' also accepts an anonymous function to filter what records must be updated:
~~~
<?php
$data = array(
'stock' => 100,
'updated_at' => time()
);
// Update all the parts except those whose type is basic
$robots->getParts()->update($data, function ($part) {
if ($part->type == Part::TYPE_BASIC) {
return false;
}
return true;
});
~~~
### 删除关联表记录（Deleting related records）[](# "永久链接至标题")
Instead of doing this:
~~~
<?php
foreach ($robots->getParts() as $part) {
if ($part->delete() == false) {
foreach ($part->getMessages() as $message) {
echo $message;
}
break;
}
}
~~~
you can do this:
~~~
<?php
$robots->getParts()->delete();
~~~
‘delete' also accepts an anonymous function to filter what records must be deleted:
~~~
<?php
// Delete only whose stock is greater or equal than zero
$robots->getParts()->delete(function ($part) {
if ($part->stock < 0) {
return false;
}
return true;
});
~~~
### 记录快照（Record Snapshots）[](# "永久链接至标题")
Specific models could be set to maintain a record snapshot when they're queried. You can use this feature to implement auditing or just to know whatfields are changed according to the data queried from the persistence:
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public function initialize()
{
$this->keepSnapshots(true);
}
}
~~~
When activating this feature the application consumes a bit more of memory to keep track of the original values obtained from the persistence.In models that have this feature activated you can check what fields changed:
~~~
<?php
// Get a record from the database
$robot = Robots::findFirst();
// Change a column
$robot->name = 'Other name';
var_dump($robot->getChangedFields()); // ['name']
var_dump($robot->hasChanged('name')); // true
var_dump($robot->hasChanged('type')); // false
~~~
### 设置模式（Pointing to a different schema）[](# "永久链接至标题")
If a model is mapped to a table that is in a different schemas/databases than the default. You can use the getSchema method to define that:
如果一个模型映射到一个在非默认的schemas/数据库中的表，你可以通过 getSchema 方法去定义它：
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public function getSchema()
{
return "toys";
}
}
~~~
### 设置多个数据库（Setting multiple databases）[](# "永久链接至标题")
In Phalcon, all models can belong to the same database connection or have an individual one. Actually, when[*Phalcon\Mvc\Model*](#) needs to connect to the database it requests the “db” servicein the application's services container. You can overwrite this service setting it in the initialize method:
在Phalcon中，所有模型可以属于同一个数据库连接，也可以分属独立的数据库连接。实际上，当 [*Phalcon\Mvc\Model*](#)需要连接数据库的时候，它在应用服务容器内请求”db”这个服务。 可以通过在 initialize 方法内重写这个服务的设置。
~~~
<?php
use Phalcon\Db\Adapter\Pdo\Mysql as MysqlPdo;
use Phalcon\Db\Adapter\Pdo\PostgreSQL as PostgreSQLPdo;
// This service returns a MySQL database
$di->set('dbMysql', function () {
return new MysqlPdo(
array(
"host" => "localhost",
"username" => "root",
"password" => "secret",
"dbname" => "invo"
)
);
});
// This service returns a PostgreSQL database
$di->set('dbPostgres', function () {
return new PostgreSQLPdo(
array(
"host" => "localhost",
"username" => "postgres",
"password" => "",
"dbname" => "invo"
)
);
});
~~~
Then, in the Initialize method, we define the connection service for the model:
然后，在 Initialize 方法内，我们为这个模型定义数据库连接。
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public function initialize()
{
$this->setConnectionService('dbPostgres');
}
}
~~~
But Phalcon offers you more flexibility, you can define the connection that must be used to ‘read' and for ‘write'. This is specially usefulto balance the load to your databases implementing a master-slave architecture:
另外Phalcon还提供了更多的灵活性，你可分别定义用来读取和写入的数据库连接。这对实现主从架构的数据库负载均衡非常有用。（译者注：EvaEngine项目为使用Phalcon提供了更多的灵活性，推荐了解和使用）
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public function initialize()
{
$this->setReadConnectionService('dbSlave');
$this->setWriteConnectionService('dbMaster');
}
}
~~~
The ORM also provides Horizontal Sharding facilities, by allowing you to implement a ‘shard' selectionaccording to the current query conditions:
另外ORM还可以通过根据当前查询条件来实现一个 ‘shard' 选择器，来实现水平切分的功能。
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
/**
* Dynamically selects a shard
*
* @param array $intermediate
* @param array $bindParams
* @param array $bindTypes
*/
public function selectReadConnection($intermediate, $bindParams, $bindTypes)
{
// Check if there is a 'where' clause in the select
if (isset($intermediate['where'])) {
$conditions = $intermediate['where'];
// Choose the possible shard according to the conditions
if ($conditions['left']['name'] == 'id') {
$id = $conditions['right']['value'];
if ($id > 0 && $id < 10000) {
return $this->getDI()->get('dbShard1');
}
if ($id > 10000) {
return $this->getDI()->get('dbShard2');
}
}
}
// Use a default shard
return $this->getDI()->get('dbShard0');
}
}
~~~
The method ‘selectReadConnection' is called to choose the right connection, this method intercepts any newquery executed:
‘selectReadConnection' 方法用来选择正确的数据库连接，这个方法拦截任何新的查询操作：
~~~
<?php
$robot = Robots::findFirst('id = 101');
~~~
### 记录底层 SQL 语句（Logging Low-Level SQL Statements）[](# "永久链接至标题")
When using high-level abstraction components such as [*Phalcon\Mvc\Model*](#) to access a database, it isdifficult to understand which statements are finally sent to the database system. [*Phalcon\Mvc\Model*](#)is supported internally by [*Phalcon\Db*](#). [*Phalcon\Logger*](#) interactswith [*Phalcon\Db*](#), providing logging capabilities on the database abstraction layer, thus allowing us to log SQLstatements as they happen.
~~~
<?php
use Phalcon\Logger;
use Phalcon\Events\Manager;
use Phalcon\Logger\Adapter\File as FileLogger;
use Phalcon\Db\Adapter\Pdo\Mysql as Connection;
$di->set('db', function () {
$eventsManager = new EventsManager();
$logger = new FileLogger("app/logs/debug.log");
// Listen all the database events
$eventsManager->attach('db', function ($event, $connection) use ($logger) {
if ($event->getType() == 'beforeQuery') {
$logger->log($connection->getSQLStatement(), Logger::INFO);
}
});
$connection = new Connection(
array(
"host" => "localhost",
"username" => "root",
"password" => "secret",
"dbname" => "invo"
)
);
// Assign the eventsManager to the db adapter instance
$connection->setEventsManager($eventsManager);
return $connection;
});
~~~
As models access the default database connection, all SQL statements that are sent to the database system will be logged in the file:
~~~
<?php
$robot = new Robots();
$robot->name = "Robby the Robot";
$robot->created_at = "1956-07-21";
if ($robot->save() == false) {
echo "Cannot save robot";
}
~~~
As above, the file *app/logs/db.log* will contain something like this:
~~~
[Mon, 30 Apr 12 13:47:18 -0500][DEBUG][Resource Id #77] INSERT INTO robots
(name, created_at) VALUES ('Robby the Robot', '1956-07-21')
~~~
### 分析 SQL 语句（Profiling SQL Statements）[](# "永久链接至标题")
Thanks to [*Phalcon\Db*](#), the underlying component of [*Phalcon\Mvc\Model*](#),it's possible to profile the SQL statements generated by the ORM in order to analyze the performance of database operations. Withthis you can diagnose performance problems and to discover bottlenecks.
~~~
<?php
use Phalcon\Db\Profiler as ProfilerDb;
use Phalcon\Events\Manager as EventsManager;
use Phalcon\Db\Adapter\Pdo\Mysql as MysqlPdo;
$di->set('profiler', function () {
return new ProfilerDb();
}, true);
$di->set('db', function () use ($di) {
$eventsManager = new EventsManager();
// Get a shared instance of the DbProfiler
$profiler = $di->getProfiler();
// Listen all the database events
$eventsManager->attach('db', function ($event, $connection) use ($profiler) {
if ($event->getType() == 'beforeQuery') {
$profiler->startProfile($connection->getSQLStatement());
}
if ($event->getType() == 'afterQuery') {
$profiler->stopProfile();
}
});
$connection = new MysqlPdo(
array(
"host" => "localhost",
"username" => "root",
"password" => "secret",
"dbname" => "invo"
)
);
// Assign the eventsManager to the db adapter instance
$connection->setEventsManager($eventsManager);
return $connection;
});
~~~
Profiling some queries:
~~~
<?php
// Send some SQL statements to the database
Robots::find();
Robots::find(
array(
"order" => "name"
)
);
Robots::find(
array(
"limit" => 30
)
);
// Get the generated profiles from the profiler
$profiles = $di->get('profiler')->getProfiles();
foreach ($profiles as $profile) {
echo "SQL Statement: ", $profile->getSQLStatement(), "\n";
echo "Start Time: ", $profile->getInitialTime(), "\n";
echo "Final Time: ", $profile->getFinalTime(), "\n";
echo "Total Elapsed Time: ", $profile->getTotalElapsedSeconds(), "\n";
}
~~~
Each generated profile contains the duration in milliseconds that each instruction takes to complete as well as the generated SQL statement.
### 注入服务到模型（Injecting services into Models）[](# "永久链接至标题")
You may be required to access the application services within a model, the following example explains how to do that:
你可能需要在模型中用到应用中注入的服务，下面的例子会教你如何去做：
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
public function notSaved()
{
// Obtain the flash service from the DI container
$flash = $this->getDI()->getFlash();
// Show validation messages
foreach ($this->getMessages() as $message) {
$flash->error($message);
}
}
}
~~~
The “notSaved” event is triggered every time that a “create” or “update” action fails. So we're flashing the validation messagesobtaining the “flash” service from the DI container. By doing this, we don't have to print messages after each save.
每当 “create” 或者 “update” 操作失败时会触发 “notSave” 事件。所以我们从DI中获取 “flash” 服务并推送确认消息。这样的话，我们不需要每次在save之后去打印信息。
### 禁用或启用特性（Disabling/Enabling Features）[](# "永久链接至标题")
In the ORM we have implemented a mechanism that allow you to enable/disable specific features or options globally on the fly.According to how you use the ORM you can disable that you aren't using. These options can also be temporarily disabled if required:
~~~
<?php
use Phalcon\Mvc\Model;
Model::setup(
array(
'events' => false,
'columnRenaming' => false
)
);
~~~
The available options are:
| Option | Description | Default |
|-----|-----|-----|
| events | Enables/Disables callbacks, hooks and event notifications from all the models | true |
| columnRenaming | Enables/Disables the column renaming | true |
| notNullValidations | The ORM automatically validate the not null columns present in the mapped table | true |
| virtualForeignKeys | Enables/Disables the virtual foreign keys | true |
| phqlLiterals | Enables/Disables literals in the PHQL parser | true |
| lateStateBinding | Enables/Disables late state binding of the method MvcModel::cloneResultMap | false |
### 独立的组件（Stand-Alone component）[](# "永久链接至标题")
Using [*Phalcon\Mvc\Model*]() in a stand-alone mode can be demonstrated below:
~~~
<?php
use Phalcon\DI;
use Phalcon\Mvc\Model;
use Phalcon\Mvc\Model\Manager as ModelsManager;
use Phalcon\Db\Adapter\Pdo\Sqlite as Connection;
use Phalcon\Mvc\Model\Metadata\Memory as MetaData;
$di = new DI();
// Setup a connection
$di->set(
'db',
new Connection(
array(
"dbname" => "sample.db"
)
)
);
// Set a models manager
$di->set('modelsManager', new ModelsManager());
// Use the memory meta-data adapter or other
$di->set('modelsMetadata', new MetaData());
// Create a model
class Robots extends Model
{
}
// Use the model
echo Robots::count();
~~~
|
- [索引](# "总目录")
- [下一页](# "模型元数据（Models Meta-Data）") |
- [上一页](# "使用控制器（Using Controllers）") |
- Phalcon 2.0.6文档
- API参考
- API列表
- Abstract class Phalcon\Acl
- Abstract class Phalcon\Acl\Adapter
- Class Phalcon\Acl\Adapter\Memory
- Interface Phalcon\Acl\AdapterInterface
- Class Phalcon\Acl\Exception
- Class Phalcon\Acl\Resource
- Interface Phalcon\Acl\ResourceInterface
- Class Phalcon\Acl\Role
- Interface Phalcon\Acl\RoleInterface
- Class Phalcon\Annotations\Annotation
- Abstract class Phalcon\Annotations\Adapter
- Class Phalcon\Annotations\Adapter\Apc
- Class Phalcon\Annotations\Adapter\Files
- Class Phalcon\Annotations\Adapter\Memory
- Class Phalcon\Annotations\Adapter\Xcache
- Interface Phalcon\Annotations\AdapterInterface
- Class Phalcon\Annotations\Collection
- Class Phalcon\Annotations\Exception
- Class Phalcon\Annotations\Reader
- Interface Phalcon\Annotations\ReaderInterface
- Class Phalcon\Annotations\Reflection
- Class Phalcon\Assets\Collection
- Class Phalcon\Assets\Exception
- Interface Phalcon\Assets\FilterInterface
- Class Phalcon\Assets\Filters\Cssmin
- Class Phalcon\Assets\Filters\Jsmin
- Class Phalcon\Assets\Filters\None
- Class Phalcon\Assets\Inline
- Class Phalcon\Assets\Inline\Css
- Class Phalcon\Assets\Inline\Js
- Class Phalcon\Assets\Manager
- Class Phalcon\Assets\Resource
- Class Phalcon\Assets\Resource\Css
- Class Phalcon\Assets\Resource\Js
- Abstract class Phalcon\Cache\Backend
- Class Phalcon\Cache\Backend\Apc
- Class Phalcon\Cache\Backend\File
- Class Phalcon\Cache\Backend\Libmemcached
- Class Phalcon\Cache\Backend\Memcache
- Class Phalcon\Cache\Backend\Memory
- Class Phalcon\Cache\Backend\Mongo
- Class Phalcon\Cache\Backend\Redis
- Class Phalcon\Cache\Backend\Xcache
- Interface Phalcon\Cache\BackendInterface
- Class Phalcon\Cache\Exception
- Class Phalcon\Cache\Frontend\Base64
- Class Phalcon\Cache\Frontend\Data
- Class Phalcon\Cache\Frontend\Igbinary
- Class Phalcon\Cache\Frontend\Json
- Class Phalcon\Cache\Frontend\None
- Class Phalcon\Cache\Frontend\Output
- Interface Phalcon\Cache\FrontendInterface
- Class Phalcon\Cache\Multiple
- Class Phalcon\Cli\Router\Route
- Class Phalcon\Config
- Class Phalcon\Config\Adapter\Ini
- Class Phalcon\Config\Adapter\Json
- Class Phalcon\Config\Adapter\Php
- Class Phalcon\Config\Adapter\Yaml
- Class Phalcon\Config\Exception
- Class Phalcon\Crypt
- Class Phalcon\Crypt\Exception
- Interface Phalcon\CryptInterface
- Abstract class Phalcon\Db
- Abstract class Phalcon\Db\Adapter
- Abstract class Phalcon\Db\Adapter\Pdo
- Class Phalcon\Db\Adapter\Pdo\Mysql
- Class Phalcon\Db\Adapter\Pdo\Oracle
- Class Phalcon\Db\Adapter\Pdo\Postgresql
- Class Phalcon\Db\Adapter\Pdo\Sqlite
- Interface Phalcon\Db\AdapterInterface
- Class Phalcon\Db\Column
- Interface Phalcon\Db\ColumnInterface
- Abstract class Phalcon\Db\Dialect
- Class Phalcon\Db\Dialect\Oracle
- Class Phalcon\Db\Dialect\Postgresql
- Class Phalcon\Db\Dialect\Sqlite
- Interface Phalcon\Db\DialectInterface
- Class Phalcon\Db\Exception
- Class Phalcon\Db\Index
- Interface Phalcon\Db\IndexInterface
- Class Phalcon\Db\Profiler
- Class Phalcon\Db\Profiler\Item
- Class Phalcon\Db\RawValue
- Class Phalcon\Db\Reference
- Interface Phalcon\Db\ReferenceInterface
- Class Phalcon\Db\Result\Pdo
- Interface Phalcon\Db\ResultInterface
- Class Phalcon\Debug
- Class Phalcon\Debug\Dump
- Class Phalcon\Debug\Exception
- Interface Phalcon\DiInterface
- Abstract class Phalcon\Dispatcher
- Interface Phalcon\DispatcherInterface
- Class Phalcon\Escaper
- Class Phalcon\Escaper\Exception
- Interface Phalcon\EscaperInterface
- Class Phalcon\Events\Event
- Interface Phalcon\Events\EventsAwareInterface
- Class Phalcon\Events\Exception
- Class Phalcon\Events\Manager
- Interface Phalcon\Events\ManagerInterface
- Class Phalcon\Exception
- Class Phalcon\Filter
- Class Phalcon\Filter\Exception
- Interface Phalcon\Filter\UserFilterInterface
- Interface Phalcon\FilterInterface
- Abstract class Phalcon\Flash
- Class Phalcon\Flash\Direct
- Class Phalcon\Flash\Exception
- Class Phalcon\Flash\Session
- Interface Phalcon\FlashInterface
- Class Phalcon\Forms\Form
- Abstract class Phalcon\Forms\Element
- Class Phalcon\Forms\Element\Check
- Class Phalcon\Forms\Element\Email
- Class Phalcon\Forms\Element\File
- Class Phalcon\Forms\Element\Date
- Class Phalcon\Forms\Element\Hidden
- Class Phalcon\Forms\Element\Numeric
- Class Phalcon\Forms\Element\Password
- Class Phalcon\Forms\Element\Radio
- Class Phalcon\Forms\Element\Select
- Class Phalcon\Forms\Element\Submit
- Class Phalcon\Forms\Element\Text
- Class Phalcon\Forms\Element\TextArea
- Interface Phalcon\Forms\ElementInterface
- Class Phalcon\Forms\Exception
- Class Phalcon\Forms\Manager
- Class Phalcon\Http\Cookie
- Class Phalcon\Http\Cookie\Exception
- Class Phalcon\Http\Request
- Class Phalcon\Http\Request\Exception
- Class Phalcon\Http\Request\File
- Interface Phalcon\Http\Request\FileInterface
- Interface Phalcon\Http\RequestInterface
- Class Phalcon\Http\Response
- Class Phalcon\Http\Response\Cookies
- Interface Phalcon\Http\Response\CookiesInterface
- Class Phalcon\Http\Response\Exception
- Class Phalcon\Http\Response\Headers
- Interface Phalcon\Http\Response\HeadersInterface
- Interface Phalcon\Http\ResponseInterface
- Class Phalcon\Image
- Abstract class Phalcon\Image\Adapter
- Class Phalcon\Image\Adapter\Imagick
- Interface Phalcon\Image\AdapterInterface
- Class Phalcon\Image\Exception
- Class Phalcon\Kernel
- Class Phalcon\Loader
- Class Phalcon\Loader\Exception
- Abstract class Phalcon\Logger
- Abstract class Phalcon\Logger\Adapter
- Class Phalcon\Logger\Adapter\File
- Class Phalcon\Logger\Adapter\Firephp
- Class Phalcon\Logger\Adapter\Stream
- Class Phalcon\Logger\Adapter\Syslog
- Interface Phalcon\Logger\AdapterInterface
- Class Phalcon\Logger\Exception
- Abstract class Phalcon\Logger\Formatter
- Class Phalcon\Logger\Formatter\Firephp
- Class Phalcon\Logger\Formatter\Json
- Class Phalcon\Logger\Formatter\Line
- Class Phalcon\Logger\Formatter\Syslog
- Interface Phalcon\Logger\FormatterInterface
- Class Phalcon\Logger\Item
- Class Phalcon\Logger\Multiple
- Class Phalcon\Mvc\Application
- Class Phalcon\Mvc\Application\Exception
- Abstract class Phalcon\Mvc\Collection
- Abstract class Phalcon\Mvc\Collection\Behavior
- Class Phalcon\Mvc\Collection\Behavior\SoftDelete
- Class Phalcon\Mvc\Collection\Behavior\Timestampable
- Interface Phalcon\Mvc\Collection\BehaviorInterface
- Class Phalcon\Mvc\Collection\Document
- Class Phalcon\Mvc\Collection\Exception
- Class Phalcon\Mvc\Collection\Manager
- Interface Phalcon\Mvc\Collection\ManagerInterface
- Interface Phalcon\Mvc\CollectionInterface
- Abstract class Phalcon\Mvc\Controller
- Interface Phalcon\Mvc\ControllerInterface
- Class Phalcon\Mvc\Dispatcher
- Class Phalcon\Mvc\Dispatcher\Exception
- Interface Phalcon\Mvc\DispatcherInterface
- Interface Phalcon\Mvc\EntityInterface
- Class Phalcon\Mvc\Micro
- Class Phalcon\Mvc\Micro\Collection
- Interface Phalcon\Mvc\Micro\CollectionInterface
- Class Phalcon\Mvc\Micro\Exception
- Class Phalcon\Mvc\Micro\LazyLoader
- Interface Phalcon\Mvc\Micro\MiddlewareInterface
- Abstract class Phalcon\Mvc\Model
- Abstract class Phalcon\Mvc\Model\Behavior
- Class Phalcon\Mvc\Model\Behavior\SoftDelete
- Class Phalcon\Mvc\Model\Behavior\Timestampable
- Interface Phalcon\Mvc\Model\BehaviorInterface
- Class Phalcon\Mvc\Model\Criteria
- Interface Phalcon\Mvc\Model\CriteriaInterface
- Class Phalcon\Mvc\Model\Exception
- Class Phalcon\Mvc\Model\Manager
- Interface Phalcon\Mvc\Model\ManagerInterface
- Class Phalcon\Mvc\Model\Message
- Interface Phalcon\Mvc\Model\MessageInterface
- Abstract class Phalcon\Mvc\Model\MetaData
- Class Phalcon\Mvc\Model\MetaData\Apc
- Class Phalcon\Mvc\Model\MetaData\Files
- Class Phalcon\Mvc\Model\MetaData\Libmemcached
- Class Phalcon\Mvc\Model\MetaData\Memcache
- Class Phalcon\Mvc\Model\MetaData\Memory
- Class Phalcon\Mvc\Model\MetaData\Session
- Class Phalcon\Mvc\Model\MetaData\Strategy\Annotations
- Class Phalcon\Mvc\Model\MetaData\Strategy\Introspection
- Interface Phalcon\Mvc\Model\MetaData\StrategyInterface
- Class Phalcon\Mvc\Model\MetaData\Xcache
- Interface Phalcon\Mvc\Model\MetaDataInterface
- Class Phalcon\Mvc\Model\Query
- Class Phalcon\Mvc\Model\Query\Builder
- Interface Phalcon\Mvc\Model\Query\BuilderInterface
- Abstract class Phalcon\Mvc\Model\Query\Lang
- Class Phalcon\Mvc\Model\Query\Status
- Interface Phalcon\Mvc\Model\Query\StatusInterface
- Interface Phalcon\Mvc\Model\QueryInterface
- Class Phalcon\Mvc\Model\Relation
- Interface Phalcon\Mvc\Model\RelationInterface
- Interface Phalcon\Mvc\Model\ResultInterface
- Abstract class Phalcon\Mvc\Model\Resultset
- Class Phalcon\Mvc\Model\Resultset\Complex
- Class Phalcon\Mvc\Model\Resultset\Simple
- Abstract class Phalcon\Mvc\Model\Validator
- Class Phalcon\Mvc\Model\Validator\Email
- Class Phalcon\Mvc\Model\Validator\Exclusionin
- Class Phalcon\Mvc\Model\Validator\Inclusionin
- Class Phalcon\Mvc\Model\Validator\Ip
- Class Phalcon\Mvc\Model\Validator\Numericality
- Class Phalcon\Mvc\Model\Validator\PresenceOf
- Class Phalcon\Mvc\Model\Validator\Regex
- Class Phalcon\Mvc\Model\Validator\StringLength
- Class Phalcon\Mvc\Model\Validator\Uniqueness
- Class Phalcon\Mvc\Model\Validator\Url
- Interface Phalcon\Mvc\Model\ValidatorInterface
- Interface Phalcon\Mvc\Model\ResultsetInterface
- Class Phalcon\Mvc\Model\Row
- Class Phalcon\Mvc\Model\Transaction
- Class Phalcon\Mvc\Model\Transaction\Exception
- Class Phalcon\Mvc\Model\Transaction\Failed
- Class Phalcon\Mvc\Model\Transaction\Manager
- Interface Phalcon\Mvc\Model\Transaction\ManagerInterface
- Interface Phalcon\Mvc\Model\TransactionInterface
- Class Phalcon\Mvc\Model\ValidationFailed
- Interface Phalcon\Mvc\ModelInterface
- Interface Phalcon\Mvc\ModuleDefinitionInterface
- Class Phalcon\Mvc\Router
- Class Phalcon\Mvc\Router\Annotations
- Class Phalcon\Mvc\Router\Exception
- Class Phalcon\Mvc\Router\Group
- Interface Phalcon\Mvc\Router\GroupInterface
- Class Phalcon\Mvc\Router\Route
- Interface Phalcon\Mvc\Router\RouteInterface
- Interface Phalcon\Mvc\RouterInterface
- Class Phalcon\Mvc\Url
- Class Phalcon\Mvc\Url\Exception
- Interface Phalcon\Mvc\UrlInterface
- Class Phalcon\Mvc\User\Component
- Class Phalcon\Mvc\User\Module
- Class Phalcon\Mvc\User\Plugin
- Class Phalcon\Mvc\View
- Abstract class Phalcon\Mvc\View\Engine
- Class Phalcon\Mvc\View\Engine\Php
- Class Phalcon\Mvc\View\Engine\Volt
- Class Phalcon\Mvc\View\Engine\Volt\Compiler
- Interface Phalcon\Mvc\View\EngineInterface
- Class Phalcon\Mvc\View\Exception
- Class Phalcon\Mvc\View\Simple
- Interface Phalcon\Mvc\ViewBaseInterface
- Interface Phalcon\Mvc\ViewInterface
- Abstract class Phalcon\Paginator\Adapter
- Class Phalcon\Paginator\Adapter\Model
- Class Phalcon\Paginator\Adapter\NativeArray
- Class Phalcon\Paginator\Adapter\QueryBuilder
- Interface Phalcon\Paginator\AdapterInterface
- Class Phalcon\Paginator\Exception
- Class Phalcon\Queue\Beanstalk
- Class Phalcon\Queue\Beanstalk\Job
- Final class Phalcon\Registry
- Class Phalcon\Security
- Class Phalcon\Security\Exception
- Abstract class Phalcon\Session
- Abstract class Phalcon\Session\Adapter
- Class Phalcon\Session\Adapter\Files
- Class Phalcon\Session\Adapter\Libmemcached
- Class Phalcon\Session\Adapter\Memcache
- Interface Phalcon\Session\AdapterInterface
- Class Phalcon\Session\Bag
- Interface Phalcon\Session\BagInterface
- Class Phalcon\Session\Exception
- Class Phalcon\Tag
- Class Phalcon\Tag\Exception
- Abstract class Phalcon\Tag\Select
- Abstract class Phalcon\Text
- Abstract class Phalcon\Translate
- Abstract class Phalcon\Translate\Adapter
- Class Phalcon\Translate\Adapter\Csv
- Class Phalcon\Translate\Adapter\Gettext
- Class Phalcon\Translate\Adapter\NativeArray
- Interface Phalcon\Translate\AdapterInterface
- Class Phalcon\Translate\Exception
- Class Phalcon\Validation
- Class Phalcon\Validation\Exception
- Class Phalcon\Validation\Message
- Class Phalcon\Validation\Message\Group
- Interface Phalcon\Validation\MessageInterface
- Abstract class Phalcon\Validation\Validator
- Class Phalcon\Validation\Validator\Alnum
- Class Phalcon\Validation\Validator\Alpha
- Class Phalcon\Validation\Validator\Between
- Class Phalcon\Validation\Validator\Confirmation
- Class Phalcon\Validation\Validator\Digit
- Class Phalcon\Validation\Validator\Email
- Class Phalcon\Validation\Validator\ExclusionIn
- Class Phalcon\Validation\Validator\File
- Class Phalcon\Validation\Validator\Identical
- Class Phalcon\Validation\Validator\InclusionIn
- Class Phalcon\Validation\Validator\Numericality
- Class Phalcon\Validation\Validator\PresenceOf
- Class Phalcon\Validation\Validator\Regex
- Class Phalcon\Validation\Validator\StringLength
- Class Phalcon\Validation\Validator\Uniqueness
- Class Phalcon\Validation\Validator\Url
- Interface Phalcon\Validation\ValidatorInterface
- Class Phalcon\Version
- 参考手册
- 安装（Installation）
- 教程 1：让我们通过例子来学习（Tutorial 1: Let’s learn by example）
- 教程 2：Introducing INVO（Tutorial 2: Introducing INVO）
- 教程 3: Securing INVO
- 教程 4: Using CRUDs
- 教程 5: Customizing INVO
- 教程 6: Vkuró
- 教程 7：创建简单的 REST API（Tutorial 7: Creating a Simple REST API）
- 示例列表（List of examples）
- 依赖注入与服务定位器（Dependency Injection/Service Location）
- MVC 架构（The MVC Architecture）
- 使用控制器（Using Controllers）
- 使用模型（Working with Models）
- 模型元数据（Models Meta-Data）
- 事务管理（Model Transactions）
- Phalcon 查询语言（Phalcon Query Language (PHQL)）
- 缓存对象关系映射（Caching in the ORM）
- 对象文档映射 ODM (Object-Document Mapper)
- 使用视图（Using Views）
- 视图助手（View Helpers）
- 资源文件管理（Assets Management）
- Volt 模版引擎（Volt: Template Engine）
- MVC 应用（MVC Applications）
- 路由（Routing）
- 调度控制器（Dispatching Controllers）
- 微应用（Micro Applications）
- 使用命名空间（Working with Namespaces）
- 事件管理器（Events Manager）
- Request Environment
- 返回响应（Returning Responses）
- Cookie 管理（Cookies Management）
- 生成 URL 和 路径（Generating URLs and Paths）
- 闪存消息（Flashing Messages）
- 使用 Session 存储数据（Storing data in Session）
- 过滤与清理（Filtering and Sanitizing）
- 上下文编码（Contextual Escaping）
- 验证（Validation）
- 表单（Forms）
- 读取配置（Reading Configurations）
- 分页（Pagination）
- 使用缓存提高性能（Improving Performance with Cache）
- 安全（Security）
- Encryption/Decryption
- 访问控制列表 ACL（Access Control Lists ACL）
- 多语言支持（Multi-lingual Support）
- Universal Class Loader
- 日志记录（Logging）
- 注释解析器（Annotations Parser）
- 命令行应用（Command Line Applications）
- 队列（Queueing）
- 数据库抽象层（Database Abstraction Layer）
- 国际化（Internationalization）
- 数据库迁移（Database Migrations）
- 调试应用程序（Debugging Applications）
- Phalcon 开发工具（Phalcon Developer Tools）
- 提高性能：下一步该做什么？（Increasing Performance: What’s next?）
- 单元测试（Unit testing）
- 授权（License）