iPhone Development – core data relationships tutorial part 1
I’m going to start a short series on Core Data relationships and maybe throw in some general Core Data stuff too. Here in part one we’re just going to set our app up with core data and add two entities with a simple one to one relationship between them. A one to one relationship means that for every Fruit there will be one source and in our case here the reverse it true too, for every source there is one fruit.

1.) Create a new Tab Bar Application named CoreDataRelationshipsTutorial.
2.) Change FirstView.xib so it looks similar to this.
3.) Add the core data framework to the app.
4.) Right click on Supporting Files and select New File, then choose Core Data select Data Model and hit Next. I just accepted the default name of Model and clicked save.
5.) Select Model.xcdatamodeld and the visual editor will open. Click Add Entity and name it Fruit. Add an Attribute named fruitName of type String. Add another Entity named Source with an Attribute sourceName, which will also be of type String.
6.) Select Fruit and then click the plus symbol under Relationships. Name the relationship fruitSource. Set the destination to Source, there will be no inverse yet. In the relationship data model inspector uncheck the Optional checkbox. In the delete rule select Cascade.
7.) Now select Source and add a relationship named sourceFruit. Destination should be Fruit and set the inverse to artistCareer. Uncheck the Optional checkbox again.
8.) Select Fruit under ENTITIES and then go under the file menu up top and select New File. Choose Core Data and NSManagedObject subclass,, click Next. Keep the default location and click Create.
Repeat this same process after selecting Source under ENTITIES.
You should now see your new objects listed under Supporting Files.
9.) Open up CoreDataRelationshipsTutorial-Prefix.pch and add an import for CoreDate. This saves us from having to import it into every file that will use it.
|
1
2
3
4
5
6
7
8
9
10
11
12
|
#import <availability.h>#ifndef __IPHONE_3_0#warning "This project uses features only available in iPhone SDK 3.0 and later."#endif#ifdef __OBJC__ #import <uikit uikit.h=""> #import <foundation foundation.h=""> #import <coredata coredata.h="">#endif</coredata></foundation></uikit></availability.h> |
10.) Now let’s add all the necessary Core Data code to the app delegate files.
First the header file. Import our FirstViewController, then declare private instance variables for our NSManagedObjectContext, NSManagedObjectModel and NSPersistentStoreCoordinator. Create an IBOutlet with out FirstViewController, and declare two methods that we’ll implement.
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
|
#import <uikit uikit.h="">#import "FirstViewController.h"@interface CoreDataRelationshipsTutorialAppDelegate : NSObject <uiapplicationdelegate, uitabbarcontrollerdelegate=""> {@private NSManagedObjectContext *managedObjectContext; NSManagedObjectModel *managedObjectModel; NSPersistentStoreCoordinator *persistentStoreCoordinator;}@property (nonatomic, retain) IBOutlet UIWindow *window;@property (nonatomic, retain) IBOutlet UITabBarController *tabBarController;@property (nonatomic, retain) IBOutlet FirstViewController *firstViewController;@property (nonatomic, retain, readonly) NSManagedObjectContext *managedObjectContext;@property (nonatomic, retain, readonly) NSManagedObjectModel *managedObjectModel;@property (nonatomic, retain, readonly) NSPersistentStoreCoordinator *persistentStoreCoordinator;- (NSURL *)applicationDocumentsDirectory;- (void)saveContext;@end</uiapplicationdelegate,></uikit> |
11.) Now open the app delegate implementation file. Synthesize our firstViewController, then set it’s managedObjectContext to the one created in the app delegate. You may see an error on the line that sets the managedObjectContext because we haven’t set that up in FirstViewController yet.
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
|
#import "CoreDataRelationshipsTutorialAppDelegate.h"@implementation CoreDataRelationshipsTutorialAppDelegate@synthesize window=_window;@synthesize tabBarController=_tabBarController;@synthesize firstViewController;- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions{ firstViewController.managedObjectContext = self.managedObjectContext; self.window.rootViewController = self.tabBarController; [self.window makeKeyAndVisible]; return YES;} |
Implement all these methods.
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
|
/** Returns the URL to the application's Documents directory. */- (NSURL *)applicationDocumentsDirectory{ return [[[NSFileManager defaultManager] URLsForDirectory:NSDocumentDirectory inDomains:NSUserDomainMask] lastObject];}- (void)saveContext{ NSError *error = nil; NSManagedObjectContext *objectContext = self.managedObjectContext; if (objectContext != nil) { if ([objectContext hasChanges] && ![objectContext save:&error]) { // add error handling here NSLog(@"Unresolved error %@, %@", error, [error userInfo]); abort(); } }}#pragma mark -#pragma mark Core Data stack/** Returns the managed object context for the application. If the context doesn't already exist, it is created and bound to the persistent store coordinator for the application. */- (NSManagedObjectContext *)managedObjectContext{ if (managedObjectContext != nil) { return managedObjectContext; } NSPersistentStoreCoordinator *coordinator = [self persistentStoreCoordinator]; if (coordinator != nil) { managedObjectContext = [[NSManagedObjectContext alloc] init]; [managedObjectContext setPersistentStoreCoordinator:coordinator]; } return managedObjectContext;}/** Returns the managed object model for the application. If the model doesn't already exist, it is created from the application's model. */- (NSManagedObjectModel *)managedObjectModel{ if (managedObjectModel != nil) { return managedObjectModel; } managedObjectModel = [[NSManagedObjectModel mergedModelFromBundles:nil] retain]; return managedObjectModel;}/** Returns the persistent store coordinator for the application. If the coordinator doesn't already exist, it is created and the application's store added to it. */- (NSPersistentStoreCoordinator *)persistentStoreCoordinator{ if (persistentStoreCoordinator != nil) { return persistentStoreCoordinator; } NSURL *storeURL = [[self applicationDocumentsDirectory] URLByAppendingPathComponent:@"CoreDataTabBarTutorial.sqlite"]; NSError *error = nil; persistentStoreCoordinator = [[NSPersistentStoreCoordinator alloc] initWithManagedObjectModel:[self managedObjectModel]]; if (![persistentStoreCoordinator addPersistentStoreWithType:NSSQLiteStoreType configuration:nil URL:storeURL options:nil error:&error]) { NSLog(@"Unresolved error %@, %@", error, [error userInfo]); abort(); } return persistentStoreCoordinator;} |
12.) Open up FirstViewController.h and let’s set it up with the necessary code and instance variables.
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
|
#import <uikit uikit.h="">@interface FirstViewController : UIViewController { NSFetchedResultsController *fetchedResultsController; NSManagedObjectContext *managedObjectContext;}@property (nonatomic, retain) NSString *fruitNameString;@property (nonatomic, retain) NSString *fruitSourceString;@property (nonatomic, retain) NSFetchedResultsController *fetchedResultsController;@property (nonatomic, retain) NSManagedObjectContext *managedObjectContext;- (IBAction) saveData;@end</uikit> |
13.) Now for the implementation file. Let’s import our managed objects.
|
1
2
3
|
#import "FirstViewController.h"#import "Fruit.h"#import "Source.h" |
Then synthesize the instance variables.
|
1
2
|
@synthesize fetchedResultsController, managedObjectContext;@synthesize fruitNameString, fruitSourceString; |
Let’s go ahead and set the values of those two strings in ViewDidLoad.
|
1
2
3
4
5
6
|
- (void)viewDidLoad{ [super viewDidLoad]; fruitNameString = [[NSString alloc] initWithString:@"Apple"]; fruitSourceString = [[NSString alloc] initWithString:@"Apple Tree"];} |
14.) Implement the saveData method.
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
- (IBAction) saveData{ NSLog(@"saveData"); Fruit *fruit = (Fruit *)[NSEntityDescription insertNewObjectForEntityForName:@"Fruit" inManagedObjectContext:managedObjectContext]; fruit.fruitName = fruitNameString; Source *source = (Source *)[NSEntityDescription insertNewObjectForEntityForName:@"Source" inManagedObjectContext:managedObjectContext]; source.sourceName = fruitSourceString; // Because we set the relationship fruitSource as not optional we must set the source here fruit.fruitSource = source; NSError *error; // here's where the actual save happens, and if it doesn't we print something out to the console if (![managedObjectContext save:&error]) { NSLog(@"Problem saving: %@", [error localizedDescription]); } // **** log objects currently in database **** // create fetch object, this object fetch's the objects out of the database NSFetchRequest *fetchRequest = [[NSFetchRequest alloc] init]; NSEntityDescription *entity = [NSEntityDescription entityForName:@"Fruit" inManagedObjectContext:managedObjectContext]; [fetchRequest setEntity:entity]; NSArray *fetchedObjects = [managedObjectContext executeFetchRequest:fetchRequest error:&error]; for (NSManagedObject *info in fetchedObjects) { NSLog(@"Fruit name: %@", [info valueForKey:@"fruitName"]); Source *tempSource = [info valueForKey:@"fruitSource"]; NSLog(@"Source name: %@", tempSource.sourceName); } [fetchRequest release];} |
15.) Release our objects in the dealloc method and set them to nil in viewDidUnload.
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
|
- (void)viewDidUnload{ [super viewDidUnload]; fetchedResultsController = nil; managedObjectContext = nil; fruitNameString = nil; fruitSourceString = nil;}- (void)dealloc{ [fetchedResultsController release]; [managedObjectContext release]; [fruitNameString release]; [fruitSourceString release]; [super dealloc];} |
16.) Open up FirstView.xib and connect the UIButton to our saveData IBAction.
17.) Open up MainWindow.xib, select the app delegate and connect firstViewController outlet to FirstViewController under the Tab Bar Controller.
18.) Now you can run the app and hit the Save Data button. Look in the console to see the results of the fetch.
The important things to note from this tutorial are these.
When we created the relationship from Fruit to Source we made it so that it was not optional. Therefore during our saveData method we had to set the fruitSource to something.
|
1
2
3
4
|
Fruit *fruit = (Fruit *)[NSEntityDescription insertNewObjectForEntityForName:@"Fruit" inManagedObjectContext:managedObjectContext];fruit.fruitName = fruitNameString;Source *source = (Source *)[NSEntityDescription insertNewObjectForEntityForName:@"Source" inManagedObjectContext:managedObjectContext];source.sourceName = fruitSourceString; |
Try commenting out that last line
|
1
|
// source.sourceName = fruitSourceString; |
And then running it again. What happens? Crash and burn. Because the relationship is not optional you must set the sourceName.
You can also see from the block of code above that we use reuse the same managedObjectContext to create both of the managed objects. Then we set the values and just saved the context. Doing this saved both objects (entities in Core Data).
Another thing to take note of happens in the fetch process. You notice that we only fetch the Fruit entity. But because of the relationship between Fruit and Source we can access the Source entity. We don’t need to do a separate fetch on Source.
|
1
2
3
4
5
6
7
8
9
10
11
12
|
NSFetchRequest *fetchRequest = [[NSFetchRequest alloc] init];NSEntityDescription *entity = [NSEntityDescription entityForName:@"Fruit" inManagedObjectContext:managedObjectContext];[fetchRequest setEntity:entity];NSArray *fetchedObjects = [managedObjectContext executeFetchRequest:fetchRequest error:&error];for (NSManagedObject *info in fetchedObjects){ NSLog(@"Fruit name: %@", [info valueForKey:@"fruitName"]); Source *tempSource = [info valueForKey:@"fruitSource"]; NSLog(@"Source name: %@", tempSource.sourceName); [tempSource release];} |
Okay that does it for this tutorial. Next time we will look at a one to many relationship.
iPhone Development – core data relationships tutorial part 1的更多相关文章
- 用 SQLite 和 FMDB 替代 Core Data
本文转载至 http://blog.csdn.net/majiakun1/article/details/38680147 为什么我不使用Core Data Mike Ash 写到: 就个人而言,我不 ...
- (转)iphone数据存储之-- Core Data的使用
原文:http://www.cnblogs.com/xiaodao/archive/2012/10/08/2715477.html iphone数据存储之-- Core Data的使用(一) 一. ...
- iphone数据存储之-- Core Data的使用(一)
http://www.cnblogs.com/xiaodao/archive/2012/10/08/2715477.html 一.概念 1.Core Data 是数据持久化存储的最佳方式 2.数据最终 ...
- iphone数据存储之-- Core Data的使用
一.概念 1.Core Data 是数据持久化存储的最佳方式 2.数据最终的存储类型可以是:SQLite数据库,XML,二进制,内存里,或自定义数据类型 在Mac OS X 10.5Leopard及以 ...
- Core Data & MagicalRecord
iOS 本地数据持久化存储: 1.plist 2.归档 3.NSUserDefaults 4.NSFileManager 5.数据库 一.CoreData概述 CoreData是苹果自带的管理数据库的 ...
- 《驾驭Core Data》 第三章 数据建模
本文由海水的味道编译整理,请勿转载,请勿用于商业用途. 当前版本号:0.1.2 第三章数据建模 Core Data栈配置好之后,接下来的工作就是设计对象图,在Core Data框架中,对象图被表 ...
- 《驾驭Core Data》 第二章 Core Data入门
本文由海水的味道编译整理,请勿转载,请勿用于商业用途. 当前版本号:0.4.0 第二章 Core Data入门 本章将讲解Core Data框架中涉及的基本概念,以及一个简单的Core Data ...
- ios开发:Core Data概述
Core Data 概述 2005年的四月份,Apple 发布了 OS X 10.4,在这个版本中 Core Data 框架发布了.Core Data本身既不是数据库也不是数据库访问框架.相反,Cor ...
- iOS教程:如何使用Core Data – 预加载和引入数据
这是接着上一次<iOS教程:Core Data数据持久性存储基础教程>的后续教程,程序也会使用上一次制作完成的. 再上一个教程中,我们只做了一个数据模型,之后我们使用这个数据模型中的数据创 ...
随机推荐
- Timestamp类型浅析
Oracle针对不同的数据需求,提供了多种类.多层次的数据类型体系.我们在实际应用中,最好可以依据业务数据的实际形态和前端应用的语言.框架特性来确定字段类型的选择. Date类型是我们经常使用的时间类 ...
- svn ignore 的用法(忽略文件及目录)
svn ignore 的用法(忽略文件及目录) 若想创建了一个文件夹,并且把它加入版本控制,但忽略文件夹中的所有文件的内容: $ svn mkdir spool $ svn propset svn:i ...
- 使用JAVA爬取去哪儿网入住信息
昨天帮一个商科同学爬取去哪儿网站的所有广州如家快捷酒店的所有入住信息. 就是上面的商务出行 xxx年入住这些东西 然而去哪儿的前端很强,在获取所有如家快捷酒店的时候就遇到了问题. 他显示的酒店列表是j ...
- Netty简单的重连机制
其实重连机制并不是多么多高深的技术,其实就是一个在客户端做一个简单的判断,如果连接断了,那么就重新调用连接服务端的代码 当然,我们重连的动作肯定是发生在断连之后发生的,我们可以在上篇的心跳机制的基础上 ...
- vue 时间选择器组件
vue 时间选择器组件 组件效果: 单文件组件: <template> <div class="date-pickers"> <!--date为com ...
- C++异常处理(转)
引言 异常,让一个函数可以在发现自己无法处理的错误时抛出一个异常,希望它的调用者可以直接或者间接处理这个问题.而传统错误处理技术,检查到一个局部无法处理的问题时: 1.终止程序(例如atol,atoi ...
- spring-boot 外部jar 打包 配置
<plugins> <plugin> <groupId>org.springframework.boot</groupId> <artifactI ...
- maven如何引入servlet-api和jsp-api
废话不多说,直接上代码 <dependency> <groupId>javax.servlet</groupId> <artifactId>javax. ...
- 【总结整理】AI产品经理大会2017(转载)
从企业大数据到企业 AI | 易观智慧院院长 李智 1.AI 不是目的,而是要了解 AI 是什么,真正意义上的强人工智能在前沿领域尚未取得突破,暂时只能在影视文学作品中去思考人机关系.机器人三定律在未 ...
- NSArray & NSDictionary
一.NSArray 1.1 简单创建方法由难到简 NSArray *arr = [[NSArray alloc] init]; NSArray *arr = [NSArray arrayWithObj ...