For the record, I thought I would post the solution to this thorny problem.
During the various checks as part of the DTS activity, I found the bug. I have
two core data models in the app, but I had not implemented
-managedObjectModel
in my NSPersistentDocument subclass and as such the
On 2013 Jun 17, at 21:13, Martin Hewitson martin.hewit...@aei.mpg.de wrote:
I did try making a mapping model (this is something I've done in the past in
other apps) but I got the same error message.
Oh, well.
Is the idea that the auto-migration magic will pick up the mapping model and
On Jun 18, 2013, at 08:08 AM, Jerry Krinock je...@ieee.org wrote:
On 2013 Jun 17, at 21:13, Martin Hewitson martin.hewit...@aei.mpg.de wrote:
I did try making a mapping model (this is something I've done in the past in
other apps) but I got the same error message.
Oh, well.
Is the
cc'ing the list this time…
On 2013-06-18, at 2:26 AM, Martin Hewitson martin.hewit...@aei.mpg.de wrote:
On Jun 18, 2013, at 08:08 AM, Jerry Krinock je...@ieee.org wrote:
On 2013 Jun 17, at 21:13, Martin Hewitson martin.hewit...@aei.mpg.de wrote:
I did try making a mapping model (this
I just had another thought I have another core data model in the app. I
wonder if the NSPersistentDocument infrastructure is picking up the wrong
model? As I'm looking through the project, I realise I don't know how the
document knows which core data model to use OK, back to the
Another question on this problem: does anyone know if
NSStoreModelVersionIdentifiers is used in looking for a source model to infer a
mapping model from?
To recap:
1) Loading an existing document with the version 11 model works
2) Adding a new version (12) with a single new boolean property on
What does your
configurePersistentStoreCoordinatorForURL:ofType:modelConfiguration:storeOptions:error:
do?
On 2013-06-18, at 5:09 AM, Martin Hewitson martin.hewit...@aei.mpg.de wrote:
Another question on this problem: does anyone know if
NSStoreModelVersionIdentifiers is used in looking for
The code is below. Anything look suspicious there?
Thanks,
Martin
- (BOOL)configurePersistentStoreCoordinatorForURL:(NSURL*)url
ofType:(NSString*)fileType
modelConfiguration:(NSString*)configuration
On Jun 18, 2013, at 05:26 PM, Dave Fernandes dave.fernan...@utoronto.ca wrote:
Looks pretty standard, but I would try commenting out the call to
setMetadataForStoreAtURL:
I'll try this and report back.
Besides that, I don't know what to suggest.
I know, it's a peculiar case. I've
Looks pretty standard, but I would try commenting out the call to
setMetadataForStoreAtURL:
Besides that, I don't know what to suggest.
On 2013-06-18, at 11:14 AM, Martin Hewitson martin.hewit...@aei.mpg.de wrote:
The code is below. Anything look suspicious there?
Thanks,
Martin
-
Are you 100% certain you set the Versioned Core Data Model current setting
to the latest model in the inspector pane on the right side of Xcode.
Have you tried doing a clean and rebuilding? I think I once had an issue where
it didn't seem to start using the new model until I did a clean build
Yes, alas, alas I have tried all of that and checked all settings, to no avail.
If I select the old model version, everything works fine (at least old
documents can be opened).
Thanks,
Martin
On 18 Jun 2013, at 19:00, davel...@mac.com wrote:
Are you 100% certain you set the Versioned Core
OK, I tried commenting out the setMetadataForStoreAtURL: part, but still it
fails.
Maybe I'm going to have to use one of my precious DTS tickets for this.
Martin
On Jun 18, 2013, at 08:32 PM, Martin Hewitson martin.hewit...@aei.mpg.de
wrote:
Yes, alas, alas I have tried all of that and
Dear list,
Something's not right with the world. I wanted to add a new boolean flag to my
NSPersistentDocument core data model. So I selected the last version (11) and
added a new version based on that (via the Editor menu). Then I carefully
selected another file and then the version 12 model
I don't see anything wrong in what you've done Martin. And I am ashamed to
admit that I have a few more version numbers than you in one of my apps.
I think the only thing I do differently is that I always create a mapping
model, whether it needs it or not. Lightweight migration has always
Hi Jerry,
I did try making a mapping model (this is something I've done in the past in
other apps) but I got the same error message. Is the idea that the
auto-migration magic will pick up the mapping model and use it, if it finds it?
Many thanks,
Martin
On Jun 17, 2013, at 10:42 PM, Jerry
On Sat, Aug 21, 2010 at 5:22 PM, Brad Gibbs bradgi...@mac.com wrote:
Well, that's the way I started doing things, but, on pages 130-131 of the
book More iPhone 3 Development (written by Dave Mark Jeff LaMarche -- your
co-authors for Learn Cocoa on the Mac) make a point of saying that the new
On Aug 22, 2010, at 04:29, Jack Nutting wrote:
On Sat, Aug 21, 2010 at 5:22 PM, Brad Gibbs bradgi...@mac.com wrote:
Well, that's the way I started doing things, but, on pages 130-131 of the
book More iPhone 3 Development (written by Dave Mark Jeff LaMarche -- your
co-authors for Learn
On Fri, Aug 20, 2010 at 8:46 PM, Brad Gibbs bradgi...@mac.com wrote:
I highlighted the .xcdatamodel and did a Design Data Model Add New
Version. That created the Config.xcdatamodeld with an unnumbered version of
the datamodel (Config.xcdatamodel) and a numbered copy named Config
Well, that's the way I started doing things, but, on pages 130-131 of the book
More iPhone 3 Development (written by Dave Mark Jeff LaMarche -- your
co-authors for Learn Cocoa on the Mac) make a point of saying that the new
version is the unnumbered version.
In some ways, I wouldn't think it
Hi Brad,
After much struggle and even writing a nightmare migrator app, I
discovered one day that the lightweight migration really does work.
In broad brush strokes here's what I did:
- Removed all the complicated migration support code that had
never worked...
- ...except the code that
On Fri, Aug 20, 2010 at 8:21 AM, Steve Steinitz
stein...@datatactics.com.au wrote:
- Removed any stray mopping models, just in case
I didn't see your question until you'd already solved it yourself, but
I just wanted to highlight this one point; Assumming you're referring
here to old .mom
I'm still having some serious issues. I've tried all suggestions from all
three responses. One or two of the suggestions worked once or twice, but
nothing worked reliably.
Is it possible that the dataModel itself is corrupt? I rebuilt it by creating
a new data model and copying all of the
On Aug 20, 2010, at 11:48, Brad Gibbs wrote:
- (NSManagedObjectModel *)managedObjectModel {
Here's what the lightweight migration documentation says:
To perform a lightweight migration, Core Data needs to be able to find the
source and destination managed object models itself at runtime.
I'm still having problems migrating to a new version of my data model. I
created a small project to test migration and everything worked smoothly -- so
smoothly that trying to get it to fail wasn't easy. But, doing the same sorts
of things to migrate to a new version of the data model in my
On Aug 19, 2010, at 14:31, Brad Gibbs wrote:
// create object for prototype model
NSString *prototypePath = [[NSBundle mainBundle]
pathForResource:@IconConfig ofType:@mom];
if (prototypePath == nil) {
prototypePath = [[NSBundle mainBundle]
26 matches
Mail list logo
