100%(8)8 out of 8 people found this document helpful
This preview shows page 6 - 12 out of 29 pages.
3.1 Object Relational Impedance Mismatch
3.2 Object Relational Mapper lets you query and manipulate data from a database using an object-oriented paradigm3.2 Advantages and disadvantages of ORMadvantagesdisadvantagesEasy input sanitizationMight cause performance issuesThere is no need to write SQLThere is a learning curve to learn itAllows the use of OOP conceptsObject Oriented Impedance MismatchFits the natural way of coding Leaky abstractions3.3 Entity Framework APIEntity Framework API (EF6 & EF Core) includes the following abilities:3.3.1 EF Architecture:
3.3.2 Context Class in Entity Framework3.4 An Entity in the EF and States1. Is a class in the domain of your application2. two types of properties:Scalar PropertiesNavigation Properties3. The entity state represented by an enum System.Data.Entity.EntityState in EF 6and Microsoft.EntityFrameworkCore.EntityState in EFCore with the following values:3.5 Querying in Entity Framework1.Entity framework supports three types of queries:LINQ-to-EntitiesEntity SQLNative SQL2.Eager Loading or Lazy Loading4. Database approach4.1 Database First Approach: database is created first using Data Definition Language, so writing SQL first
4.2 Model First Approach: Visual Designer is used or the model is mapped out via XML configuration files, so ERD fisrt4.3 Code First Approach: This is when Code (C# classes) are written or created)5. Conceptual model from your domain classesThere are two ways to configure your domain classes:Data Annotation Attributes(System.ComponentModel.DataAnnotations, System.ComponentModel.DataAnnotations.Schema)Fluent API6. Inheritance Strategy Overview
6.1 Table per Hierarchy (TPH)6.2 Table per Type (TPT)6.3 Table per Concrete Type (TPC)
You've reached the end of your free preview.
Want to read all 29 pages?
.NET Framework, Representational State Transfer, ASP.NET MVC, validation error messages
, Take Down Request