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

DbContext: Require name for "persistent" in-memory database and add explicit API for creating transient database #7482

Closed
ajcvickers opened this issue Jan 25, 2017 · 1 comment
Closed

DbContext: Require name for "persistent" in-memory database and add explicit API for creating transient database #7482

ajcvickers opened this issue Jan 25, 2017 · 1 comment
Labels
breaking-change closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Milestone
2.0.0

Comments

@ajcvickers
Copy link
Member

We see this being asked for a lot and we could make the break for 2.0.
@ajcvickers
Copy link
Member Author

Discussed this in the design meeting and decided:

  • Will require a name for persistent databases
  • Will add a new method (or otherwise change the API) to create a transient database
  • We may obsolete the existing API, or we may just make a clean break

@ajcvickers ajcvickers self-assigned this Jan 26, 2017
@ajcvickers ajcvickers added this to the 2.0.0 milestone Jan 26, 2017
ajcvickers added a commit that referenced this issue Feb 21, 2017
@ajcvickers
Force named in-memory databases and add new API for using transient d…
ebaf263 
…atabase

Issue #7482
@ajcvickers ajcvickers mentioned this issue Feb 21, 2017
Merged
@ajcvickers ajcvickers changed the title Consider making in-memory database transient by default Require name for "persistent" in-memory database and add explicit API for creating transient database Feb 22, 2017
ajcvickers added a commit that referenced this issue Feb 23, 2017
@ajcvickers
Force named in-memory databases and add new API for using transient d…
5e22532 
…atabase

Issue #7482
ajcvickers added a commit that referenced this issue Feb 28, 2017
@ajcvickers
Force named in-memory databases and add new API for using transient d…
e3ae9fd 
…atabase

Issue #7482
ajcvickers added a commit that referenced this issue Mar 1, 2017
@ajcvickers
Force named in-memory databases and add new API for using transient d…
13a0c32 
…atabase

Issue #7482
ajcvickers added a commit that referenced this issue Mar 1, 2017
@ajcvickers
Force named in-memory databases and add new API for using transient d…
ef675e4 
…atabase

Issue #7482
@ajcvickers ajcvickers added the closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. label Mar 1, 2017
@ajcvickers ajcvickers changed the title Require name for "persistent" in-memory database and add explicit API for creating transient database DbContext: Require name for "persistent" in-memory database and add explicit API for creating transient database May 9, 2017
@ajcvickers ajcvickers mentioned this issue May 16, 2017
Closed
@ajcvickers ajcvickers mentioned this issue Jun 21, 2017
Closed
25 tasks
@ajcvickers ajcvickers modified the milestones: 2.0.0-preview1, 2.0.0 Oct 15, 2022
@ajcvickers ajcvickers removed their assignment Sep 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
breaking-change closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Projects
None yet
Milestone
2.0.0
Development

No branches or pull requests
1 participant
@ajcvickers