Databases
StackOverflow2013
Postsdbo
PONSThread vs. NSOperationQueue vs. ??? on the iPhone
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PONSThread vs. NSOperationQueue vs. ??? on the iPhone
    primarykey
    data
    text
    <p>Currently I'm using <code>NSThread</code> to cache images in another thread.</p> <pre><code>[NSThread detachNewThreadSelector:@selector(cacheImage:) toTarget:self withObject:image]; </code></pre> <p>Alternately:</p> <pre><code>[self performSelectorInBackground:@selector(cacheImage:) withObject:image]; </code></pre> <p>Alternately, I can use an <code>NSOperationQueue</code> </p> <pre><code>NSInvocationOperation *invOperation = [[NSInvocationOperation alloc] initWithTarget:self selector:@selector(cacheImage:) object:image]; NSOperationQueue *opQueue = [[NSOperationQueue alloc] init]; [opQueue addOperation:invOperation]; </code></pre> <p>Is there any reason to switch away from <code>NSThread</code>? GCD is a 4th option when it's released for the iPhone, but unless there's a significant performance gain, I'd rather stick with methods that work in most platforms.</p> <hr> <p>Based on @Jon-Eric's advice, I went with an <code>NSOperationQueue</code>/<code>NSOperation</code> subclass solution. It works very well. The <code>NSOperation</code> class is flexible enough that you can use it with invocations, blocks or custom subclasses, depending on your needs. No matter how you create your <code>NSOperation</code> you can just throw it into an operation queue when you are ready to run it. The operations are designed to work as either objects you put into a queue or you can run them as standalone asynchronous methods, if you want. Since you can easily run your custom operation methods synchronously, testing is trivially easy.</p> <p>I've used this same technique in a handful of projects since I asked this question and I couldn't be happier with the way it keeps my code and my tests clean, organized and happily asynchronous.</p> <p>A++++++++++ Would subclass again</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USkubi
    1. USkubi
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PONSThread vs. NSOperationQueue vs. ??? on the iPhone
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PONSThread vs. NSOperationQueue vs. ??? on the iPhone
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PONSThread vs. NSOperationQueue vs. ??? on the iPhone
      1. USraaz
      1. VTFavorite
    1. COYou could profile each of them. That would be one way to find out.
      singulars
      1. PONSThread vs. NSOperationQueue vs. ??? on the iPhone
      1. USAlex Reynolds
    2. COPerformance was the wrong word, I suspect they're all the same underneath. I'm more looking for someone who has experience with two or more of these methods to give me some advice on the preferred way and why it's better.
      singulars
      1. PONSThread vs. NSOperationQueue vs. ??? on the iPhone
      1. USkubi
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload