Mathijs Kadijk

Importing incorrect data corrupts the context, if you still save the context hell will break loose. So I think importing should happen in a seperate child context and the user...

CoreData doesn't call `willSave` for newly inserted objects. So many of my projects include this "fix", maybe CoreDataKit could include this as a optional fix that you can enable?! ```...

See: http://microsoft.wikia.com/wiki/WinFS#Relationships And also: https://github.com/mac-cain13/CoreDataKit/issues/5

So you don't have to save it with something like doctrine, but also can put it in an single database field or on disk.

So you can see what state changes happened when.

That would make it super easy to save transactions to the database. That is also probably what you want 90% of the time. By extending this entity you could also...

Should be somewhat more specific, also check where it's used and what for.