StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19674292
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-10-30T05:07:37.520
FavoriteCount
0
LastActivityDate
2014-10-25T01:15:27.333
LastEditDate
2014-10-25T01:15:27.333
LastEditorUserId
445312
OwnerUserId
654016
ParentId
19569244
PostTypeId
2
Score
9
ViewCount
0
LastEditorDisplayName
text
Body
The execution thread of NSOperation depends on the <code>NSOperationQueue</code> where you added the operation. Look out this statement in your code - <pre><code>[[NSOperationQueue mainQueue] addOperation:yourOperation]; // or any other similar add method of NSOperationQueue class </code></pre> All this assumes you have not done any further threading in <code>main</code> method of <code>NSOperation</code> which is the actual monster where the work instructions you have (expected to be) written. However, in case of concurrent operations, the scenario is different. The queue may spawn a thread for each concurrent operation. Although it's not guarrantteed and it depends on system resources vs operation resource demands at that point in the system. You can control concurrency of operation queue by it's <code>maxConcurrentOperationCount</code> property. EDIT - I found your question interesting and did some analysis/logging myself. I have NSOperationQueue created on main thread like this - <pre><code>self.queueSendMessageOperation = [[[NSOperationQueue alloc] init] autorelease]; NSLog(@"Operation queue creation. current thread = %@ \n main thread = %@", [NSThread currentThread], [NSThread mainThread]); self.queueSendMessageOperation.maxConcurrentOperationCount = 1; // restrict concurrency </code></pre> And then, I went on to create an NSOperation and added it using addOperation. In the main method of this operation when i checked for current thread, <pre><code>NSLog(@"Operation obj = %@\n current thread = %@ \n main thread = %@", self, [NSThread currentThread], [NSThread mainThread]); </code></pre> it was not as main thread. And, found that current thread object is not main thread object. So, custom creation of queue on main thread (with no concurrency among its operation) doesn't necessarily mean the operations will execute serially on main thread itself.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PONSOperation and NSOperationQueue working thread vs main thread
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USPavan
UserOwnerUserId
1. USAshok
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

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.