Re: Core Data Status
Re: Core Data Status
- Subject: Re: Core Data Status
- From: mmalc Crawford <email@hidden>
- Date: Wed, 20 Jun 2007 10:31:33 -0700
On Jun 20, 2007, at 9:45 AM, James Dessart wrote:
On 6/20/07, Yakov Zaytsev <email@hidden> wrote:
Problem of-course is that we can't change database scheme.. :( So we
need to find a way -rather obvoius?- to make classes on top of
existing scheme to use with core data. That is why CD seems to be
nice to me..
While you can't do this with Core Data, you might be able to do it
with EnterpriseObjects and WebObjects. From what I remember, there are
migration tools to use an old database scheme with an EO object model.
If you're able to use a web server to vend your data, then WebObjects
certainly might offer a solution. It doesn't "own" the database
schema in the same way Core Data does -- and you can use an existing
schema. You could integrate the web content into your app using
WebView (there was an interesting session on hybrid Cocoa/web apps at
WWDC last week)...
However, I'm not sure if it would work nicely with another framework
modifying those tables as well.
Do you mean modifying the schema or modifying records?
If the schema's changed, then any client app will have to change...
If another framework modifies a record simultaneously being edited by
a WebObjects app, then EOF will notice at save time with an optimistic
locking failure (you can also use "pessimistic" locking -- i.e.
actually lock the records on the database -- but this is typically
discouraged).
mmalc
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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