You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 13, 2018. It is now read-only.
Jared Barnes edited this page Nov 23, 2015
·
24 revisions
The DataContext helps developers with handling changes to models. Think of the DataContext as a transaction handler.
If you have the need to query for data and modify some of the data and the relationships among that model, then the DataContext is your answer. It handles relationships for you, so you don't have to think about updating foreign keys, or primary keys from a service. The DataContext wants you to think about data as it should be, just data, not so much about the storage structure for persisting the data.
The DataContext uses many of the other technologies to handle complexity. It uses Queryables for querying your data store, Futures for asynchrony, and Observables for knowing whether or not properties have changed on a instance of a model.
Here is a list of the other technologies that you need to understand while using the DataContext.