Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Core Data is worth using in every scenario you described. In fact, if an app stores more than preferences, you should probably use Core Data. Here are some reasons, among which, you'll find answers to your own problems:</p> <ul> <li>is definitely faster than the filesystem, even if you wipe out everything and write it again as you describe (so you don't benefit to much from caching). This is basically because you can coalesce your operations and only access the store when needed. So if you read, write and read, you can save only once, the rest is done in memory, which is, needless to say, very fast.</li> <li>everything is versioned and you can migrate from one version to another easily (while keeping the content the user has on the device)</li> <li>80% of your model operations come free. Like, when something changes, you can override the <code>willSave</code> managed object method and notify your controllers.</li> <li>using <code>cascade</code> makes it trivial to delete even very complex object structures</li> <li>while is a bad idea to keep images in the database, you can still keep them on the filesystem and have core data delete them automatically when the managed object that represents them is deleted</li> <li>is flexible, in fact is so flexible that you could migrate your project from using the local filesystem to using a server with very little modifications by writing a custom data store.</li> <li>the core data designer basically creates the model objects for you. You don't need to create your own model classes (which you would have to if using the filesystem)</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POCore Data vs NSFileManager
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USValentin Radu
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCore Data vs NSFileManager
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COthe cache is more for offline scenarios. So in normal conditions with internet access, I normally replace the stored data very frequently, that's why I had concerns. Another advantage, is the fact of just using an `NSDictionary` and not having the need to know what's inside of him (how he is composed). Would it make sense to have `NSManagedObject` with only a `NSDictionary`?
      singulars
      1. PO
      1. USPeres
    2. COThe cache is important for local filesystem as well. The filesystem access is way slower than memory access. I'm not sure why you don't have the need to know what's inside that dictionary, don't you read/interpret it as some point. If you only store a file like any other, which happens to be a serialized dictionary, then yes, there's no point in using Core Data
      singulars
      1. PO
      1. USValentin Radu
    3. COI mean, I Know what's inside, but if for some reason an API changes, and add different things, I am not constrained to that.
      singulars
      1. PO
      1. USPeres
 

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.

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