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

Use Case: Multiple Databases with the Same Code #238

Closed
Grauenwolf opened this issue Feb 9, 2020 · 4 comments
Closed

Use Case: Multiple Databases with the Same Code #238

Grauenwolf opened this issue Feb 9, 2020 · 4 comments
Assignees
Labels
Use Case Proposal Proposed use case.

Comments

@Grauenwolf
Copy link
Contributor

Demonstrate accessing both SQL Server and PostgreSQL using the same code.

@Grauenwolf Grauenwolf added the Use Case Proposal Proposed use case. label Feb 9, 2020
@Grauenwolf Grauenwolf self-assigned this Feb 9, 2020
Grauenwolf added a commit that referenced this issue Feb 9, 2020
ADO, EF Core, Chain
Untested
Grauenwolf added a commit that referenced this issue Feb 9, 2020
Grauenwolf added a commit that referenced this issue Feb 11, 2020
Partial fix for EF Core.
@Grauenwolf
Copy link
Contributor Author

@FransBouma
Copy link
Collaborator

Is a good scenario as it's used a lot in practice. And I should be able to support this without lifting a finger too :)

@mikependon
Copy link
Collaborator

I liked this too :)

@Grauenwolf
Copy link
Contributor Author

I've got the tests written, but I've got a little bit of work left to do for EF Core. But I can comment that out and just push the tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Use Case Proposal Proposed use case.
Projects
None yet
Development

No branches or pull requests

3 participants