Mapping Stored Procedure in Entity Framework

Question

0.00/5 (No votes)

See more:

, +

Hi,
Is there any way to map single stored procedure for all (insert, update, delete) operations in Entity Framework. As far as i searched i found the ways of mapping individual proceures for each operation. But i have one procedure that does insert, update and delte with options. Pls help to accompish this task.
Thank U All

Posted 8-Jan-14 16:57pm

Divya RS

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Christian Graus · Answer 1 · 2014-01-08T17:04:00

Having one process that does it all, is a dumb design. It means passing in a parameter to tell it what to do, and having a lot more code than you need, in terms of when you edit it, for one task.

However, when you map to a proc in EF, you don't define what it DOES, you simply expose it as something you call. So, I think you're talking about one of the ( also ridiculous ) ASP.NET controls which you tell what methods to call for CRUD. You're better off taking more control than that, and if you do, if you must, can call the same proc in all instances, and pass in a parameter to tell it which operation you want.

I still think you're better off with one proc/one task though.