How is maximum count for a Core Data relationship enforced?
I have a User
entity that has a to-many
relationship to Location
entities. I have it set the relationship to be ordered with a maxCount
of 50. When I create new Location
entities and set them to users, does Core Data automatically delete the old entities. Do I have to check if the new size will be greater than 50
and manually delete the old Location
entity so I don't have a dangling object that I don't need anymore. I have the delete rule set to Cascade
.
The description of NSRelationshipDescription.maxCount
is just The maximum count of the receiver.
and I don't see anything describing how minCount/maxCount
works.
Any insight to the behavior of this is appreciated. Thanks!
ios objective-c swift core-data
add a comment |
I have a User
entity that has a to-many
relationship to Location
entities. I have it set the relationship to be ordered with a maxCount
of 50. When I create new Location
entities and set them to users, does Core Data automatically delete the old entities. Do I have to check if the new size will be greater than 50
and manually delete the old Location
entity so I don't have a dangling object that I don't need anymore. I have the delete rule set to Cascade
.
The description of NSRelationshipDescription.maxCount
is just The maximum count of the receiver.
and I don't see anything describing how minCount/maxCount
works.
Any insight to the behavior of this is appreciated. Thanks!
ios objective-c swift core-data
add a comment |
I have a User
entity that has a to-many
relationship to Location
entities. I have it set the relationship to be ordered with a maxCount
of 50. When I create new Location
entities and set them to users, does Core Data automatically delete the old entities. Do I have to check if the new size will be greater than 50
and manually delete the old Location
entity so I don't have a dangling object that I don't need anymore. I have the delete rule set to Cascade
.
The description of NSRelationshipDescription.maxCount
is just The maximum count of the receiver.
and I don't see anything describing how minCount/maxCount
works.
Any insight to the behavior of this is appreciated. Thanks!
ios objective-c swift core-data
I have a User
entity that has a to-many
relationship to Location
entities. I have it set the relationship to be ordered with a maxCount
of 50. When I create new Location
entities and set them to users, does Core Data automatically delete the old entities. Do I have to check if the new size will be greater than 50
and manually delete the old Location
entity so I don't have a dangling object that I don't need anymore. I have the delete rule set to Cascade
.
The description of NSRelationshipDescription.maxCount
is just The maximum count of the receiver.
and I don't see anything describing how minCount/maxCount
works.
Any insight to the behavior of this is appreciated. Thanks!
ios objective-c swift core-data
ios objective-c swift core-data
asked Nov 19 '18 at 4:16
Dhananjay SureshDhananjay Suresh
35111
35111
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
CoreData will not automatically delete anything, it will just fail to save the context if the current state is breaking the maxCount rule.
So it is up to you to decide what needs to be deleted and clean up before trying to save.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53368233%2fhow-is-maximum-count-for-a-core-data-relationship-enforced%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
CoreData will not automatically delete anything, it will just fail to save the context if the current state is breaking the maxCount rule.
So it is up to you to decide what needs to be deleted and clean up before trying to save.
add a comment |
CoreData will not automatically delete anything, it will just fail to save the context if the current state is breaking the maxCount rule.
So it is up to you to decide what needs to be deleted and clean up before trying to save.
add a comment |
CoreData will not automatically delete anything, it will just fail to save the context if the current state is breaking the maxCount rule.
So it is up to you to decide what needs to be deleted and clean up before trying to save.
CoreData will not automatically delete anything, it will just fail to save the context if the current state is breaking the maxCount rule.
So it is up to you to decide what needs to be deleted and clean up before trying to save.
answered Nov 19 '18 at 6:35
trappertrapper
7,33452463
7,33452463
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53368233%2fhow-is-maximum-count-for-a-core-data-relationship-enforced%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown