Re: When NSArray is not an Array
Re: When NSArray is not an Array
- Subject: Re: When NSArray is not an Array
- From: "I. Savant" <email@hidden>
- Date: Thu, 11 Jan 2007 16:54:03 -0500
On Jan 11, 2007, at 4:39 PM, Gordon Apple wrote:
Well, that was kind of my complaint with relational databases
in general
as an object backend. Apparently, Core Data has not solved the
problem. I
guess its part of what's generally called the "impedance mismatch"
when
doing this. We are trying to evaluate whether or not to use Core
Data or
role our own with PostgreSQL. The later still has the same
problem. I
would rather not use blobs for arrays is there is an alternative.
Another
reason to consider Core Data is that SQLite is also available on
the OLPC
(MIT laptop) program which we would like to also target.
I'm sorry, but how exactly would 1) building this solution from
the ground-up with PostgreSQL or 2) using blobs for arrays be
better / more efficient than using Core Data just to gain ordered
lists? With Core Data, you're getting a lot more than just a
'database backend' ...
Honestly, it'd take you all of ten minutes to crank out a drop-in-
reusable solution to this problem provided you've read all the
pertinent documentation. Less if you use mmalc's ready-made example
that handles DnD reordering of the content array. You're making a
mountain out of a mole hill.
in its current incarnation, a sort order
key or the use of a linked list are the only solutions to this
limitation of Core Data. I prefer the use of a sortOrder key ... it's
cleaner and easier to maintain in my opinion and experience. YMMV.
I'm assuming this is what I described with the sequenced index
field?
Yes. Apparently, your terminology may vary as well. :-)
--
I.S.
_______________________________________________
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