Using EF only for Insert/Update/Delete and SQL for Querying

296 Views Asked by At

Anyone has experience of using/developing a Data Access model which uses Entity Framework only for Insert/Update/Delete and raw SQL for Reading/Querying purposes. If any, how was your experience, what are the pros and cons for such a Data Access Model.

Or do you know any open source projects that i can have inspiration which uses such a Data Access model.

P.S: By using raw SQL for querying, I dont mean using DataTables in Business Layers but, querying and creating DTO classes that maps the result of the query.

0

There are 0 best solutions below