[SOLVED] Re: CoreData "I/O error for database: no such table"
[SOLVED] Re: CoreData "I/O error for database: no such table"
- Subject: [SOLVED] Re: CoreData "I/O error for database: no such table"
- From: Nick Zitzmann <email@hidden>
- Date: Tue, 09 Aug 2011 18:07:16 -0600
On Aug 8, 2011, at 4:35 AM, Nick Shore wrote:
> I was in fact using existing databases - actually the update I'm working on has a migration involved in it too. I didn't mention it originally as I'd ruled it out as the cause, but that actually helped fix the problem. Since I was already migrating the data (with custom entity migration policies) it was trivial to rename the relationships at the same time. And that worked - the migration can read the existing database and it fixed my issue when attempting to read the new one.
And that turned out to be the solution. I was already working on a new data model at the time, so I turned it on and made a mapping model, and the migrator created a database that doesn't generate any I/O errors when the app tries to access the object with the many-to-many relationship.
The really strange part is, I did not rename the many-to-many relationship between database versions, and in the migrated database, the many-to-many table is not called "Z_16PARENTS" as I expected would happen after the migration. But I guess I shouldn't complain.
Nick Zitzmann
<http://www.chronosnet.com/>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden