Nick,
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 p
quot;Simple" as that, problem solved.
Obscure! Pretty sure I haven't read in the docs anywhere that you should have
unique relationship names between entities, so I hope this helps if anyone runs
in to the issue.
Cheers,
-nick
On 23/07/2011, at 11:49 AM, Nick Shore wrote:
> I&#
I'm getting the following error in my application:
CoreData: error: (1) I/O error for database at /Users/nick//blah.sqlite. SQLite error code:1, 'no such column:
t1.Z_3RELATIONSHIP1
This error only occurs if I build the project in Xcode 4.1 on Lion. If I build
the same project on Snow Leopard
