StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19447237
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-18T10:20:10.043
FavoriteCount
0
LastActivityDate
2013-10-18T10:30:35.777
LastEditDate
2013-10-18T10:30:35.777
LastEditorUserId
839332
OwnerUserId
839332
ParentId
19383101
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
The best way I found for creating an extra searchable relation column in a gridview is by using the following pattern: <pre class="lang-php prettyprint-override"><code>// the model class class Product extends CActiveRecord { // create a custom field in your model class to hold your search data public $searchSupplierName; // [...] // make sure the custom field is safe to set in your rules public function rules() { return array( // [...] // add your custom field name to this rule array('id, searchSupplierName', 'safe', 'on'=>'search'), ); } // edit your search function public function search() { // [...] // use the value of the custom attribute as a condition in your search $criteria->compare('supplier.name', $this->searchSupplierName,true); // you could use something like the following // to make sure you don't fire a lazy loading query // for every result that is shown on the gridview. if($this->searchSupplierName) $criteria->with = array( 'supplier' ); // then do something like this if you want to be able to sort on the field return new CActiveDataProvider($this, array( 'criteria'=>$criteria, 'sort'=>array( 'attributes'=>array( 'searchSupplierName'=>array( 'asc'=>'supplier.name', 'desc'=>'supplier.name DESC', ), '*', // this makes sure the rest of the field sorts keep working ), ), )); } } </code></pre> <pre class="lang-php prettyprint-override"><code>// in the template <?php $this->widget('zii.widgets.grid.CGridView', array( // set the dataprovider to the changed search function output 'dataProvider' => $model->search(), 'filter' => $model, // model is an instance of Product in this case (obviously ;) // [...] 'columns' => array( // [...] // this is the column we care (extra) about // notice I still use a custom value here (as @ethan describes in his answer) array( 'name' => 'searchSupplierName', 'value' => '$data->supplier->name', ), ), )); ?> </code></pre> This solution should work for (almost) any case you want. It is the best solution I can think of if you want text based filtering on the column. But there are <a href="http://www.yiiframework.com/forum/index.php?/topic/9083-search-filter-of-a-relations-field-through-cgridview/" rel="nofollow">other options</a> as well. For example if you just want to search on a <code>relation_id</code> by using a combobox to find the right value there are <a href="http://www.yiiframework.com/forum/index.php/topic/9083-search-filter-of-a-relations-field-through-cgridview/page__p__45552#entry45552" rel="nofollow">less complicated solutions</a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POYii Framework: Display associated table entry through foreign key and search against it
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USTommy Bravo
UserOwnerUserId
1. USTommy Bravo
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.