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.

Sign up for GitHub

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

Jump to bottom

Allow empty constructor as well as DbContextOptions constructor when using pooled DbContext #25390

Open
ajcvickers opened this issue Aug 2, 2021 · 1 comment
Open

Allow empty constructor as well as DbContextOptions constructor when using pooled DbContext #25390

ajcvickers opened this issue Aug 2, 2021 · 1 comment
Labels
area-dbcontext type-enhancement
Milestone
Backlog

Comments

@ajcvickers
Copy link
Contributor

#24124 allowed this for DbContextFactory, but pooling scenarios still require exactly one constructor. We should be able to relax this while still using the correct constructor.
@ajcvickers ajcvickers added this to the Backlog milestone Aug 3, 2021
@ajcvickers
Copy link
Contributor Author

Note: this may require changes in D.I. before it will work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-dbcontext type-enhancement
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
1 participant
@ajcvickers