To speed up development Phalcon\Mvc\Model helps you to query fields and constraints from tables related to models. To achieve this, Phalcon\Mvc\Model\MetaData is available to manage and cache table metadata.
Phalcon\Mvc\Model 能幫助你查詢字段從表關聯到模型和約束從而加快你的開發效率。為了達到這個目標, Phalcon\Mvc\Model\MetaData元數據管理和緩存表的元數據是有必要的。
Sometimes it is necessary to get those attributes when working with models. You can get a metadata instance as follows:
有時候，在使用模型時需要獲得這些屬性。您可以獲得一個元數據實例:
~~~
<?php
$robot = new Robots();
// Get Phalcon\Mvc\Model\Metadata instance
$metadata = $robot->getModelsMetaData();
// Get robots fields names
$attributes = $metadata->getAttributes($robot);
print_r($attributes);
// Get robots fields data types
$dataTypes = $metadata->getDataTypes($robot);
print_r($dataTypes);
~~~
#### 緩存元數據（Caching Metadata）
Once the application is in a production stage, it is not necessary to query the metadata of the table from the database system each time you use the table. This could be done caching the metadata using any of the following adapters:
一旦應用程序處于生產階段，就不需要在每次使用該表時從數據庫系統查詢表的元數據。可以使用以下任何一個適配器來緩存元數據:
| Adapter 適配器 | Description 描述 | API |
| --- | --- | --- |
| Memory 內存 | This adapter is the default. The metadata is cached only during the request. When the request is completed, the metadata are released as part of the normal memory of the request. This adapter is perfect when the application is in development so as to refresh the metadata in each request containing the new and/or modified fields. 這個適配器是默認的。元數據僅在請求期間被緩存。當請求完成時，元數據作為請求的正常內存的一部分被釋放。當應用程序處于開發階段時，該適配器是完美的，以便在包含新/或修改字段的每個請求中刷新元數據。 | Phalcon\Mvc\Model\MetaData\Memory |
| Session 會話 | This adapter stores metadata in the `$_SESSION `superglobal. This adapter is recommended only when the application is actually using a small number of models. The metadata are refreshed every time a new session starts. This also requires the use of `session_start()` to start the session before using any models. 該適配器將元數據存儲在$SESSION超全局中。只有當應用程序實際使用少量的模型時，才推薦這個適配器。每次新會話開始時，元數據都會刷新。這還需要使用sessionstart()在使用任何模型之前，先啟動會話。 | Phalcon\Mvc\Model\MetaData\Session |
| Apc | This adapter uses the Alternative PHP Cache (APC) to store the table metadata. You can specify the lifetime of the metadata with options. This is the most recommended way to store metadata when the application is in production stage. 這個適配器使用另一個PHP緩存(APC)來存儲表元數據。您可以使用選項指定元數據的生命周期。當應用程序處于生產階段時，這是最推薦的存儲元數據的方法。 | Phalcon\Mvc\Model\MetaData\Apc |
| XCache | This adapter uses XCache to store the table metadata. You can specify the lifetime of the metadata with options. This is the most recommended way to store metadata when the application is in production stage. 這個適配器使用XCache來存儲表元數據。您可以使用選項指定元數據的生命周期。當應用程序處于生產階段時，這是最推薦的存儲元數據的方法。 | Phalcon\Mvc\Model\MetaData\Xcache |
| Files | This adapter uses plain files to store metadata. By using this adapter the disk-reading is increased but the database access is reduced. 該適配器使用普通文件存儲元數據。通過使用這個適配器，磁盤讀取增加了，但是數據庫訪問減少了。 | Phalcon\Mvc\Model\MetaData\Files |
As other ORM’s dependencies, the metadata manager is requested from the services container:
作為其他ORM的依賴項，從服務容器請求元數據管理器:
~~~
<?php
use Phalcon\Mvc\Model\MetaData\Apc as ApcMetaData;
$di["modelsMetadata"] = function () {
// Create a metadata manager with APC
$metadata = new ApcMetaData(
[
"lifetime" => 86400,
"prefix" => "my-prefix",
]
);
return $metadata;
};
~~~
#### 元數據策略（Metadata Strategies）
As mentioned above the default strategy to obtain the model’s metadata is database introspection. In this strategy, the information schema is used to know the fields in a table, its primary key, nullable fields, data types, etc.
正如上面提到的，獲取模型元數據的默認策略是數據庫內省。在這個策略中，信息模式用于了解表中的字段、它的主鍵、可空字段、數據類型等。
You can change the default metadata introspection in the following way:
您可以以下方式更改默認的元數據內省:
~~~
<?php
use Phalcon\Mvc\Model\MetaData\Apc as ApcMetaData;
$di["modelsMetadata"] = function () {
// Instantiate a metadata adapter
$metadata = new ApcMetaData(
[
"lifetime" => 86400,
"prefix" => "my-prefix",
]
);
// Set a custom metadata introspection strategy
$metadata->setStrategy(
new MyIntrospectionStrategy()
);
return $metadata;
};
~~~
#### 數據庫內部策略（Database Introspection Strategy）
This strategy doesn’t require any customization and is implicitly used by all the metadata adapters.
此策略不需要任何定制，并且被所有元數據適配器隱式地使用。
#### 注釋策略（Annotations Strategy）
This strategy makes use of annotations to describe the columns in a model:
該策略使用注釋來描述模型中的列:
~~~
<?php
use Phalcon\Mvc\Model;
class Robots extends Model
{
/**
* @Primary
* @Identity
* @Column(type="integer", nullable=false)
*/
public $id;
/**
* @Column(type="string", length=70, nullable=false)
*/
public $name;
/**
* @Column(type="string", length=32, nullable=false)
*/
public $type;
/**
* @Column(type="integer", nullable=false)
*/
public $year;
}
~~~
Annotations must be placed in properties that are mapped to columns in the mapped source. Properties without the @Column annotation are handled as simple class attributes.
注釋必須放在映射到映射源中的列的屬性中。沒有@column注釋的屬性被處理為簡單的類屬性。
The following annotations are supported:
下面的注釋得到了支持:
| Name 名字 | Description 描述 |
| --- | --- |
| Primary | Mark the field as part of the table’s primary key 將字段標記為表的主鍵的一部分 |
| Identity | The field is an auto_increment/serial column 該字段是一個自動遞增/串行列 |
| Column | This marks an attribute as a mapped column 它將一個屬性標記為一個映射的列 |
The annotation @Column supports the following parameters:
@column的注釋支持以下參數:
| Name | Description 描述 |
| --- | --- |
| type | The column’s type (string, integer, decimal, boolean) 列的類型(字符串、整數、小數、布爾) |
| length | The column’s length if any 列的長度如果有的話 |
| nullable | Set whether the column accepts null values or not 設置該列是否接受null值 |
The annotations strategy could be set up this way:
注釋策略可以這樣設置:
~~~
<?php
use Phalcon\Mvc\Model\MetaData\Apc as ApcMetaData;
use Phalcon\Mvc\Model\MetaData\Strategy\Annotations as StrategyAnnotations;
$di["modelsMetadata"] = function () {
// Instantiate a metadata adapter
$metadata = new ApcMetaData(
[
"lifetime" => 86400,
"prefix" => "my-prefix",
]
);
// Set a custom metadata database introspection
$metadata->setStrategy(
new StrategyAnnotations()
);
return $metadata;
};
~~~
#### 自定義元數據（Manual Metadata）
Phalcon can obtain the metadata for each model automatically without the developer must set them manually using any of the introspection strategies presented above.
如果沒有開發人員必須手動使用上面介紹的任何一種內省策略，那么就可以自動為每個模型獲取元數據。
The developer also has the option of define the metadata manually. This strategy overrides any strategy set in the metadata manager. New columns added/modified/removed to/from the mapped table must be added/modified/removed also for everything to work properly.
開發人員還可以手動定義元數據。該策略覆蓋了元數據管理器中的任何策略。從映射表中添加/修改/刪除的新列必須被添加/修改/刪除，以便所有的工作都能正常工作。
The following example shows how to define the metadata manually:
下面的例子展示了如何手動定義元數據:
~~~
<?php
use Phalcon\Mvc\Model;
use Phalcon\Db\Column;
use Phalcon\Mvc\Model\MetaData;
class Robots extends Model
{
public function metaData()
{
return array(
// Every column in the mapped table
MetaData::MODELS_ATTRIBUTES => [
"id",
"name",
"type",
"year",
],
// Every column part of the primary key
MetaData::MODELS_PRIMARY_KEY => [
"id",
],
// Every column that isn't part of the primary key
MetaData::MODELS_NON_PRIMARY_KEY => [
"name",
"type",
"year",
],
// Every column that doesn't allows null values
MetaData::MODELS_NOT_NULL => [
"id",
"name",
"type",
],
// Every column and their data types
MetaData::MODELS_DATA_TYPES => [
"id" => Column::TYPE_INTEGER,
"name" => Column::TYPE_VARCHAR,
"type" => Column::TYPE_VARCHAR,
"year" => Column::TYPE_INTEGER,
],
// The columns that have numeric data types
MetaData::MODELS_DATA_TYPES_NUMERIC => [
"id" => true,
"year" => true,
],
// The identity column, use boolean false if the model doesn't have
// an identity column
MetaData::MODELS_IDENTITY_COLUMN => "id",
// How every column must be bound/casted
MetaData::MODELS_DATA_TYPES_BIND => [
"id" => Column::BIND_PARAM_INT,
"name" => Column::BIND_PARAM_STR,
"type" => Column::BIND_PARAM_STR,
"year" => Column::BIND_PARAM_INT,
],
// Fields that must be ignored from INSERT SQL statements
MetaData::MODELS_AUTOMATIC_DEFAULT_INSERT => [
"year" => true,
],
// Fields that must be ignored from UPDATE SQL statements
MetaData::MODELS_AUTOMATIC_DEFAULT_UPDATE => [
"year" => true,
],
// Default values for columns
MetaData::MODELS_DEFAULT_VALUES => [
"year" => "2015",
],
// Fields that allow empty strings
MetaData::MODELS_EMPTY_STRING_VALUES => [
"name" => true,
],
);
}
}
~~~
- Welcome
- 安裝
- XAMPP 下的安裝
- WAMP 下安裝
- Apache 安裝說明
- Nginx 安裝說明
- Cherokee 安裝說明
- 使用 PHP 內置 web 服務器
- Phalcon 開發工具
- Windows 系統下使用 Phalcon 開發工具
- Mac OS X 系統下使用 Phalcon 開發工具
- Linux 系統下使用 Phalcon 開發工具
- 教程 1：讓我們通過例子來學習
- 教程 2：INVO簡介
- 教程 3: 保護INVO
- 教程4: 使用CRUD
- 教程5: 定制INVO
- 教程6: V?kuró
- 教程 7：創建簡單的 REST API
- 依賴注入與服務定位器（Dependency Injection/Service Location）
- MVC 架構（The MVC Architecture）
- 使用控制器（Using Controllers）
- 使用模型（Working with Models）
- 模型關系（Model Relationships）
- 模型事件（Model Events）
- 模型行為（Model Behaviors）
- 模型元數據（Models Metadata）
- 事務管理（Model Transactions）
- 模型驗證（Validating Models）
- Working with Models (Advanced)
- Phalcon 查詢語言（Phalcon Query Language (PHQL)）
- 緩存對象關系映射（Caching in the ORM）
- 對象文檔映射 ODM (Object-Document Mapper)
- 使用視圖（Using Views）
- 視圖助手 (Tags)（View Helpers (Tags)）