title: When should I do certain SQLite operations on another thread(not the main thread)?
body: <p>My Android application includes an SQLite database with an <code>SQLiteOpenHelper</code> class to help manage it.  During application use, the user may perform some operations such as adding/deleting/updating etc on the database.  </p>
  
  <p>At some points the size of the operation will be known, like this:</p>
  
  <ol>
  <li>user clicks button to save item</li>
  <li>the <code>SQLiteDatabase</code> performs a single <code>insert</code> query</li>
  <li>user continues using app</li>
  </ol>
  
  <p>At other areas of the app, the operation may be large, like inserting 10+ items into the database all at once.</p>
  
  <p>Questions: </p>
  
  <ul>
  <li>should I thread simple operations like inserting/updating/deleting/viewing 1 item?</li>
  <li>will it take longer to insert 1 item into a table which contains many items(like 30+) than it would take to insert into a table with no items?</li>
  <li>if i don't need to thread such simple operations, at what point do you suggest i <strong>start</strong> threading them?</li>
  </ul>
  
  <p>when i say <strong>thread</strong> i mean using a thread that is not the main UI thread.</p>
  
  <p>edit: I realize that small operations do not take much time and i could very well get away with doing them on the main thread. I am just concerned that it would be bad practice to be executing them on the main thread and would like clarification!</p>