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.
Currently I need to set up a database that uses the following structure.
My first thought was to create 3 entities, one for “Item”, “Object”, and “Stuff”, then have an array in each.
So each “Item” would have an array containing the “objects”, and each object with an array of “stuff.”
Would this be a good approach? If not, what would be a more correct and efficient way of accomplishing the same task?
In theese situations, when you have 2 entities and you want to have a relation between them, you should try out CoreData’s relationships. In this case you should use to-many relationship.
PS: Don’t forget to select your relationship delete rule! 🙂