Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Why does Apples Core Data iPhone Recipes Example use a separate entity for called Image linked to the Recipe Entity via a one to one Relationship to store the recipes image. Why not just have an “image” attribute in the Recipe Entity?
Many Thanks
They could. But it’s an efficiency thing. If image is a large blob, then to save on excessively slow fetches from Recipe, it’s simplest to create a separate table for each blob property.