On Tue, 28 May 2013 21:16:05 -0700, Rick Mann said:
>Pity Xcode doesn't automatically make a copy of the model when you make
>a change (after each build).
That would be really annoying during development when your model is changing
rapidly.
Also, IIRC, inferred migration requires that newly add
Pity Xcode doesn't automatically make a copy of the model when you make a
change (after each build).
Thanks.
On May 28, 2013, at 21:14 , Dave Fernandes wrote:
> I think I have gotten away with that for development purposes in the past,
> but that isn't the way it is supposed to work. And thin
I think I have gotten away with that for development purposes in the past, but
that isn't the way it is supposed to work. And things have definitely been
tightened up as Core Data has evolved. If you want to open old persistent
stores, you will need to have a copy of the model that goes with it.
On May 28, 2013, at 20:50 , Dave Fernandes wrote:
> Forgive the basic question, but do you still have the old version of the
> model present in your versioned model?
That's an excellent question, and no, I don't. But I still thought I've
successfully added properties without actually making d
Forgive the basic question, but do you still have the old version of the model
present in your versioned model?
On 2013-05-28, at 10:18 PM, Rick Mann wrote:
> In the past, Core Data was able to deal with a simple addition of a property
> to an Entity. Now, every time I add a property, I get "C
