• 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: Multi-User DB That Talks to Core Data?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Multi-User DB That Talks to Core Data?


  • Subject: Re: Multi-User DB That Talks to Core Data?
  • From: Kyle Sluder <email@hidden>
  • Date: Fri, 14 Aug 2009 11:27:59 -0700

On Fri, Aug 14, 2009 at 10:50 AM, Brad Gibbs<email@hidden> wrote:
> Actually, I wouldn't mind sending the relevant portion of the persistent
> store over the network.  The database is an in-house app that many people
> will need to be able to work in simultaneously.  We'll use that database to
> create products and packages and to update pricing and information.  That
> data needs to be sent to the Core Data client.

You would need to send the entire persistent store.  NSAtomicStore is
what it says it is: atomic.  The store exists in state A, then a save
happens, then it exists in state B.  This quickly becomes untenable
for large datasets.

> The Core Data-based app is something we'll give to perspective customers,
> loading it onto their computer when the time is right.  Only one user at a
> time will access that software, and we won't need access to the information
> until the client is done with it (maybe a week or two later).  Then, we'll
> import the system they've built back into the main database app.

You can't merge persistent stores, so there would be no "main database
app".  Unless you want to open up the persistent store the customer
sent you, figure out the objects that have changed since you sent it
to them (remember, this is atomic store), and do merge conflict
resolution yourself.

> So, transfers might happen a few times per month and they can all be done
> over a local network.

It will probably take you significant human and capital expense to
assemble even a rickety workflow that could pull this off.

> Making the client app would be much easier using Core Data (and, I've
> already actually started working on it).

I'm reasonably certain it would not, having tried to do the same thing
once and realizing how much additional work I was creating for myself,
with no benefit.

--Kyle Sluder
_______________________________________________

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

References: 
 >Multi-User DB That Talks to Core Data? (From: Brad Gibbs <email@hidden>)
 >Re: Multi-User DB That Talks to Core Data? (From: Kyle Sluder <email@hidden>)
 >Re: Multi-User DB That Talks to Core Data? (From: Brad Gibbs <email@hidden>)
 >Re: Multi-User DB That Talks to Core Data? (From: Kyle Sluder <email@hidden>)
 >Re: Multi-User DB That Talks to Core Data? (From: Brad Gibbs <email@hidden>)

  • Prev by Date: Re: Stripping out between chars in NSString
  • Next by Date: Re: iPhone: MPVolumeView not displaying
  • Previous by thread: Re: Multi-User DB That Talks to Core Data?
  • Next by thread: Re: Multi-User DB That Talks to Core Data?
  • Index(es):
    • Date
    • Thread