Note that there are some explanatory texts on larger screens.

plurals
  1. POBest practice in recreating CoreData entities with actual data retrieved from the server
    primarykey
    data
    text
    <p>Purpose: I have to create entities from files.</p> <p>So entities represent my data model in CoreData and files have all information for this entities.</p> <p>All files I get from Internet. For this I use AFNetworking framework.</p> <p>How I get files (algorithm):</p> <ol> <li>Request plist file. Plist file has values to other urls that I have to download.</li> <li>When plist was downloaded to my Documents directory on device. I parse it.</li> <li>When I parse plist I grab url from each item from NSDictionary that represent this plist.</li> <li>Then I request zip files from this urls.</li> <li>After zip files were downloaded I unzip them and go to the next step.</li> <li>Parse unzipped files and create data model.</li> </ol> <p>It is my problem. I have version of file that stored locally and that stored on the server and when version on the server changed I need to reload my data model with actual data. The bad way it is load all data from server again next delete all entities in storage and make new entities from new data. But it is not professional way at first and second it is an additional burden on the traffic, because if I have just one entity that I need to reload why I have to reload other entities that are in the actual state. So maybe someone knows best practice with this question. Of course I can create my solution and it will work, but I want to see how people solve this problem and figure out with the differences in my solution and in the other solutions also.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

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