• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: A CoreData Limitation?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A CoreData Limitation?


  • Subject: Re: A CoreData Limitation?
  • From: Arthur Schuster <email@hidden>
  • Date: Tue, 17 May 2005 22:03:21 +0200

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


  • Follow-Ups:
    • Re: A CoreData Limitation?
      • From: Óscar Morales Vivó <email@hidden>
References: 
 >A CoreData Limitation? (From: Arthur Schuster <email@hidden>)

  • Prev by Date: Re: A CoreData Limitation?
  • Next by Date: Re: A CoreData Limitation?
  • Previous by thread: Re: A CoreData Limitation?
  • Next by thread: Re: A CoreData Limitation?
  • Index(es):
    • Date
    • Thread