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

InMemory: Enable joins between sources which have client eval #21200

Closed
smitpatel opened this issue Jun 10, 2020 · 1 comment
Closed

InMemory: Enable joins between sources which have client eval #21200

smitpatel opened this issue Jun 10, 2020 · 1 comment
Labels
closed-out-of-scope This is not something that will be fixed/implemented and the issue is closed. customer-reported punted-for-6.0 punted-for-7.0 Originally planned for the EF Core 7.0 (EF7) release, but moved out due to resource constraints.

Comments

@smitpatel
Copy link
Contributor

Spun off from #17763 & #19247
Part of broader issue #20291

@ajcvickers ajcvickers added this to the Backlog milestone Jun 12, 2020
@ajcvickers ajcvickers modified the milestones: Backlog, 6.0.0 Nov 5, 2020
@smitpatel smitpatel removed this from the 6.0.0 milestone Sep 3, 2021
@ajcvickers ajcvickers added type-enhancement priority-bug Issues which requires API breaks and have bigger impact hence should be fixed earlier in the release punted-for-6.0 and removed type-bug labels Sep 3, 2021
@ajcvickers ajcvickers added this to the Backlog milestone Sep 4, 2021
@ajcvickers ajcvickers modified the milestones: Backlog, 7.0.0 Nov 3, 2021
@ajcvickers ajcvickers added propose-punt punted-for-7.0 Originally planned for the EF Core 7.0 (EF7) release, but moved out due to resource constraints. and removed propose-punt labels Jul 6, 2022
@ajcvickers ajcvickers modified the milestones: 7.0.0, Backlog Jul 7, 2022
@smitpatel smitpatel removed their assignment Sep 14, 2022
@ajcvickers ajcvickers added propose-close closed-out-of-scope This is not something that will be fixed/implemented and the issue is closed. and removed type-enhancement propose-close area-in-memory priority-bug Issues which requires API breaks and have bigger impact hence should be fixed earlier in the release labels Oct 20, 2022
@ajcvickers
Copy link
Member

We recommend against using the in-memory provider for testing--see Testing EF Core Applications. While we have no plans to remove the in-memory provider, we will not be adding any new features to this provider because we believe valuable development time is better spent in other areas. When feasible, we plan to still fix regressions in existing behavior.

@ajcvickers ajcvickers closed this as not planned Won't fix, can't repro, duplicate, stale Oct 26, 2022
@ajcvickers ajcvickers removed this from the Backlog milestone Oct 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-out-of-scope This is not something that will be fixed/implemented and the issue is closed. customer-reported punted-for-6.0 punted-for-7.0 Originally planned for the EF Core 7.0 (EF7) release, but moved out due to resource constraints.
Projects
None yet
Development

No branches or pull requests

2 participants