Re: A CoreData Limitation?
Re: A CoreData Limitation?
- Subject: Re: A CoreData Limitation?
- From: SA Dev <email@hidden>
- Date: Tue, 17 May 2005 15:50:19 -0400
Hmmm ... if you wouldn't mind, can you elaborate on the very
basics of what actual data you're managing? You said previously
you're new to data models (modeling in general, I take it). If that's
the case, just think of it in terms of the basic object types
(entities) you'll be managing in your data model. Good examples are
Mail.app (Account, Mailbox, Message), or Address Book.app (Group,
Person), etc.
Using the data modeler, create these entities (singular form as
you're representing AN object of a certain type). Then define
properties of the entities. A Mailbox, for instance, would have
properties like "ownerAccount", "mailboxName", and a to-many
relationship to many Message objects called,
"messagesInThisMailbox" (probably just "messages", but it illustrates
the point nicely). A "Message" will have a to-one relationship back
to its Mailbox item called, "mailbox", a "subject", a to-many
"recipients", "content", "attachments", etc. Soon you'll have a nice-
looking model you can weep with joy over.
What you once had to keep straight in your head is now very easy
to build in minutes, graphically, with the data modeler. This takes a
HUGE load off of you because you can easily glance at your model and
tweak it as the concepts are refined in your brain. It makes it a lot
easier to conceptualize your data model once you learn how to use
this tool. Again, read Apple's docs on using XCode's data modeler for
specifics on how to do all this, but it all starts with making a list
of all the basic 'things' your model will keep track of.
On May 17, 2005, at 3:19 PM, Arthur Schuster wrote:
On 17.05.2005, at 20:39, SA Dev wrote:
Apart from that, your data model may need a once-over (I'm
having a hard time picturing what you're trying to do) to fit the
paradigm - it sounds like it may be over-complicating things a bit.
The model definitively needs a rewrite, and you might be right,
it's probably over-complicating things. This is because it evolved
slowly over the course of years. In the beginning, for example, the
columns weren't customizable. To be able to load old files the
whole model is a big hack now. That's also one of the reasons I
want to rewrite it. And because I never worked with bindings or
CoreData before, my brain probably wants to just bend the current
model until it fits the new paradigms and not rethink the whole
model instead. On the other hand, I really have no idea how I could
represent the data in a different, simpler way.
Arthur Schuster.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden