Relationship in Core Data is always a better choice as it help developers to separate data into different tables also it allow user to a safe access of require data not the full access of data to the view if not require it help to safeguard the data when not in use.
As when developer perform fetch request it can able to perform whole Data search from the Core Data at once so you don’t always need to provide unnecessary data fetching for each views you can easily pass into another views when necessary. When fetching for relationship developer can able to fetch according to their choice what table they want to access and what not.
In this video we gonna learn how to use Core Data having a One to Many Relationship.
Recommended Videos :
1. Intro to Core Data : https://youtu.be/0fCxpENpZt4
2. Core Data with MVVM Architecture : https://youtu.be/mpCGUQN1AvM
3. Core Data with One to One Relationship : https://youtu.be/5mYJCj9EjBs
Source Code : https://github.com/recoding-io/swiftui-videos/tree/main/CD_One_To_Many_Relationship
Checkout full playlist :
1. SwiftUI 3.0 Tutorials : https://www.youtube.com/watch?v=eyOT8SNoF8k&list=PLkpYvePHPSwuOzj3B7ljFBWefLHq2rDsv
2. SwiftUI Tutorials : https://www.youtube.com/watch?v=Ru0bEvYiQ_Q&list=PLkpYvePHPSwsj1NrVy7ROQ-8n15AJ1Nnu
3. Apple Persistence Storage : https://www.youtube.com/playlist?list=PLkpYvePHPSwv4N6BO_tlGC0F7E1A1X_wV
Timeline
Intro (00:00)
Core Data with One to Many Relationship (0:28)
What is One to Many Relationship (1:15)
Diagram to One to Many Relationship (1:39)
Example of One to Many Relationship (2:01)
How it Works Behind the Scene (2:31)
App Demo (3:14)
Setting up Entity and Relationship (5:21)
Setting up NSManagedObject Class (7:37)
Creating App Department View (10:33)
Setting up Content View (12:02)
Creating App Employee View (15:21)
Deleting For Data (22:43)
Delete Rules Consideration in One to Many Relationship (24:48)
Support us on
☕ @Buy me a coffee - https://www.buymeacoffee.com/recoding
As when developer perform fetch request it can able to perform whole Data search from the Core Data at once so you don’t always need to provide unnecessary data fetching for each views you can easily pass into another views when necessary. When fetching for relationship developer can able to fetch according to their choice what table they want to access and what not.
In this video we gonna learn how to use Core Data having a One to Many Relationship.
Recommended Videos :
1. Intro to Core Data : https://youtu.be/0fCxpENpZt4
2. Core Data with MVVM Architecture : https://youtu.be/mpCGUQN1AvM
3. Core Data with One to One Relationship : https://youtu.be/5mYJCj9EjBs
Source Code : https://github.com/recoding-io/swiftui-videos/tree/main/CD_One_To_Many_Relationship
Checkout full playlist :
1. SwiftUI 3.0 Tutorials : https://www.youtube.com/watch?v=eyOT8SNoF8k&list=PLkpYvePHPSwuOzj3B7ljFBWefLHq2rDsv
2. SwiftUI Tutorials : https://www.youtube.com/watch?v=Ru0bEvYiQ_Q&list=PLkpYvePHPSwsj1NrVy7ROQ-8n15AJ1Nnu
3. Apple Persistence Storage : https://www.youtube.com/playlist?list=PLkpYvePHPSwv4N6BO_tlGC0F7E1A1X_wV
Timeline
Intro (00:00)
Core Data with One to Many Relationship (0:28)
What is One to Many Relationship (1:15)
Diagram to One to Many Relationship (1:39)
Example of One to Many Relationship (2:01)
How it Works Behind the Scene (2:31)
App Demo (3:14)
Setting up Entity and Relationship (5:21)
Setting up NSManagedObject Class (7:37)
Creating App Department View (10:33)
Setting up Content View (12:02)
Creating App Employee View (15:21)
Deleting For Data (22:43)
Delete Rules Consideration in One to Many Relationship (24:48)
Support us on
☕ @Buy me a coffee - https://www.buymeacoffee.com/recoding
- Category
- Job
Be the first to comment