New database provider list #632
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
divega
commented
Feb 24, 2018
| > EF Core providers are built by a variety of sources. Not all providers are maintained as part of the Entity Framework Core project. When considering a provider, be sure to evaluate quality, licensing, support, etc. to ensure they meet your requirements. Also make sure you review each provider's documentation for detailed version compatibility information. | ||
|
|
||
| | NuGet Package | Supported database engines | Maintainer / Vendor | Notes | Useful links | | ||
| |:------------------------------------------------------------------------------------------------------------------|:---------------------------|:------------------------------------------------------------------------------|:----------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| |
There was a problem hiding this comment.
This markdown table is read-optimized. It should be easier to review it using two screens 😄
divega
force-pushed
the
new-database-provider-list
branch
from
430c0de
to
235c3a1
Compare
|
@mairaw this PR removes some low-value pages from the EF Core docs. Ideally they would all redirect to providers/index.md. Anything I need to do? |
|
@mairaw FWIW, it appears that the pages don't get removed, at least in the preview site. |
|
@mairaw I think I got how to do the redirects now, but feel free to review the master redirect file. |
fix typo (from PR#630)
divega
force-pushed
the
new-database-provider-list
branch
from
8ee109d
to
596fdd7
Compare
ajcvickers
reviewed
Feb 26, 2018
| @@ -12,7 +12,7 @@ uid: core/providers/in-memory/index | |||
| --- | |||
| # EF Core In-Memory Database Provider | |||
|
|
|||
| This database provider allows Entity Framework Core to be used with an in-memory database. This is useful when testing code that uses Entity Framework Core. The provider is maintained as part of the [EntityFramework GitHub project](https://github.com/aspnet/EntityFramework). | |||
| This database provider allows Entity Framework Core to be used with an in-memory database. This is useful when testing code that uses Entity Framework Core. The provider is maintained as part of the [Entity Framework Core Project](https://github.com/aspnet/EntityFrameworkCore). | |||
There was a problem hiding this comment.
Maybe "This can be useful for testing, although the SQLite provider in in-memory mode may be a more appropriate test replacement for relational databases."
ajcvickers
reviewed
Feb 26, 2018
| The Oracle .NET team has announced they are planning to release a first-party provider for EF Core 2.0 approximately in the third quarter of 2018. See their [statement of direction for .NET Core and Entity Framework Core](http://www.oracle.com/technetwork/topics/dotnet/tech-info/odpnet-dotnet-ef-core-sod-4395108.pdf) for more information. | ||
| Please direct any questions about this provider, including the release timeline, to the [Oracle Community Site](https://community.oracle.com/). | ||
|
|
||
| In the meanwhile, the EF team has produced a [sample EF Core provider for Oracle databases](https://github.com/aspnet/EntityFrameworkCore/blob/dev/samples/OracleProvider/README.md). The purpose of the project is not to produce an EF Core provider owned by Microsoft, but to help us identify gaps in EF Core's relational and base functionality which we need to address in order to better support Oracle, and to jumpstart the development of other Oracle providers for EF Core either by Oracle or third parties. |
There was a problem hiding this comment.
Maybe add "We would welcome and encourage a community effort to create an open-source Oracle provider for EF Core, using the sample as a starting point."
ajcvickers
approved these changes
Feb 26, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #472
Fixes #378