Thanks Erik,
On 01 Dec 2008, at 4:59 PM, Erik Buck wrote:
Vector3DReference is abstract. I have derived Vector3DReference for
all of the cases where I have other entities with relationships to
Vector3DReference. For example, I have a Billboard entity that has
a "to one" relationship to B
On 1 Dec 2008, at 15:59, Erik Buck wrote:
I use Core Data to store large amounts of 3D vector data. I solved
your problem in the following way:
I have a "Vector3D" entity that you can think of as an "end point"
in your model. My Vector3D entity has x,y,z attributes.
I have a "Vector3DR
As another refinement, store all of your end points as an array of float.
Store the array in NSData. Have an entity called EndPointStorage that has an
NSData attribute, endpoints.
The Vector3DReference entity can then have an integer attribute called
endPointIndex. Use endPointIndex to look
I use Core Data to store large amounts of 3D vector data. I solved your
problem in the following way:
I have a "Vector3D" entity that you can think of as an "end point" in your
model. My Vector3D entity has x,y,z attributes.
I have a "Vector3DReference" entity.
Vector3D has a "to many" re
Using an analogy, I'm trying to model a 'vector' using CD. I have a
Vector entity, which has 2 to-one relationships to a VectorEnpoint
entity. The VectorEndpoint entity describes how the Vector is
connected at one end to other entities in the model
Vector:
source -> to-one -> VectorEndpoint
