Re: Core Data: How best to create a data model for tracking changes to related objects?
Re: Core Data: How best to create a data model for tracking changes to related objects?
- Subject: Re: Core Data: How best to create a data model for tracking changes to related objects?
- From: Steve Weller <email@hidden>
- Date: Sun, 11 Feb 2007 22:19:42 -0800
On Feb 11, 2007, at 9:44 PM, Scott Stevenson wrote:
On Feb 11, 2007, at 8:37 PM, Steve Weller wrote:
2. If I create an abstract entity called TrackedItem with a name
and a UUID and make that the parent of Files and Folders then I
can remove the name and UUID from them, and Transaction just has a
to-many relationship with Tracked Item. This seems much simpler.
I agree. This is easier for a number of reasons. There's ultimately
little that separates folders and files, particularly if you
consider file packages, which are folders that just appear to be
single files to the user.
Assuming I go this way, how do I distinguish between files and
folders that are returned as query on a TrackedItem for, say a range
of dates? Is it necessary to have a flag in the abstract entity that
says "I am a folder" or "I am a file" so that my query is possible,
or is there a way that does not involve filtering the TrackedItems a
second time?
_______________________________________________
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