should core data code must be embedded into viewController code

Question

I'm now developing an app with core data on iPhone. After reading many projects about core data, I find that core data code is embedded into viewController code in all of there projects. for example:

@interface MyAppMasterViewController : UITableViewController <NSFetchedResultsControllerDelegate>

@property (strong, nonatomic) MyAppDetailViewController *detailViewController;

@property (strong, nonatomic) NSFetchedResultsController *fetchedResultsController;
@property (strong, nonatomic) NSManagedObjectContext *managedObjectContext;

I want to split all code about core data from viewController, and create a special storage class. what's more, provide some method to package core data api, for example:

@interface MyAppMasterViewController : UITableViewController
...
...
@interface MyAppStorageClass : NSObject <NSFetchedResultsControllerDelegate>
@property (strong, nonatomic) NSFetchedResultsController *fetchedResultsController;
@property (strong, nonatomic) NSManagedObjectContext *managedObjectContext;

(Note *)createNote;
(BOOL)deleteNote;

I think, if one day, I don't want to use core data to store my project, I can replace it with low cost.

All above, is that right? and can I do this?

score 0 · Accepted Answer · edited May 23 '17 at 10:24

0

Yes, it's a good idea to separate your data storage code from your user interface code. I tend to use a singleton class like this to manage data for an application.

edited May 23 '17 at 10:24

Community

1
1

answered Mar 08 '12 at 12:57

Jim

72,985
14
101
108

score 0 · Answer 2 · answered Mar 08 '12 at 13:11

0

Its better to factor that out into a data access object. The code isn't spread around, easy testable (code coverage) and reusable even in other projects. Using a singleton and putting that into the appDelegate makes sense in most cases.

answered Mar 08 '12 at 13:11

hburde

1,441
11
6

should core data code must be embedded into viewController code

2 Answers2