objective c - NSManagedObject as store with continuous analysis of raw data -


This is similar to the question I asked earlier, but now when I come forward a lot, I still have the question NSManagedObject As the "proper" sub-classification of I was told last night that this is a very non-permanent property and Ivar is placed inside one. Currently I have tons of code inside the NSMANGE object, and Apple's docs do not actually address that "right". FYI: Code works, but I'm asking if there are further losses, or else it There is obvious improvement to the other way.

My "object" is an increasing array of incoming data, properties / iwar which track the progress of data analysis, and processed data (output) all stored in memory because it is too large , It grows very fast, and it will not be possible to re-generate / re-analyze the fact that the NSManagedObject properties are only the original data (regularly saved, the core data is NSMUtableData Does not support), some basic properties and other two relationships Ansmanedobjekt (1 user of the second set of a snapshot statistics). Only one object is being recorded at any time, although dozens can be opened to look at (which can at any time incorporate further process).

There are all processing logic / variables in the unit (the data manager who manages the core data), because each object requires at least a handful of arrays / properties, which are the form of intermediaries Are used in and track values ​​for analysis. And I personally think that it seems silly to create two objects for each object (the NSMANED object that stores, and another object that is a processing / temporary store).

In fact, all the examples I can find using NSManagedObjects are super simple objects, such as coordinates, address book entries, pictures: the things which are basically constant, I can see all the arguments Which makes / modifies them outside the object However, my case is not easy and I still need to come up with an option in which repetition is not included.

Any suggestion would be appreciated.

You can use an 'wrapper', which is one of your managed object instances A class with reference is going to say, in this wrapper your algorithm and your non-working algorithm

Comments

Popular posts from this blog

excel vba - How to delete Solver(SOLVER.XLAM) code -

github - Teamcity & Git - PR merge builds - anyway to get HEAD commit hash? -

ios - Replace text in UITextView run slowly -