Support method overloads for default parameters with Database first


When using Database first to generate a model from an existing database for stored procedures, only a single method call is generated that does not take into account default parameters the stored procedure may have. This effectively means there is no way to call mapped stored procedures without having to write the code by hand, negating the point of generating a model from the data
Closed Dec 5, 2016 at 11:32 PM by RoMiller
EF Team Triage: We are transitioning this project to GitHub (https://github.com/aspnet/EntityFramework6). As part of this transition we are bulk closing a large number of issues in order that our new issue tracker will accurately reflect the work that our team is planning to complete on the EF6.x code base.

Moving forwards, our team will be fixing bugs, implementing small improvements, and accepting community contributions to the EF6.x code base. Larger feature work and innovation will happen in the EF Core code base (https://github.com/aspnet/EntityFramework). Closing a feature request in the EF6.x project does not exclude us implementing the feature in EF Core. In fact, a number of popular feature requests for EF have already been implemented in EF Core (alternate keys, batching in SaveChanges, etc.).

This is a bulk message to indicate that this issue was closed and not ported to the new issue tracker. The reasons for not porting this particular issue to GitHub may include:
• It was a bug report that does not contain sufficient information for us to be able to reproduce it 
• It was a question, but sufficient time has passed that it's not clear that taking the time to answer it would provide value to the person who asked it 
• It is a feature request that we are realistically not going to implement on the EF6.x code base
Although this issue was not ported, you may still re-open it in the new issue tracker for our team to reconsider (https://github.com/aspnet/EntityFramework6/issues). We will no longer be monitoring this issue tracker for comments, so please do not reply here.


RoMiller wrote Jan 24, 2013 at 12:59 AM

EF Team Triage: We are only taking minimal changes to the designer in EF6 because we are still converting the code base to open source. We'll consider this bug for the next release.

moozzyk wrote Jan 24, 2013 at 5:36 PM

I wonder if we could just use default parameters instead of overloads.

MgSam wrote Jan 24, 2013 at 6:16 PM

@moozzyk The problem with that is that it's brittle. If the default parameters change in the database, the generated code would unknowingly be passing the old, wrong default parameters. It's more robust to just generate overloads in which the proc is called without those parameters for which there are defaults.

Upshon wrote May 30, 2013 at 11:58 AM

Surely if the SP Param is marked as Nullable and you pass in null as value when you execute the SP you just Pass DBNull.Value not null?

Misiu wrote Nov 2, 2016 at 2:37 PM

Any changes to this?