> if you look at the entity
> descriptions you'll see that the Event entity description in the calendar
> store includes a versionHashModifier and the imported one does not.
> Â Specifying the same version hash modifier in your imported version of the
> Event entity should fix that.
Now it works! T
On Aug 7, 2009, at 8:39 AM, Matteo Manferdini wrote:
This can happen as a side effect of the old template code that
merges a
model using all managed object models from the application
resources as well
as all frameworks linked into the application.
Thank you Adam, this is exactly the case
> This can happen as a side effect of the old template code that merges a
> model using all managed object models from the application resources as well
> as all frameworks linked into the application.
Thank you Adam, this is exactly the case! The old template code (I
inherited it from Tiger, sinc
On Aug 6, 2009, at 10:37 AM, Matteo Manferdini wrote:
To further investigate the matter, I logged the contents of both the
NSStoreModelVersionHashesKey dictionary from my store metadata and the
dictionary returned by the entityVersionHashesByName: method of my
source model. I did this both for
On Aug 6, 2009, at 10:37 AM, Matteo Manferdini wrote:
What I discovered is that in the first case the hashes are the same
for the model and the store, while in the second case the model has
lost a lot of metadata in the versioning process. Along with my
entities there are also other entities li
To further investigate the matter, I logged the contents of both the
NSStoreModelVersionHashesKey dictionary from my store metadata and the
dictionary returned by the entityVersionHashesByName: method of my
source model. I did this both for my working app without versioning
and the not working one
> Did you create a mapping model?
> If not, did you specify the NSInferMappingModelAutomaticallyOption option?
Yes, I did create one. But I think that the problem is not there,
since not knowing the source model, Core Data cannot infer the correct
mapping model.
For the manual migration I'm sure o
I had this exact problem. I did exactly what he did, and to continue
this, yes, I did create a mapping model. Never got it to work, but I
had a user base of 1 and a database of about 10 objects at the time,
so I just abandoned attempting migration entirely and recreated the DB
with the new
On Aug 4, 2009, at 11:20 PM, Matteo Manferdini wrote:
I created a mapping model and
called addPersistentStoreWithType:configuration:URL:options:error:
with the NSMigratePersistentStoresAutomaticallyOption option.
Did you create a mapping model?
If not, did you specify the NSInferMappingModelA
On Aug 4, 2009, at 11:20 PM, Matteo Manferdini wrote:
I'm trying to run core data migration on the store of my app but it
seems to be unable to find the source object model no matter what.
What happens if you don't try to perform migration and instead simply
open the existing store with the
Hi everybody,
I'm trying to run core data migration on the store of my app but it
seems to be unable to find the source object model no matter what. I
tried different approaches, taking some hints by some results I found
on google, but without success. This is what I tried:
- First I tried followi
11 matches
Mail list logo
