title: Core data multithreading with children contexts
body: <p>I have just began learning Core data. When it comes to multithreading, some blogs say that in this case we should use children contexts (by creating a context and setting its parent) and just invoke the performBlock: method. However some other blogs say that we should avoid this approach since it has introduced many bugs.
  I have just began developing an application that manipulates a large data base and the project manager voted for Core data (instead of SQLLite).
  Could any one please give me some directions. Should i use the children contexts strategy (introduced since iOS 5) or is there a better way to perform multithreading with Core Data ?
  Thanks.</p>