A CoreData Limitation?
A CoreData Limitation?
- Subject: A CoreData Limitation?
- From: Arthur Schuster <email@hidden>
- Date: Tue, 17 May 2005 20:20:13 +0200
I am thinking about rewriting one of my applications to make use of
CoreData (the current code doesn't even use bindings, so it would be
a complete rewrite), because of the better maintainability. I just
started looking into this, so I could be completely wrong, but I
think I found a limitation in CoreData that would make it impossible
to implement my previous data model (at least with the data model
designer of Xcode, maybe it's possible in code).
The current implementation of the application displays data in a
table view, but not only the rows are customizable, the columns are
as well: there are three different cell-types and no limitations on
the number of columns or rows. The data in the cells of one row form
a "data unit", the cells of one column don't really have much more in
common other than their column. Currently, my data model consists of
two "root" containers (arrays): one for the columns, another one for
the rows. The columnArray contains objects that describe
NSTableColumns (and create them on demand---the table view is also
created and set up in code) with title, width, etc. The objects of
the rowArray, on the other hand, contain dictionaries that themselves
contain the actual cell values of the table view. The (of course
unique...) identifiers of the columns are used as keys.
This model works fine (without CoreData), also searching, sorting,
etc. are implemented. In CoreData, I have no idea how to "use" the
columns, which are also part of the data model, as keys for the data
contained in the rows. If someone has an idea how this could be
solved, I'd be very grateful (also completely new data models, that
are of course possible to implement and don't change the application
behaviour, are welcome).
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