title: ListView: filtering via Filterable vs. restarting CursorLoader with new URI
body: <p>The <code>ListView</code> implements methods for filtering the content. Can you elaborate on when it should be used?</p>
  
  <p>As I understand it, that kind of filtering is suitable for the array based adapter -- all data already is in memory. This way, the filter just helps to skip the data that should not be displayed.</p>
  
  <p>However, if the <code>ListView</code> is used with a cursor adapter (SQLite database) for displayig a lot of items, the data may not be in memory. On the other hand, the filter value can be embed in the SQL query to get the reduced data set effectively.</p>
  
  <p>Was the filtering mechanism for <code>ListView</code> designed also for the cursor based data? When the <code>Filterable</code> should be used and when filter should be passed to the SQL query without using ListView filters? Are there any recommendations when this or that approach should be used?</p>
  
  <p>Thanks</p>
  
  <p>P.S. The question was separated from <a href="https://stackoverflow.com/q/18121813/1346705">How the system of URIs should be designed?</a> that combined the two earlier.</p>