Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

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.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3243672
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 17, 20262026-05-17T18:27:39+00:00 2026-05-17T18:27:39+00:00

I have 2 entities : User, Address. I have set the relationship each User

  • 0

I have 2 entities : User, Address.
I have set the relationship each User can have many “Address”.
I am not sure how core data works but from my understanding, every time i call insertEntityForName it creates and stores an object. (also a row in table)

So the question:
Doesn’t the following code store a duplicate address in core data?

  1. When i insert for user entity it
    also inserts an address
  2. When i call insert for address
    entity it creates another address.

If i am correct and this actually creates a duplicate in the database what is the way to prevent it?

User *user = [NSEntityDescription insertEntityForName:@"User" 
                      inManagedObjectContext:self.managedObjectContext];
user.firstName = @"first name";
user.lastName = @"last name";

Address *address = [NSEntityDescription insertEntityForName:@"Address" 
                      inManagedObjectContext:self.managedObjectContext];
address.street = @"street";
user.address = address;
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-17T18:27:40+00:00Added an answer on May 17, 2026 at 6:27 pm

    No, this will not create a duplicate address. With the first insert it only creates the User, not the Address. The user’s address will be nil.

    If you truly did make the Address relationship of the User one-to-many, you can’t assign user.address like that, it should give a warning since it’s expecting an NSSet*. Also I would recommend calling it addresses. You can do:

    user.address = [NSSet setWithObject:address];
    

    or

    [user addAddressObject:address];
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have two entities Foo and Bar with a Many to Many relationship between
I have two entities, Entity1 and Entity2, on a one to many relationship. On
I have created a user control to handle adding comments to certain business entities,
Should entities have behavior? or not? Why or why not? If not, does that
I have two entities, each from a different database and therefore different edmx files.
I have a entities as: BaseEntity --> Which contains user login info like createdBy,
When I have entities in my domain with lists of things, should they be
Say I have entities organized in a hierarchy with Parent being the root entity
I have a situation where I have two entities that share a primary key
So, I am using the Linq entity framework. I have 2 entities: Content and

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.