1 to many core data w/ large arrays
1 to many core data w/ large arrays
- Subject: 1 to many core data w/ large arrays
- From: "Brett O'Donnell" <email@hidden>
- Date: Sun, 8 May 2005 17:51:08 -0500
Hey guys,
Since there isn't a Core Data list, I was hoping I could get
some opinions from you wonderful people!
It's disturbingly easy to make data arrays and such with core data...
I'm trying to make an app to store data for multiple transactions for
multiple customers.
It doesn't seem too hard to make the app have a list of customers,
and a list of transactions... but what's the best way to mix the two?
Should the "customer" view be a sort through the main database for
all transactions with "customer145" as the controller, or should
there be "customer" that opens up a whole bunch of little docs with
transactions?
Which is better for future core data things?
It seems like one makes the customers more modular, but could make
creating reports of multiple customers more complicated.... On the
other hand, would having the data be displayed as part of a bigger
file cause problems? I know SQLite is pretty scalable, but what about
2000+ customers with 100 transactions?
There's a good chance that I'm missing something simple... so advice
would be wonderful!
Thanks,
Brett
_______________________________________________
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