Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Set localContext to be the same as threadContext when saveDataInBackgroundWithBlock: #122

Closed
wants to merge 9 commits into
from

Conversation

Projects
None yet
2 participants
Contributor

tonyxiao commented Dec 29, 2011

There is a subtle bug when calling saveDataInBackgroundWithBlock:. The localContext passed to the block is not the same context as the context for the thread. So when calling [NSManagedObjectContext contextForCurrentThread] two contexts actually get created. I added MR_setContextForCurrentThread: to the API and called it before passing localContest to block to fix this issue.

Also updated README.md

Contributor

tonyxiao commented Feb 6, 2012

There's a bug in detecting private queue isolation mode on mac, which is available in 10.7 in addition to iOS 5.

Contributor

tonyxiao commented Feb 13, 2012

just merged in all the upstream changes and fixed another bug. please review and see if you think it's appropriate for merging

Member

blackgold9 commented Sep 10, 2012

Currently we create a child context of the main context, work there in the background, and then save. The caller doesn't have to worry about where the context came from.

@blackgold9 blackgold9 closed this Sep 10, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment