We have seen how to use Active Record (AR) to get data from a single data table. In this section, we explain how to use AR to connect multiple related data tables and retrieve the joined data set.
In order to use relational AR, we recommend defining primary key-foreign key constraints in the tables that need to be related. These constraints can help ensure the consistency and integrity of related data.
For simplicity, we demonstrate the examples in this section using the data structure in an entity-relationship (ER) diagram as shown below.
INFO: Support for foreign key constraints varies between DBMSs. SQLite
Before we use AR to perform related queries, we need to let AR know how one AR class is related to another.
The relationship between two AR classes is directly related through the relationship between the data tables represented by the AR classes. From a database perspective, there are three types of relationships between tables A and B: one-to-many (such as tbl_user and tbl_post), one-to-one (such as tbl_user and tbl_profile) and many-to-many Many (many-to-many such as tbl_category and tbl_post). In AR, there are four kinds of relationships:
BELONGS_TO（属于）: 如果表 A 和 B 之间的关系是一对多，则 表 B 属于 表 A (例如 Post 属于 User); HAS_MANY（有多个）: 如果表 A 和 B 之间的关系是一对多，则 A 有多个 B (例如 User 有多个 Post); HAS_ONE（有一个）: 这是 HAS_MANY 的一个特例，A 最多有一个 B (例如 User 最多有一个 Profile); MANY_MANY: 这个对应于数据库中的多对多关系。 由于多数 DBMS 不直接支持 多对多 关系，因此需要有一个关联表将 多对多 关系分割为 一对多 关系。 在我们的示例数据结构中，tbl_post_category 就是用于此目的的。在 AR 术语中，我们可以解释 MANY_MANY 为 BELONGS_TO 和 HAS_MANY 的组合。 例如，Post 属于多个（belongs to many） Category ，Category 有多个（has many） Post.
Defining relationships in AR requires overriding the relations() method in CActiveRecord. This method returns an array of relationship configurations. Each array element represents a single relationship in the following format.
'VarName'=>array('RelationType', 'ClassName', 'ForeignKey', ...additional options)VarName is the name of the relationship; RelationType specifies the relationship type, which can be one of the following four constants: self::BELONGS_TO, self::HAS_ONE, self::HAS_MANY and self::MANY_MANY ; ClassName is the name of the AR class associated with this AR class; ForeignKey specifies the foreign key (one or more) used in the relationship. Additional options can be specified at the end of each relationship (more on this later).
The following code demonstrates how to define the relationship between the User and Post classes:
class Post extends CActiveRecord
{
......
public function relations()
{
return array(
'author'=>array(self::BELONGS_TO, 'User', 'author_id'),
'categories'=>array(self::MANY_MANY, 'Category',
'tbl_post_category(post_id, category_id)'),
);
}
}
class User extends CActiveRecord
{
......
public function relations()
{
return array(
'posts'=>array(self::HAS_MANY, 'Post', 'author_id'),
'profile'=>array(self::HAS_ONE, 'Profile', 'owner_id'),
);
}
}Information: The foreign key may be compound, containing two or more columns. In this case, we should link these foreign key names, separated by spaces or commas. For the MANY_MANY relationship type, the name of the related table must also be specified in the foreign key. For example, the categories relationship in Post is specified by the foreign key tbl_post_category(post_id, category_id).
Relationship definitions in an AR class implicitly add an attribute to the class for each relationship. After a correlation query is executed, the corresponding properties will be populated with the associated AR instance. For example, if $author represents a User AR instance, we can access its associated Post instance using $author->posts.
The simplest way to perform related queries is to read the related attributes in an AR instance. If this property has not been accessed before, a join query will be initialized that joins the two tables and filters using the primary key of the current AR instance. The query results are saved to the property as an instance of the associated AR class. This is the legendary lazy loading (also translated as late loading) method. For example, a related query is only executed when the related object is accessed for the first time. The following example demonstrates how to use this approach:
// 获取 ID 为 10 的帖子 $post=Post::model()->findByPk(10); // 获取帖子的作者(author): 此处将执行一个关联查询。 $author=$post->author;
Information: If there is no related instance in the relationship, the corresponding property will be null or an empty array. The result of the BELONGS_TO and HAS_ONE relationships is null, and the result of HAS_MANY and MANY_MANY is an empty array. Note that the HAS_MANY and MANY_MANY relationships return arrays of objects, and you need to iterate over these results before accessing any properties. Otherwise, you may receive a "Trying to get property of non-object" error.
Lazy loading is very convenient, but in some cases it is not efficient. If we want to get the authors of N posts, using this lazy loading will result in N join queries being executed. In this case, we should use eager loading instead.
The eager loading method will obtain the associated AR instance while obtaining the main AR instance. This is done by using the with method when using the find or findAll methods in AR. For example:
$posts=Post::model()->with('author')->findAll();The above code will return an array of Post instances. Unlike lazy loading, before we access the author property in each Post instance, it has already been populated with the associated User instance. Eager loading returns all posts and their authors through a single join query, rather than performing a join query for each post.
We can specify multiple relationship names in the with() method, and eager loading will retrieve them all at once. For example, the following code will retrieve the post along with its author and category.
$posts=Post::model()->with('author','categories')->findAll();We can also implement nested eager loading. Like below, we pass a hierarchical relation name expression to the with() method instead of a list of relation names:
$posts=Post::model()->with( 'author.profile', 'author.posts', 'categories' )->findAll();
上述示例将取回所有帖子及其作者和所属分类。它还同时取回每个作者的简介（author.profile）和帖子（author.posts）。
从版本 1.1.0 开始，渴求式加载也可以通过指定 CDbCriteria::with 的属性执行，就像下面这样：
$criteria=new CDbCriteria; $criteria->with=array( 'author.profile', 'author.posts', 'categories', ); $posts=Post::model()->findAll($criteria);
或者
$posts=Post::model()->findAll(array( 'with'=>array( 'author.profile', 'author.posts', 'categories', ) );
我们提到在关系声明时可以指定附加的选项。这些 名-值 对形式的选项用于自定义关系型查询。概括如下：
select: 关联的 AR 类中要选择(select)的列的列表。 默认为 '*'，即选择所有列。此选项中的列名应该是已经消除歧义的。 condition: 即 WHERE 条件。默认为空。此选项中的列名应该是已经消除歧义的。 params: 要绑定到所生成的 SQL 语句的参数。应该以 名-值 对数组的形式赋值。此选项从 1.0.3 版起有效。 on: 即 ON 语句。此处指定的条件将会通过 AND 操作符附加到 join 条件中。此选项中的列名应该是已经消除歧义的。此选项不会应用到 MANY_MANY 关系中。此选项从 1.0.2 版起有效。 order: 即 ORDER BY 语句。默认为空。 此选项中的列名应该是已经消除歧义的。 with: 应该和该对象一起加载的一些列子相关对象. 注意不适当的使用该选项可能造成无限关系循环. joinType: 该关系的join类型. 默认是LEFT OUTER JOIN. alias: 和该关系关联的表的别名. 这个选项从yii版本1.0.1起有效. 默认是null, 意味着表别名和关系名称一样. together: 该关系所关联的表是否应该强制和主表和其他表联接. 这个选项只对HAS_MANY 和 MANY_MANY 这两种关系有意义. 如果这个选项设置为false, 那么HAS_MANY或者 MANY_MANY 关系所关联的表将会和主表在相互隔离的SQL查询中联接, 这将会提高整个查询的性能，因为这会返回较少的重复数据. 如果这个选项设置为true, 关联的表总会和主表联接在一个SQL查询中, 即使主表是分页的. 如果这个选项没有设置， 关联表只有主表不是分页的情况下才会和主表联接在一个SQL查询中. 更多细节，请查看章节 "关系查询性能". 这个选项从版本1.0.3开始支持. join: 额外的 JOIN 条款. 默认是空. 这个选项从版本1.1.3开始支持. group: GROUP BY 条款. 默认是空. 在该选项中列名的使用应该是无歧义的. having: HAVING 条款. 默认是空. 在该选项中列名的使用应该是无歧义的. 注意: 从版本1.0.1开始支持该选项. index: 列名被用于存储关系对象数组的键值. 如果表不设置这个选项, 关系对象数组将会使用从0开始的整型索引.这个选项只能用于设置HAS_MANY 和 MANY_MANY 关系类型. yii框架从版本1.0.7以后开始支持该选项
此外, 下面这些选项在懒惰式加载中对特定关系是有效的:
limit: 被查询的行数限制. 这个选项不能用于 BELONGS_TO 关系. offset: 被查询的起始行.这个选项不能用于 BELONGS_TO 关系.
下面我们通过加入上述的一些选项来修改 User中的posts 关系声明:
class User extends CActiveRecord
{
public function relations()
{
return array(
'posts'=>array(self::HAS_MANY, 'Post', 'author_id',
'order'=>'posts.create_time DESC',
'with'=>'categories'
),
'profile'=>array(self::HAS_ONE, 'Profile', 'owner_id'),
);
}
}现在如果你访问$author->posts, 就会得到基于创建时间排序的author's posts，并且每一个post 实例都会加载其分类.
当两表或多表联接出现同一个列名时, 需要排除歧义.这可以通过给列名加上表别名前缀来实现.
在关系 AR 查询中, 主表别名默认是 t, 同时关系表的别名默认是相应的关系名称.例如, 在下面的语句中, Post 和 Comment的别名分别是t 和 comments:
$posts=Post::model()->with('comments')->findAll();现在假设 Post 和 Comment 都有一个表明其创建时间的列叫做create_time,并且我们想要将posts和其对应的comments放在一起查询，排序方式首先是posts的创建时间，然后是comments的创建时间。我们需要按照如下方式消除列名歧义:
$posts=Post::model()->with('comments')->findAll(array(
'order'=>'t.create_time, comments.create_time'
));注意: 列歧义的行为从版本1.1.0起有所改变. 在版本1.0.x中,默认Yii会为每一个关系表自动生成表别名, 并且我们必须使用前缀??. 来引用自动生成的别名. 此外，在1.0.x版本中, 主表别名就是表名本身
从版本1.0.2开始,我们可以在with()和with选项中使用动态关系查询选项. 动态选项会覆盖已存在的如relations()方法中所指定的选项. 例如，在上面的User 模型中, 如果我们想要使用渴求式加载方式以升序为每一个author附带 posts （在关系定义中默认排序是降序), 可以按照如下方式：
User::model()->with(array(
'posts'=>array('order'=>'posts.create_time ASC'),
'profile',
))->findAll();从版本1.0.5开始, 动态查询选项可以在使用懒惰式加载方式进行关系查询的时候使用. 我们可以调用一个关系名称相同的方法并且传入动态查询选项作为参数. 例如, 下面的代码返回status为1的 user's posts:
$user=User::model()->findByPk(1);
$posts=$user->posts(array('condition'=>'status=1'));As we described above, the eager loading approach is mainly used in the scenario when we need to access many related objects. It generates a big complex SQL statement by joining all needed tables. A big SQL statement is preferrable in many cases since it simplifies filtering based on a column in a related table. It may not be efficient in some cases, however.
Consider an example where we need to find the latest posts together with their comments. Assuming each post has 10 comments, using a single big SQL statement, we will bring back a lot of redundant post data since each post will be repeated for every comment it has. Now let's try another approach: we first query for the latest posts, and then query for their comments. In this new approach, we need to execute two SQL statements. The benefit is that there is no redundancy in the query results.
So which approach is more efficient? There is no absolute answer. Executing a single big SQL statement may be more efficient because it causes less overhead in DBMS for yparsing and executing the SQL statements. On the other hand, using the single SQL statement, we end up with more redundant data and thus need more time to read and process them.
For this reason, Yii provides the together query option so that we choose between the two approaches as needed. By default, Yii adopts the first approach, i.e., generating a single SQL statement to perform eager loading. We can set the together option to be false in the relation declarations so that some of tables are joined in separate SQL statements. For example, in order to use the second approach to query for the latest posts with their comments, we can declare the comments relation in Post class as follows,
public function relations()
{
return array(
'comments' => array(self::HAS_MANY, 'Comment', 'post_id', 'together'=>false),
);
}We can also dynamically set this option when we perform the eager loading:
$posts = Post::model()->with(array('comments'=>array('together'=>false)))->findAll();Note: In version 1.0.x, the default behavior is that Yii will generate and execute N+1 SQL statements if there are N HAS_MANY or MANY_MANY relations. Each HAS_MANY or MANY_MANY relation has its own SQL statement. By calling the together() method after with(), we can enforce only a single SQL statement is generated and executed. For example,
$posts=Post::model()->with( 'author.profile', 'author.posts', 'categories' )->together()->findAll();
Note: Statistical query has been supported since version 1.0.4.
Besides the relational query described above, Yii also supports the so-called statistical query (or aggregational query). It refers to retrieving the aggregational information about the related objects, such as the number of comments for each post, the average rating for each product, etc. Statistical query can only be performed for objects related in HAS_MANY (e.g. a post has many comments) or MANY_MANY (e.g. a post belongs to many categories and a category has many posts).
Performing statistical query is very similar to performing relation query as we described before. We first need to declare the statistical query in the relations() method of CActiveRecord like we do with relational query.
class Post extends CActiveRecord
{
public function relations()
{
return array(
'commentCount'=>array(self::STAT, 'Comment', 'post_id'),
'categoryCount'=>array(self::STAT, 'Category', 'post_category(post_id, category_id)'),
);
}
}In the above, we declare two statistical queries: commentCount calculates the number of comments belonging to a post, and categoryCount calculates the number of categories that a post belongs to. Note that the relationship between Post and Comment is HAS_MANY, while the relationship between Post and Category is MANY_MANY (with the joining table post_category). As we can see, the declaration is very similar to those relations we described in earlier subsections. The only difference is that the relation type is STAT here.
With the above declaration, we can retrieve the number of comments for a post using the expression $post->commentCount. When we access this property for the first time, a SQL statement will be executed implicitly to retrieve the corresponding result. As we already know, this is the so-called lazy loading approach. We can also use the eager loading approach if we need to determine the comment count for multiple posts:
$posts=Post::model()->with('commentCount', 'categoryCount')->findAll();The above statement will execute three SQLs to bring back all posts together with their comment counts and category counts. Using the lazy loading approach, we would end up with 2*N+1 SQL queries if there are N posts.
By default, a statistical query will calculate the COUNT expression (and thus the comment count and category count in the above example). We can customize it by specifying additional options when we declare it in relations(). The available options are summarized as below.
select: the statistical expression. Defaults to COUNT(*), meaning the count of child objects. defaultValue: the value to be assigned to those records that do not receive a statistical query result. For example, if a post does not have any comments, its commentCount would receive this value. The default value for this option is 0. condition: the WHERE clause. It defaults to empty. params: the parameters to be bound to the generated SQL statement. This should be given as an array of name-value pairs. order: the ORDER BY clause. It defaults to empty. group: the GROUP BY clause. It defaults to empty. having: the HAVING clause. It defaults to empty.
Note: The support for named scopes has been available since version 1.0.5.
Relational query can also be performed in combination with named scopes. It comes in two forms. In the first form, named scopes are applied to the main model. In the second form, named scopes are applied to the related models.
The following code shows how to apply named scopes to the main model.
$posts=Post::model()->published()->recently()->with('comments')->findAll();This is very similar to non-relational queries. The only difference is that we have the with() call after the named-scope chain. This query would bring back recently published posts together with their comments.
And the following code shows how to apply named scopes to the related models.
$posts=Post::model()->with('comments:recently:approved')->findAll();The above query will bring back all posts together with their approved comments. Note that comments refers to the relation name, while recently and approved refer to two named scopes declared in the Comment model class. The relation name and the named scopes should be separated by colons.
Named scopes can also be specified in the with option of the relational rules declared in CActiveRecord::relations(). In the following example, if we access $user->posts, it would bring back all approved comments of the posts.
class User extends CActiveRecord
{
public function relations()
{
return array(
'posts'=>array(self::HAS_MANY, 'Post', 'author_id',
'with'=>'comments:approved'),
);
}
}Note: Named scopes applied to related models must be specified in CActiveRecord::scopes. As a result, they cannot be parameterized.
以上就是Yii框架官方指南系列26——使用数据库:关系型 Active Record的内容，更多相关内容请关注PHP中文网（www.php.cn）！
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
