Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Core Data] Lightweight Objects



Hi,

Hopefully this is a simple question:

I have a core data application in mind, and I'm wondering what the best way
to organise my model would be. The bit that has me concerned is that I have
an entity (let's call it "aLog") that has associated with it an ordered set
of 1 byte values that's variable in number. They are data samples from an
device which captures data. There's no real limit on how many samples might
exist in a log.

So, I could have:

aLog ----to many---> aSample

But that seems very wasteful, especially as the sample will probably need an
Id number to keep sequence and possibly a reverse relation to say which log
a sample belongs to. Multiply up by thousands of samples and that seems
silly.

So I'm thinking it would be nice to store the samples in a property of the
"aLog" entity. A String with no max length? A BLOB?

Any suggestions?

Paul
_______________________________________________

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:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden

This email sent to email@hidden



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.