Hi Sean,
thanks for the reply. Aye I'd thought of packaging it all up in a
package so that only deliberate saboteurs could harm the integrity of
my lovely lovely app. In terms of UUIDs, I think you're right, it'll
be safer - or rather I'll know that it's definitely my fault if it
isn't working, rather than trying to figure out if the Core Data
objectID naming system has changed between versions!
Thanks for your help,
Ken
On 6 Apr 2010, at 4:17, Sean McBride wrote:
On Tue, 6 Apr 2010 12:27:18 +0100, Ken Tabb said:
I have a Snow Leopard non-document based Core Data app (currently XML
based, but will be SQLite upon release). Supposing I have an entity
(Employee) that would like to store an auxiliary file (a tiff of
their
mugshot), then as I see it I have the following options:
You could make your file format a package and store within it the
TIFFs
and the CoreData persistent store. You can add a 'uuid' string
attribute to your Employee entity and use that as the filename.
--
____________________________________________________________
Sean McBride, B. Eng s...@rogue-research.com
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
- - - - - - - - - -
Dr. Ken Tabb
Mac & UNIX Developer - Health & Human Sciences
Machine Vision & Neural Network researcher - School of Computer Science
University of Hertfordshire, UK
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
