relatedsearchbehavior Follow @yiiframework

Please check the forum for the continuation of the discussion.

@le_top Thanks for taking time to reply , actually that's what i was planning to do but i thought maybe somebody faced the same issue ..anyway i found out that the the three order by clauses in the query (the outer and inner data sets query)that pick up the data are missing and i have no idea why ...

Hi In the demo the pagination behavior looks normal to me (using sqlite) and also on a production site (using mysql). This may have something to do with your gridview wrapper. I suggest that you check out the demo and "migrate" it to your bootstrap wrapper (using a new view). I think that this will help discover where the issue may be. Also check the SQL searches/requests made (using tbdebug extension for instance).

thanks for this great extension..

i wanted to know if anybody facing issues with pagination where the data rows stay the same if you search using one of the related fields or sort by one of them and i noticed also that the indicators of the current page are changing but the data staying the same

everything works normally if i search using the fields of the same model i'm using crisu bootstrap grid and

appreciate any help

Follow a request on the forum, I added multi-attribute defaultOrder support. So now the default order can be like this:

'sort'=>array('defaultOrder'=>'Artist DESC,TrackName ASC'),

where Artist and TrackName correspond to virtual attributes referring to fields in related tables (Related Search Behavior updates the defaultOrder as needed).

@zvik2004: I see that you are developing a relation as a keen user ;-).

I have added the partialMatch code (slightly differently), and 'autoScope' a feature that I started using myself.

Hi

In your search, you use partialMatch=true. I think it will be great to get it as a parameter. I modified my code, please let me know what you think:

The configuration can be something like:

'fieldxyz'  => array(
    'field'         => 'table.field',
    'partialMatch'  => false,
),

And in the RelatedSearchBehavior file (in the appropriate places):

if(is_array($relationvar)) {
    $relationfield=$relationvar['field'];
    $search_value = isset($relationvar['searchvalue']) ? $this->getOwner()->{$relationvar['searchvalue']} : $this->getOwner()->{$var};;
    $partialMatch = isset($relationvar['partialMatch']) ? $relationvar['partialMatch'] : true;
} else {
    $relationfield=$relationvar;
    $search_value=$this->getOwner()->{$var};
    $partialMatch = true;
}
 
//and the search part:
$criteria->compare($column,$search_value,$partialMatch);

Thanks!

Zvi.

Please check the Forum regarding a potential new feature to automatically add scopes for attributes.

Hi Just one field because of the work (writing/testing) involved. Ideally, the code would accept multifield ordering in a single string specification or in an array specification. I am happy to integrate any full code.

Hi, thanks for extending your extension to work also with the default sort. Perfect. Just for curiosity: Why only for one field? Is this getting too complex otherwise? Don't get me wrong, I am totally happy with this, but I can think of cases where I need to do this for more than one field.

gb

Hi I extended the extension so that you can define 1 related field for the defaultOrder. I have updated the demo (Invoiceline.php) to sort on 'Artist DESC' which is a related field.

Thanks for providing this extension. Works very well. I right now want to do a sort on one of the related records. So to follow your example, this does not work for me:

$sort=array(
    'defaultOrder'=>'serial ASC',
);
return $this->relatedSearch(
    $criteria,
    array('sort'=>$sort)
);

Is there any work around for this? Thanks again, gb

Hi The demo has no drop-down filters - it has the default filter function for gridviews - you fill in text. Using drop-downs for filtering is a different feature - I'll see where this is suitable to add.

I probably modified the KeenActiveDataProvider to improve it. I think I submitted my improvements, but not sure of it.

can you show example, how to setup it? I can`t understand how it works. demo has no dropdown filter.

ps your behavior not work with KeenActiveDataProvider.php from github, only work from demo.

The demo is available on line under 'Live demo' and you can download the demo too. That is not ok for you?

Hi...

demo please :)

I updated the demo to use the Chinook Demo Database which is an open source database with a schema and data that is easy to understand.

It is a better demonstration of how easy it is to get a fully searcheable and sortable table.

Searching for 'jane' and sorting by email results in the following SQL query using 3 joins with very limited effort to achieve it.

SELECT COUNT(DISTINCT 't'."InvoiceLineId") FROM 'invoiceline' 't'  LEFT OUTER JOIN 'track' 'track' ON ('track'."TrackId"='t'."TrackId")  LEFT OUTER JOIN 'invoice' 'invoice' ON ('invoice'."InvoiceId"='t'."InvoiceId")  LEFT OUTER JOIN 'customer' 'customer' ON ('customer'."CustomerId"='invoice'."CustomerId")  LEFT OUTER JOIN 'employee' 'support' ON ('support'."EmployeeId"='customer'."SupportRepId")  WHERE (support.Email LIKE :ycp0)

Also, by using the KeenDataProvider there is just one extra SQL request to get all the related data from the database.

Thanks for the feedback. I was certain that I was going to have some good suggestions to further improve this.

1. I forgot to update the documentation. After adding the getter/setter implementation to the behavior I realised that the behavior could not be added on the fly and that the relations had to be known also to the data model instances. Which is actually a good thing because this make adding aliases to data fields in related models quite easy.

2. Good suggestion - which is why '$options' is an array. To make it as generic as possible, the extension now passes on all the keys provided in '$options' to the DataProvider (while updating the 'sort' value).

There is also a fix for the 'searchvalue' functionality (which needs an example).

[Updates are in 1.02]

I have 2 comments:

• In the example in this page, you specify:

return 
  $this->relatedSearch(
    $criteria,
    $relationsearch,
    array('sort'=>$sort)
  );

But the parameter: $relationsearch shouldn't be there.

• There is no pagination handling (both in the code and in the examples); So for example, it will be nice to mention it in the example:

return 
  $this->relatedSearch(
    $criteria,
    array('sort'=>$sort, 'pagination'=>array('pageSize'=>10))
  );

And in your class: RelatedSearchBehavior, the method should be changed (this is the code that I used, but it's only example):

return new KeenActiveDataProvider($this->getOwner(), array(
                'pagination'=>(isset($options['pagination']) ? $options['pagination'] : null),
                'criteria'=>$criteria,
                'sort'=>$sort,
        ));

Thanks!

Zvi.

I just updated this extension so that the behavior itself takes care of the getter and setters for the search field. This helped me reduce the code in my own project a lot.

I hope that you'll enjoy this extension as much as I do.