I've run into an issue that I haven't seen before with our mapping models: If
the filter predicate was set, and is then cleared, migration complains about
the empty filter predicate with:
NSInvalidArgumentException: Unable to parse the format string ""
I'm having to hand-edit the mappin
, 26 Feb 2015 17:00:49 -0800, Rick Mann said:
>
>> A problem I run into a lot with automatic migration using a Mapping
>> Model is that I'm usually in the process of making incremental changes
>> to my schema. So I create a Mapping Model, modify it as necessary, and
>>
Oh, maybe. I'll try that next time (I already blew away and re-created the
file).
Thanks!
> On Feb 26, 2015, at 17:09 , Sean McBride wrote:
>
> On Thu, 26 Feb 2015 17:00:49 -0800, Rick Mann said:
>
>> A problem I run into a lot with automatic migration using a Mappi
On Thu, 26 Feb 2015 17:00:49 -0800, Rick Mann said:
>A problem I run into a lot with automatic migration using a Mapping
>Model is that I'm usually in the process of making incremental changes
>to my schema. So I create a Mapping Model, modify it as necessary, and
>things are fin
A problem I run into a lot with automatic migration using a Mapping Model is
that I'm usually in the process of making incremental changes to my schema. So
I create a Mapping Model, modify it as necessary, and things are fine.
But then if I change the schema again, that Mapping Model i
. I honestly don't know
if I set these values or if Xcode did that for me. At any rate, setting the
minimum count back to "1" seemed to make the mapping model recognized by Core
Data.
I hope this helps you.
John
On Jan 22, 2013, at 12:12 PM, Sean McBride wrote:
> On Thu,
On Thu, 17 Jan 2013 21:45:51 -0500, John Brayton said:
>I am building a mapping model between two versions of my Core Data
>model, and I am encountering a strange issue:
>
>* If I define six of the seven entity mappings I need in the mapping
>model, migrating the data works as expe
Hi,
I am building a mapping model between two versions of my Core Data model, and I
am encountering a strange issue:
* If I define six of the seven entity mappings I need in the mapping model,
migrating the data works as expected.
* When I add the seventh entity mapping, the migration fails
I needed to create a Core Data Mapping Model today. The only value migration
necessary was to negate a boolean. It seems like one should be able to enter
such a simple expression into the "Value Expression" column of "Attribute
Mappings". Reading the Predicate Programmin
On Aug 8, 2011, at 06:24 PM, Sean McBride wrote:
> On Sun, 7 Aug 2011 07:39:25 +0200, Martin Hewitson said:
>
>> Is there a know problem or limitation in naming relationships? I haven't
>> come across this anywhere before.
>
> Well, you should not name properties with the same name as an NSObje
On Sun, 7 Aug 2011 07:39:25 +0200, Martin Hewitson said:
>Is there a know problem or limitation in naming relationships? I haven't
>come across this anywhere before.
Well, you should not name properties with the same name as an NSObject or
NSMangedObject method name. ex: don't create a property
(Cc'd cocoa mailing list because this turns out to be relevant to those working
with core data.)
This turns out to be much more sinister than I'd thought.
The mapping model seems to be a red herring and the problem of having nil'ed
out inherited attributes is not to do with th
Hi Amy,
It might be helpful if you could post an extract from your mapping method, or
the whole thing if it's short. The last time I had a problem of this kind it
turned out I had made a stupid error which only became obvious after I had left
the problem for a week and then returned to it with
I've got a data model that I want to add an attribute to (as in adding
an attribute to an entity). The attribute is optional and can begin
with a nil value.
I've created a mapping model and it opens the old file, but I've got
odd behaviour.
The entity is called manufact
On Tue, Sep 7, 2010 at 3:55 PM, Kyle Sluder wrote:
> Since all you're doing is adding methods, +load might be an okay time
> to do things, except if the method you're replacing comes from a
> category. You might want to defer to +initialize instead.
For the record, this is still risky business. A
On Tue, Sep 7, 2010 at 3:41 PM, Jerry Krinock wrote:
> Messy. I added a +load method to the NSMigrationManger category that I
> added, and invoked the patch in there. Seems to work fine. Is +load [2] not
> the recommended place to invoke patches?
+load is kind of risky. See Bill Bumgarner's
On 2010 Sep 07, at 15:37, Quincey Morris wrote:
> Didn't that document say that this scenario occurs when the entity has a
> sub-entity …
Ah, indeed this was my first subentity. You are correct as usual, Quincey –
thank you!
___
Cocoa-dev mailing
The workaround given in the note [1] works.
But it recommends that you patch NSMigrationManager "in a method that is
guaranteed to be invoked before migration could be attempted—for example, if
you have an application delegate, this could be in its init method"
Messy. I added a +load method to
> method, and now all of a sudden one relationship in one mapping model
> requires this new method.
Didn't that document say that this scenario occurs when the entity has a
sub-entity? I think, though I didn't keep track of the links, other results in
the search that lead to this
does not exist in Mac OS X v10.5. And the
workaround is: They give you the code for the method and tell you to stitch it
into the runtime.
So I looked more closely at that mapping model. It has 19 entities and 9
to-one|to-many relationships. By that I mean it has 9 of these guys:
On Sep 7, 2010, at 11:26, Jerry Krinock wrote:
> 4. I cannot find the workaround mentioned in the warning in Core Data's 10.6
> Release Notes.
Does this describe and/or provide a solution for your problem?
http://developer.apple.com/mac/library/releasenotes/Cocoa/MigrationCrashBuild10
I'm getting an apparently spurious warning when compiling an mapping model
(.xcmappingmodel) file:
Foo.xcmappingmodel: warning: Relationship Mapping
"Starkoid_entityToStarkoid_entity".ixportLog -- NSMigrationManager method
destinationInstancesForSourceRelationshipNamed:sourc
t; I can set it all up in the datamodel, but to be able to use the data already
> in the app I need to migrate it over. I expect to initially set all quantites
> to 1, but I can't work out how to set up the mapping model so it moves the
> relationships correctly.
>
> Can an
need to migrate it over. I expect to initially
set all quantites to 1, but I can't work out how to set up the mapping
model so it moves the relationships correctly.
Can anyone point me in the right direction?
data model 1.0
Entities: Product, PurchaseOrder
Rel
24 matches
Mail list logo
