The impact of master data on an existing iphone project

I'm starting to look at Core Data, as many argue that this is the best way to save data.

I have a working project with its model and objects, the main purpose of the application is to encapsulate objects as attributes (NString, NSObject, Custom Object..ecc) in one main class, give the opportunity to create many instances of this class, then save it to the repository, then get and display a list of tables with all instances saved.

In this case, when my class is already defined (as an NSObject extension), what can happen with the introduction of Core Data? Do I need to rewrite my model?

For example, as a first attempt, I created a model in xcode and then linked an object to it as an object. But some attributes that did not use the standard, such as string, int ... ecc, got UNDEFINED as a type.

@interface Car {
NSString *name;
WheelsType wtype; <-- undefined
NSDate *buy;
CarColor *color; <-- undefined
}
@end

What does it mean? Can I save only String, Int, Boolean ... ecc, but not my custom classes? If not, what table structure can be?

thank

0
source share
1 answer

Custom types in CoreData can be declared transformable, which means that they will be converted to and from instances NSData. The default converter works in many cases, but your classes may require a custom one NSValueTransformer.

Edit: CoreData , . CoreData, , , , .

0

All Articles