Re: Filters as views (ISSUE-45)

Hi Ruben

I'd disagree with you:
>> So, I struggle to see the difference between pagination and filtering.
>It is different.
>
>– Paging breaks up a resource into multiple parts,
>  which together, form the exact same resource.
>
>– Filtering results in one subset of a resource.
>
>– A filtered subset might be paged.

Consider that each element of the collection has an index - a value that is 
not directly assigned, but it's bound to that item whatever you'll do. In 
this approach paging is nothing else than a filter on that property (index). 
Actually There are some SQL implementations that are implementing paging 
that way - you create a row index and then filter it in a WHERE clause.

In previous discussion on the collections and paging mechanism I was 
stubborn enough to always relate to filtering as well as I see no difference 
between both.
Only operation on a collection that I acknowledge to behave a bit different 
is ordering.

As for the final solution taken all I care is whether all these operations 
can be combined and how the client can be told about these capabilities.

I'd like also to address also a matter of collections and views. In my 
opinion collection can be also considered it's view - unmodified/unaltered, 
but still view.

As for a filter and view - my reckoning is the former is a 'tool' to 'craft' 
the latter.

Best

Karol

Received on Tuesday, 12 January 2016 18:15:01 UTC