NsPerstentContainer name in Appdelegate conventions in Core Data setup
I'm programming my fist SwiftApp got stuck setting up Core data. Since I'm integrating it into existing code I can't have Xcode set it up on Prohect init anymore. Furthermore I als want to understand what the lines of code actually do. Since all Core libraries are secret I am stuck with Apple's Docs which are not very clear on the matter.
Pfew... with that out of the way here is the question; What is the significance of the name passed to...
let container = NSPersistentContainer(name: "Core_Data")
...in the App Delegate file. I had set it up before but during compilation Xcode complained that it could not find the specified Name's module. Changing it to my project's name, the core data file I had created or the name of the Database passed to the menu when adding a Core Data file did not seem to help at all. Searching the web and a few tutorials people just fly over it and it is still very much unclear to me.
Any help would be much appreciated!
swift core-data
asked Nov 25 '18 at 16:10
Arne OldenhaveArne Oldenhave
175
add a comment |
I'm programming my fist SwiftApp got stuck setting up Core data. Since I'm integrating it into existing code I can't have Xcode set it up on Prohect init anymore. Furthermore I als want to understand what the lines of code actually do. Since all Core libraries are secret I am stuck with Apple's Docs which are not very clear on the matter.
Pfew... with that out of the way here is the question; What is the significance of the name passed to...
let container = NSPersistentContainer(name: "Core_Data")
...in the App Delegate file. I had set it up before but during compilation Xcode complained that it could not find the specified Name's module. Changing it to my project's name, the core data file I had created or the name of the Database passed to the menu when adding a Core Data file did not seem to help at all. Searching the web and a few tutorials people just fly over it and it is still very much unclear to me.
Any help would be much appreciated!
swift core-data
asked Nov 25 '18 at 16:10
Arne OldenhaveArne Oldenhave
175
add a comment |
I'm programming my fist SwiftApp got stuck setting up Core data. Since I'm integrating it into existing code I can't have Xcode set it up on Prohect init anymore. Furthermore I als want to understand what the lines of code actually do. Since all Core libraries are secret I am stuck with Apple's Docs which are not very clear on the matter.
Pfew... with that out of the way here is the question; What is the significance of the name passed to...
let container = NSPersistentContainer(name: "Core_Data")
...in the App Delegate file. I had set it up before but during compilation Xcode complained that it could not find the specified Name's module. Changing it to my project's name, the core data file I had created or the name of the Database passed to the menu when adding a Core Data file did not seem to help at all. Searching the web and a few tutorials people just fly over it and it is still very much unclear to me.
Any help would be much appreciated!
swift core-data
asked Nov 25 '18 at 16:10
Arne OldenhaveArne Oldenhave
175
I'm programming my fist SwiftApp got stuck setting up Core data. Since I'm integrating it into existing code I can't have Xcode set it up on Prohect init anymore. Furthermore I als want to understand what the lines of code actually do. Since all Core libraries are secret I am stuck with Apple's Docs which are not very clear on the matter.
Pfew... with that out of the way here is the question; What is the significance of the name passed to...
let container = NSPersistentContainer(name: "Core_Data")
...in the App Delegate file. I had set it up before but during compilation Xcode complained that it could not find the specified Name's module. Changing it to my project's name, the core data file I had created or the name of the Database passed to the menu when adding a Core Data file did not seem to help at all. Searching the web and a few tutorials people just fly over it and it is still very much unclear to me.
Any help would be much appreciated!
swift core-data
swift core-data
asked Nov 25 '18 at 16:10
Arne OldenhaveArne Oldenhave
175
asked Nov 25 '18 at 16:10
Arne OldenhaveArne Oldenhave
175
asked Nov 25 '18 at 16:10
Arne OldenhaveArne Oldenhave
175
asked Nov 25 '18 at 16:10
Arne OldenhaveArne Oldenhave
175
asked Nov 25 '18 at 16:10
Arne OldenhaveArne Oldenhave
175
175
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The string passed there is used for two things. If you were to pass the string Foo, Core Data would attempt:
- To find the data model by looking for
Foo.xcdatamodelorFoo.xcdatamodeld. - To find (or create) the persistent store, using the name
Foo.sqlite.
Even an incorrect string value (i.e. one that doesn't match the name of your data model) should not cause a compilation error. It might cause an error at run time if iOS can't find the named data model.
answered Nov 27 '18 at 0:02
Tom HarringtonTom Harrington
53.6k5104131
Thank you very much for the clear explanation. It turned out I had forgotten to set the Class Module!
– Arne Oldenhave
Nov 27 '18 at 14:57
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%2f53469349%2fnsperstentcontainer-name-in-appdelegate-conventions-in-core-data-setup%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
The string passed there is used for two things. If you were to pass the string Foo, Core Data would attempt:
- To find the data model by looking for
Foo.xcdatamodelorFoo.xcdatamodeld. - To find (or create) the persistent store, using the name
Foo.sqlite.
Even an incorrect string value (i.e. one that doesn't match the name of your data model) should not cause a compilation error. It might cause an error at run time if iOS can't find the named data model.
answered Nov 27 '18 at 0:02
Tom HarringtonTom Harrington
53.6k5104131
Thank you very much for the clear explanation. It turned out I had forgotten to set the Class Module!
– Arne Oldenhave
Nov 27 '18 at 14:57
add a comment |
The string passed there is used for two things. If you were to pass the string Foo, Core Data would attempt:
- To find the data model by looking for
Foo.xcdatamodelorFoo.xcdatamodeld. - To find (or create) the persistent store, using the name
Foo.sqlite.
Even an incorrect string value (i.e. one that doesn't match the name of your data model) should not cause a compilation error. It might cause an error at run time if iOS can't find the named data model.
answered Nov 27 '18 at 0:02
Tom HarringtonTom Harrington
53.6k5104131
Thank you very much for the clear explanation. It turned out I had forgotten to set the Class Module!
– Arne Oldenhave
Nov 27 '18 at 14:57
add a comment |
The string passed there is used for two things. If you were to pass the string Foo, Core Data would attempt:
- To find the data model by looking for
Foo.xcdatamodelorFoo.xcdatamodeld. - To find (or create) the persistent store, using the name
Foo.sqlite.
Even an incorrect string value (i.e. one that doesn't match the name of your data model) should not cause a compilation error. It might cause an error at run time if iOS can't find the named data model.
answered Nov 27 '18 at 0:02
Tom HarringtonTom Harrington
53.6k5104131
The string passed there is used for two things. If you were to pass the string Foo, Core Data would attempt:
- To find the data model by looking for
Foo.xcdatamodelorFoo.xcdatamodeld. - To find (or create) the persistent store, using the name
Foo.sqlite.
Even an incorrect string value (i.e. one that doesn't match the name of your data model) should not cause a compilation error. It might cause an error at run time if iOS can't find the named data model.
answered Nov 27 '18 at 0:02
Tom HarringtonTom Harrington
53.6k5104131
answered Nov 27 '18 at 0:02
Tom HarringtonTom Harrington
53.6k5104131
answered Nov 27 '18 at 0:02
Tom HarringtonTom Harrington
53.6k5104131
answered Nov 27 '18 at 0:02
Tom HarringtonTom Harrington
53.6k5104131
53.6k5104131
Thank you very much for the clear explanation. It turned out I had forgotten to set the Class Module!
– Arne Oldenhave
Nov 27 '18 at 14:57
add a comment |
Thank you very much for the clear explanation. It turned out I had forgotten to set the Class Module!
– Arne Oldenhave
Nov 27 '18 at 14:57
Thank you very much for the clear explanation. It turned out I had forgotten to set the Class Module!
– Arne Oldenhave
Nov 27 '18 at 14:57
Thank you very much for the clear explanation. It turned out I had forgotten to set the Class Module!
– Arne Oldenhave
Nov 27 '18 at 14:57
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%2f53469349%2fnsperstentcontainer-name-in-appdelegate-conventions-in-core-data-setup%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
