Re: A CoreData Limitation?
Re: A CoreData Limitation?
- Subject: Re: A CoreData Limitation?
- From: Óscar Morales Vivó <email@hidden>
- Date: Tue, 17 May 2005 16:15:43 -0400
May I suggest, put everything "fixed" in the Core Data Model and put
everything else in "blob" properties. If you know what I mean.
After all for the most part it seems the additional data could go in
a 'other' dictionary property in the model. You'd need to write more
code than you'd like to get it working but it seems like it can be
done. Then again I might have not caught exactly what you want.
On 17 May , 2005, at 16:03 , Arthur Schuster wrote:
I found this in another thread:
On 11.05.2005, at 20:21, Bill Bumgarner wrote:
SQLite did not support ALTER TABLE until very, very recently.
IIRC 3.1.3 -- the version that ships with Tiger -- has very
limited ALTER TABLE support, if any at all. So adding or
removing a "column" (the change may be more complicated) is not
simply a matter of writing an appropriate ALTER TABLE SQL statement.
I think this pretty much sums up my problem---if it's (nearly or
completely) impossible to for CoreData itself to change its data
model by adding or removing a column, I probably also won't be able
for me as a developer to use CoreData for storing the data of a
table view with a variable number of columns.
So I'll stay with my current ugly but working model, unless of
course someone still finds a great workaround for this.
Arthur Schuster.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden