Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Even more controversial: Allow creation of a DbCommand from an EF IQueryable #19335

Merged
merged 1 commit into from
Dec 18, 2019

Conversation

ajcvickers
Copy link
Member

Provides access to all the real parameter values, including facets. Should be executable.

However, pretty sure people will think this isn't a good idea...

Provides access to all the real parameter values, including facets. Should be executable.

However, pretty sure people will think this isn't a good idea...
@roji
Copy link
Member

roji commented Dec 17, 2019

This would be an alternative to #19334 rather than an addition, right?

I still don't find this very controversial :) A DbCommand can be seen as a tuple of SQL and parameters, which also happens to be directly executable. I like it. API-wise it's also a bit cleaner than #19334, where the parameters is an "out" parameter.

BTW it's good that this is restricted to relational - we should consider doing this regardless of whether we implement DbCommand or leave just query string.

@ajcvickers
Copy link
Member Author

@roji No, this is independent of #19334 which is not relational-specific (see Cosmos) and doesn't involve handling a disposable object.

@roji
Copy link
Member

roji commented Dec 17, 2019

Apologies, I meant to write above that I don't find this very controversial, but ended up writing the opposite.

@ajcvickers
Copy link
Member Author

@AndriySvyryd @smitpatel @roji @bricelam @maumar I think we agreed in the design meeting that we were going to to this. Can I get an approval?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants