Saving images in Core Data for use in UITableView
===

I planning on building an app whose main content are images. Basically, it is going to have multiple menus using `UITableViews`, whose cells are going to have only an image. When you click the cell, you'll be pushed to a simple view with that image and another one, wich has the rest of the detailed content.

This is all quite easy to do, my questions is about optimization. It's gonna have LOTs of content (Maybe 1k rows) and It's gonna display images in the `UITableView`, so Core Data is a must (given it's lazy loading and several other optimizations) 

My question is: What's best, to store the image in the `Core Data` db (as `NSData`) or to just store the name of the image? What I'm imagining is if I store the name of the resource, For each row in the `UITableView` the device must go fetch that image, process it finally display it. When scrolling trough them (wich is expected to happen A LOT) we would have lots of fetching images. If I store them in `Core Data`, it would be as simple as taking that info and using it as if it where an image.

The benefits of storing the images in `Core Data` comes with the normal withdraws of storing blobs in a db. I don't know how much of a problem this would be in Core Data (My experience in dbs comes mainly from MySQL)

On the other hand, tough my "common sense" dictates saving just the name and fetching the images as they're needed its gonna take more time if they're requested more, I'm not sure how much of a performance hit would this be. Is there a "best way" to store them? Just the name and then call `pathForResourse:ofType:`or (if it's faster) `pathForResourse:ofType:inDirectory:` on the `mainBundle`, store the URI, or other form of pointing to it.


