Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Saving Images with Core Data (i.e., JPEG, TIFF, etc.)



On Apr 29, 2005, at 2:37 PM, mmalcolm crawford wrote:

For example, if a Person entity should have a 'photo' attribute, then create a Photo entity with just a single attribute -- the data -- and if you care a relationship back to the Person (typically modeling relationships in both directions is a Good Thing). Then create a relationship from the Person to the Photo entity. This will mean that photo data is only loaded from the persistent store if you actually use it.

Is this true in general (or at least for SQLite stores)? Relationships are loaded on demand, but attributes are loaded when the object is? Is there any situation where attributes will be lazily loaded, or is the concept of faulting only for entities? I'm thinking of an example of an object that has


ObjectEntity
    name
    date
    comments

It is being displayed in a table view, but the table view only has columns for name and date, for example.

Jim
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden

This email sent to email@hidden
References: 
 >Saving Images with Core Data (i.e., JPEG, TIFF, etc.) (From: Marc Blatt <email@hidden>)
 >Re: Saving Images with Core Data (i.e., JPEG, TIFF, etc.) (From: mmalcolm crawford <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.