Torsten,
I've followed some tutorials to get started but somehow I am a bit
lost when I want to do some more complex things. This might actually
be more because of bindings than because of core data. Or maybe I just
did not look at the right place. Maybe you guys can give me some hints
links and so on.
Most of your questions are about Cocoa Bindings or NSTableView
(AppKit). So those would be good technologies to look at, especially
in developer.apple.com documentation.
The Core Data Programming Guide should give you a good idea about
which technologies and classes lie within the Core Data framework,
and which you should search out elsewhere.
<http://developer.apple.com/documentation/Cocoa/Conceptual/CoreData/cdProgrammingGuide.html>
Other links include <http://cocoadevcentral.com/> and
<http://www.cocoadev.com> and
<http://osx.hyperjeff.net/Reference/CocoaArticles.php?cat=all> and
pretty much all their external links.
I was also wondering ...what if we are talking about 1M objects (or
rows thinking of it in terms of a database). How does this scale?
If you're on 10.5, the framework can handle millions of rows. It is
of course necessary to restrict your UI classes to only showing the
user as much data as a human being can process (not much) and to be
careful about controlling the high watermark of your memory usage.
On 10.5, the NSArrayController has a "Use Lazy Fetching" option which
can assist you with this.
Also I am wondering about migrations. When you change the data model
and users upgrade the application. How can one define the migrations?
On 10.5, Core Data has both tools in Xcode, and classes in the
framework for this. They're called mapping models and NSMappingModel
respectively.
--
-Ben
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please 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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
