On 04.11.2009, at 12:15, Kai Brüning wrote:
2. multithreaded core data is very hard to get right (multiple contexts,
data merges)
Isn’t this true for multi threaded code in general?
Seriously, the documentation explains how to structure multi threaded use of
Core Data. This might even
On Nov 10, 2009, at 8:15 AM, Ruotger Skupin wrote:
True, but as I found out the hard way, using Core Data multithreaded and
Bindings at the same time is a very bad idea and will lead you into a world
of pain.
This is part of the reason for Core Data’s recommended thread isolation policy:
more disadvantages to mention:
1. schema updates with every model change if you use an sql store (you
have to make a mapping for every single from version/ to version
combination you need to support)
2. multithreaded core data is very hard to get right (multiple
contexts, data merges)
3.
On 4.11.2009, at 11:33, Ruotger Skupin wrote:
more disadvantages to mention:
1. schema updates with every model change if you use an sql store
(you have to make a mapping for every single from version/ to
version combination you need to support)
In Snow Leopard Core Data does this
Core Data is powerful stuff but it can be tough going - very tough
going.
If you are determined to make your code work you will get through it.
If not, it might get the better of you.
The fact is that CoreData offers a great deal of functionality. If you
want that functionality you either
I have not used core data myself, my only comment is that the best
time to learn a technology is when you have a real project which could
use it, I find that's a lot better way to get beyond the 10 line
examples or whatever simple examples you think up as a 'good way to
learn this' and
On 11/3/09 8:22 PM, David Hirsch said:
So, I'm hearing folks sing the praises of CoreData, which I have not
yet learned. It seems like a long uphill climb, but if life will be
spectacular afterwards, I'll do it. I am a semi-casual programmer;
I've just finished a couple of small programs that
1. Keep going back to the documentation.
It takes time to grasp all the concepts.
If something is not clear and complete,
submit a comment on the documentation.
Every documentation web page has a link
to a comment form.
___
Cocoa-dev
So, I'm hearing folks sing the praises of CoreData, which I have not
yet learned. It seems like a long uphill climb, but if life will be
spectacular afterwards, I'll do it. I am a semi-casual programmer;
I've just finished a couple of small programs that do not use
CoreData, and I can
Hi David,
this question is most definitely on topic :-)
So, lets see, what would Core Data give you:
- Scalability, fast incremental loads and saves for big data sets.
I don’t think you’ll need this. Loading and saving 500 items each time
will be fast enough.
- A data model modeler.
That’s
10 matches
Mail list logo
