There must be somewhere on this site that has this explanation but I just can't seem to find it. I hope someone can point me to the right direction.
What is the advantages of using QueryableCollectionView vs say, ObservableCollection?
3 Answers, 1 is accepted
0
Vlad
Telerik team
answered on 28 May 2012, 06:56 AM
Hello,
With our QueryableCollectionView you have built-in support for filtering, grouping, sorting, aggregates and many more not supported in plain ObservableCollection. Furthermore the collection is ICollectionView (currency support), IEditableCollectionView (edit/update/cancel), IPagedCollectionView (paging) and the biggest advantage - IQueryable. If you provide IQueryable for QueryableCollectionView all operations will be executed directly on your data-base server using the query provider. Of course in Silverlight this is not verry common case (you have very few options for real IQueryable) however in WPF this can be very convenient.
Greetings,
Vlad
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>
The QueryableCollectionView constructor only takes an IEnumerable source parameter so how would it be used with an IQueryable source? Can you provide an example of this?