• 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: q's regarding appropriate use of core data?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: q's regarding appropriate use of core data?


  • Subject: Re: q's regarding appropriate use of core data?
  • From: Charles Romestant <email@hidden>
  • Date: Sat, 21 Mar 2009 15:29:25 +1930

May I suggest not using a 70 mb file, it might make things slow, plus
distributing that on the target platform ( as I am guessing it is) will not
be practical.
Why not try and do it as a REST API call with parameters, so that you can
retrieve it "as needed" instead of handling all that with that sqllite file.


On Sat, Mar 21, 2009 at 3:18 PM, Darren Minifie <email@hidden> wrote:

> Hey everyone
>
> I have made my way through the documentation to core data and am really
> excited to start using it.  I have a couple of Q's about if my particular
> scenario is appropriate for core data, or if I'm forcing the wrong
> technology for the job.  I suspect that discussing anything related to sdk
> iphone 3.0 is off limits, so i will skirt around that.  If this type of
> talk
> is allowed please let me know and I can elaborate on my poblem.
>
> 1.  For my theseis project I am writing software that wil help visually
> disabled people use public transit through the use of modile devices.  For
> this stage, lets assume I'm talking about a prototype on the mac desktop.
> The transit authority has given me scheduling data in the form of multiple
> txt files.  I have written python scripts to extract the data from these
> files and crate a SQlite database.  With indexes this database is about 70
> MB.  Now, after reading Marcus Zarra's core data book, and some of the
> docs,
> I really like how data can be accessed in an object-like way, and not an
> sql
> way.  My idea was to pre-load a core data store up with this transit info
> and distribute the app accordingly.  I have two concerns that lead me to
> believe that core data may not be appropriate.  First, this data is never
> modified by the user, its just a store of data that is used to find bus
> times.  Second, since the db is so large, I dont want to incur unnecessary
> processing.  Like I siad, I would generally like to avoid the sql api and
> use the features of core data, but my question is, is this overkill?
>
> 2. This may crossing nda lines, so please ignore if inappropriate.  My
> question is, if i created this core data store targeted for a mac
> application, would the store itself be compatible with core data on the
> iphone?  The tutorials on the iphone core data are significantly different
> than for the mac, especially since bindings are still not around.
>
> Thank you for your advice.
>
>
>
> --
> Darren Minifie
> Graduate Studies: Computer Science
> www.myavalon.ca
> www.ohsnapmusic.com
> _______________________________________________
>
> 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
>



--
Lic. Charles M. Romestant F.
Phone: +58412 622 2298
_______________________________________________

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: 
 >q's regarding appropriate use of core data? (From: Darren Minifie <email@hidden>)

  • Prev by Date: Re: NSData confusion
  • Next by Date: Re: NSData confusion
  • Previous by thread: q's regarding appropriate use of core data?
  • Next by thread: re: q's regarding appropriate use of core data?
  • Index(es):
    • Date
    • Thread