During migration you have a bare NSManagedObject and not your custom subclass.
So any custom code has to be in a migration policy.
Sent from my iPhone
> On May 20, 2014, at 12:07 PM, Mike Abdullah wrote:
>
>
>> On 20 May 2014, at 15:21, Sean McBride wrote:
>>
>> Hi all,
>>
>> Doing a Core
On 2014 May 20, at 07:21, Sean McBride wrote:
> As a test I made the relationship optional, then it no longer complains.
Consider leaving it that way, Sean. The only effect I’ve ever had from setting
Core Data properties to be non-optional is the creation of mysterious errors
and exceptions
On 20 May 2014, at 15:21, Sean McBride wrote:
> Hi all,
>
> Doing a Core Data migration (not the lightweight kind) I hit an error at the
> end:
>
> "foo is a required value."
>
> the 'foo' relationship it complains about is transient and so not present in
> the store. Normally, I recreate
On Tue, 5 Mar 2013 18:56:32 -0800, Jerry Krinock said:
>> I take it you are using your technique successfully in practice?
>
>Maybe not. I'd pasted in some of my code but modified it for your
>case. Although I have done a lot of stuff in that method, I'm not sure
>if I have ever used that specif
On 2013 Mar 05, at 14:25, Sean McBride wrote:
> I take it you are using your technique successfully in practice?
Maybe not. I'd pasted in some of my code but modified it for your case.
Although I have done a lot of stuff in that method, I'm not sure if I have ever
used that specific techniq
On Mon, 4 Mar 2013 22:17:44 -0800, Jerry Krinock said:
>This is easy to do with a mapping model, migration policy and migration
>manager. In your NSMigrationManager subclass implementation, implement
>an override something like this…
>
>- (BOOL)createDestinationInstancesForSourceInstance:
>(NSMan
Correcting the message I just sent, wherever I mentioned subclassing
NSMigrationManager, I meant subclassing NSMigrationPolicy.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list
On 2013 Mar 04, at 14:38, Sean McBride wrote:
> What's a good way to delete some managed objects from a store when migrating
> the store from version x to version y? Basically, for entity 'Foo', I'd like
> for instances that match predicate 'bar' to not exist in the new store.
This is easy t
On 2012 Apr 04, at 16:40, Sean McBride wrote:
> How do I update my existing .xcmappingmodels to point to version 4 instead of
> 3?
>
> When viewing the xcmappingmodel in Xcode 4, should I use the 'destination'
> popup and change it from 3 to 4? After doing so, and diffing its
> xcmapping.xml
I'm not using autosave. In fact this is done in my document controller before
the NSPersistentDocument is even created. Does the Core Data stack have some
awareness of an autosave mode? Perhaps, as you suggest, Apple has dropped this
feature and this is just a documentation bug. Hope someone fro
On 2011 Jul 31, at 21:18, Dave Fernandes wrote:
> I just found a strange thing on Lion: the backup~ file doesn't get produced
> with in-place lightweight migration. The same binary *does* create the
> backup~ file on Snow Leopard, though. Has anyone else noticed this?
Have not noticed it becau
I just found a strange thing on Lion: the backup~ file doesn't get produced
with in-place lightweight migration. The same binary *does* create the backup~
file on Snow Leopard, though. Has anyone else noticed this?
On 2011-07-21, at 8:31 AM, Roland King wrote:
> I suppose I had to get to core
On 2011-07-21, at 12:16 PM, Roland King wrote:
> Great - thanks for this - gets me started, I've found the documentation quite
> dense and soon I have to pitch in and just give it a go (I have a model I
> need to update in my test app and I really don't want to toss the data).
>
> I need to h
Great - thanks for this - gets me started, I've found the documentation quite
dense and soon I have to pitch in and just give it a go (I have a model I need
to update in my test app and I really don't want to toss the data).
I need to hunt around the NSManagedObjectModel class a bit more, clear
Yes, if you want the file deleted you have to do it yourself. There are
certainly cases where you would not want to delete the file. For example for a
document, the user may want to keep that archive around in case they need to
revert to a previous version of the app, or share it with someone el
On 2011 Jan 16, at 17:31, Michael Link wrote:
> This migration is using the default mapping model created in Xcode. The Event
> entity was changed to have an abstract parent entity, before it stood alone.
Migrating abstract entities can be problematic. For example,
http://www.cocoabuilder.com
On 2010 Sep 13, at 15:38, Jerry Krinock wrote:
> …I found that Xcode accepted my input if I set "Source Fetch" to Default and
> entered one of these as "Filter Predicate":
>
>($source.beak != nil) // Bird
>($source.beak == nil) // Fish
Upon studying my situation a little furt
Oh sorry, forgot to 'reply all'
my bad.
Thanks,
Chaitanya Pandit
Expersis Software Inc.
On Dec 22, 2009, at 7:12 PM, Jerry Krinock wrote:
>
> On 2009 Dec 21, at 23:16, Chaitanya Pandit wrote:
>
>> Hi jerry,
>> I think what i'll have to do is if the user closes the doc without saving,
>> just
On Dec 20, 2009, at 11:40 pm, Chaitanya Pandit wrote:
> One weird thing that is happening is that just after the
> "configurePersistentStoreCoordinatorForURL..." call, the contents of my
> document on the disk are changed, even if i didn't save the document
>
It's not clear in what sense this
On 2009 Dec 20, at 23:40, Chaitanya Pandit wrote:
> I'm working on the migration for one of my Core Data document based
> application
>
> One weird thing that is happening is that just after the
> "configurePersistentStoreCoordinatorForURL..." call, the contents of my
> document on the disk a
On Sep 2, 2009, at 4:51 AM, Ian Kennedy wrote:
Hi all,
How would I go about doing a one-time migration of application data
from an xml persistent store to a sqlite persistent store? i.e. the
model stays the same, the data is migrated, and the app uses the
sqlite store from there on out.
On Thu, May 7, 2009 at 1:19 PM, Adam Swift wrote:
> Unless you are specifying NSIgnorePersistentStoreVersioningOption as an
> option to addPersistentStoreWithType:...
I'm not.
> ... if there are any changes to your
> data model that would result in changes to the data that is persisted
> ...
On May 7, 2009, at 7:02 AM, I. Savant wrote:
On Wed, May 6, 2009 at 6:36 PM, Melissa J. Turner
wrote:
Context is important. Also future-proofing.
If your app was originally written against v1 CoreData (Tiger),
you need to
update the app to be wise enough to check the store's metadata a
On Wed, May 6, 2009 at 6:36 PM, Melissa J. Turner wrote:
> Context is important. Also future-proofing.
>
> If your app was originally written against v1 CoreData (Tiger), you need to
> update the app to be wise enough to check the store's metadata and run away,
> run away from any store containi
Dear Apple Developer Engineering Team (Dev Support, Dev Tools, Core
Data, and anyone else who works for Matt Firlik):
I miss Enterprise Objects Framework for the Desktop. Badly.
I know the Objective-C codebase is sitting somewhere in an old CVS or
Subversion repository deep in the bowels of
Context is important. Also future-proofing.
If your app was originally written against v1 CoreData (Tiger), you
need to update the app to be wise enough to check the store's metadata
and run away, run away from any store containing unexpected values (ie
version hash information). v1 CoreDa
On Apr 7, 2009, at 12:28 PM, Timothy Larkin wrote:
I think that Jon is asking whether he should give a version number
to his data model, and not whether he should create a second version
of his data model. If this is in fact his question, then I think the
answer is yes, because this will m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think that Jon is asking whether he should give a version number to
his data model, and not whether he should create a second version of
his data model. If this is in fact his question, then I think the
answer is yes, because this will make it
On Apr 7, 2009, at 10:53 AM, Jon Munson II wrote:
I wasn't certain if, in order to utilize versioning later, that I
would need to mark the current model in some way. The Apple dox
didn't state one way or another, and I didn't wish to make an
assumption and find out later that I missed som
I wasn't certain if, in order to utilize versioning later, that I
would need to mark the current model in some way. The Apple dox
didn't state one way or another, and I didn't wish to make an
assumption and find out later that I missed some important step which
would result in hours of hea
On Apr 7, 2009, at 9:34 AM, Jon C. Munson II wrote:
One thing I cannot readily determine from the documents is whether one
should begin with a "versioned" model. By "begin" I mean the model is
versioned from the start as opposed to later in the application's life
cycle.
So, my question is: is
Having worked through this problem myself, I can offer a few
suggestions. First, some kind list member pointed out to me that the
automated migration function does not support abstract classes. So you
have to outwit Apple.
I created a custom migration policy for the abstract class by
subc
Back on March 29 2008, Mr. Wilson reported a problem with migration
that I seem to be having now. To wit, a core data model that includes
an abstract entity and entity inheritance fails to be migrated on OS X
10.5.
I'm getting different errors than he reported. I created a mapping
model f
On Thu, Sep 11, 2008 at 8:02 PM, Adam Swift <[EMAIL PROTECTED]> wrote:
> No, you'll need to do a manual migration so you can register yourself as an
> observer of the NSMigrationManager's migrationProgress
Thanks Adam, I figured that was the case. I didn't want to spend much
time on this feature
On Sep 11, 2008, at 8:08 AM, Doug Penny wrote:
I have a core data store that I am migrating using the
default/automatic migration process. It seems to work very smoothly,
but takes a minute or two to complete. I would like to provide some
type of feedback to the user to let them know what is
David,
To sum up:
Relationships to entities from which another entity inherits are not
automatically set up properly.
Unfortunately. This is a known issue.
Anyone have any experience with this, or know how to handle this
situation? I suppose I could write a whole bunch of custom code to
han
36 matches
Mail list logo
