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

Ef core - Add Microsoft access to the list of supported databases #472

Closed
scottaddie opened this issue Sep 6, 2017 · 2 comments
Closed
Assignees
Labels
good first issue This issue should be relatively straightforward to fix.
Milestone

Comments

@scottaddie
Copy link
Member

Moved from dotnet/AspNetCore.Docs#4217. Filed by @bubibubi.

Is it possible to add EF core provider for Microsoft access (as for other 3rd parties providers)?

@divega
Copy link
Contributor

divega commented Sep 6, 2017

@bubibubi It depends on what you mean.

If you mean that you have a Microsoft Access database and you want a provider to exist for it, then that is a feature request and the question doesn't belong in any of the docs repos. I personally don't know of any EF Core provider for Microsoft Access and I don't think we would prioritize building it because we don't see demand for it.

If you meant that you know about the existence of such provider and you are confident that it works, then your question has now landed on the right repository. Feel free to send a PR to add it to the list or at least provide the information here on how to get it and how to learn more about it (the kind of information we have for other providers).

@bubibubi
Copy link

bubibubi commented Sep 7, 2017

@divega I meant your second option.

The source code is in this repository
https://github.com/bubibubi/EntityFrameworkCore.Jet
and you can find it also on nuget as
EntityFrameworkCore.Jet.
It supports all the EF features (also codefirst from database) but it can't handle complex queries and some data types (Jet can't).
(about PR is better I don't write in English for an 'official' documentation).

@ajcvickers ajcvickers added this to the 2.1.0 milestone Sep 18, 2017
@divega divega added the good first issue This issue should be relatively straightforward to fix. label Feb 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue This issue should be relatively straightforward to fix.
Projects
None yet
Development

No branches or pull requests

4 participants