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

Feedback Request: NSOperations For Importing - Thoughts? #681

Closed
JRG-Developer opened this Issue Feb 19, 2014 · 3 comments

Comments

Projects
None yet
3 participants
Contributor

JRG-Developer commented Feb 19, 2014

@casademora @blackgold9 @tonyarnold

I'm working on a project where data import can take a bit of time due to several related (child) objects that need to be imported together.

Unfortunately, the data set is large and fairly dynamic, so it's not very feasible to sync the whole thing with the device. Data import is also driven by user selection; a user wants to see his selection immediately after making it.

I'm considering adding new methods to MagicalRecord that would return an NSOperation - similar in design to how AFNetworking's AFHTTPRequestOperationManager returns an operation - for importing.

This way, the import operations could be (1) queueable and (2) cancelable.

Thoughts ?

Would this be useful to the main repo or is this a relatively uncommon situation (slow import due to occasional heavy data source objects) ?

That is, would this type of feature have a chance of getting into the main repo?

Contributor

JRG-Developer commented Mar 18, 2014

Closing due to lack of interest.

Contributor

tonyarnold commented Mar 18, 2014

I actually really like the idea, Joshua. I think it's an uncommon scenario, but I've certainly seen this enough times to have wanted it. If you're keen, go for it — but it would be best if you targeted your changes to MagicalRecord 3.0 — in the release/3.0 branch.

Alydyn commented Mar 19, 2014

I would also like to see this!

On Tue, Mar 18, 2014 at 6:00 PM, Tony Arnold notifications@github.comwrote:

I actually really like the idea, Joshua. I think it's an uncommon
scenario, but I've certainly seen this enough times to have wanted it. If
you're keen, go for it -- but it would be best if you targeted your changes
to MagicalRecord 3.0 -- in the release/3.0 branch.

Reply to this email directly or view it on GitHubhttps://github.com/magicalpanda/MagicalRecord/issues/681#issuecomment-37999659
.

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