[REPOST] Data Modeler/Core Data
[REPOST] Data Modeler/Core Data
- Subject: [REPOST] Data Modeler/Core Data
- From: Cem Karan <email@hidden>
- Date: Fri, 10 Feb 2006 08:01:44 -0500
Apologies to those who saw this before and decided to ignore it; I
never got any comments earlier, and was hoping to get some...
I've been fiddling with the Data Modeler in XCode 2.2.1, and I've run
into these problems and wanted to get other's comments on them.
1) When I specify an Integer 64 as an attribute, and try to set its
max/min/default values to anything outside what an Integer 32 can
hold, the modeler automatically clamps down to the range [-2**32,
2**32). This is a bug, and I need to file it (or so I think).
Comments?
2) I have yet to find a way to group parts of the graph together;
that is, my graph is getting VERY crowded, and it would be nice to
abstract a subset of the model in a group, just so I can see the
forest and the trees at the same time.
3) Is it possible to create limits within the model based on other
items within the model? E.g., I have two attributes, minNumItems and
maxNumItems. I want to be able to specify that maxNumItems >=
minNumItems within the model. I know that I can write code that will
do this, I was just wondering if it is possible to do within the
modeler.
4) The only way I've been able to think of for specifying
enumerations is to have an abstract entity that all of the concrete
entities declare as their parent; entities that need to use the
enumeration specify that they expect an entity of the abstract type.
Is this the best way of doing things in the modeler?
Finally, I have a couple of questions that would probably be better
answered on the Cocoa-dev list, but I'd rather not split this post up.
5) What is the upper limit to the number of elements that an element
can own? I.e., when I specify a 'to-many' relationship, at what
point will CoreData break when I add one more element? What is the
upper limit on the size of the store? I'm being deliberately vague
in that I don't want to find that the SQL store can handle huge
amounts of data, but that the binary or XML versions can't.
6) I noticed that CoreData can handle multiple threads (although I
haven't explored that aspect yet). Can it be distributed? That is,
if I create a cluster of machines, do I end up with a bottleneck
because the only way to distribute the data is via NSProxy, or does
CoreData have a truly intelligent way of replicating data such that
the whole cluster looks like it has one large backing store? If it
does have this ability, what about security? That is, do I have to
figure out how to setup a VPN, use digital certificates, etc., or is
there something in CoreData that will take care of it for me?
Thanks,
Cem Karan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden