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

Give me info about the current provider #19

Open
MikaelEliasson opened this issue Jan 9, 2015 · 1 comment
Open

Give me info about the current provider #19

MikaelEliasson opened this issue Jan 9, 2015 · 1 comment

Comments

@MikaelEliasson
Copy link

When writing extensions for EF it's actually incredibly hard to find out what DB engine is being used. You end up checking the connection which is a problem if that is wrapped because of things like profiling. (Don't get me started on what I feel about the IConnection design)

Simply being able to get the info about the db or the provider being used would solve this.

@FransBouma
Copy link
Owner

This should indeed be possible without a lot of hoops.

I've planned to factor out the DB engines, I don't think they'll be placed in different assemblies, as they'll use DbProviderFactory. Additionally, there will be compatibility modes, so the engine can be set into compatibility mode X so it will generate SQL matching the DBs of vX, e.g. compatibility mode for SQL server 2005 or 2008 or 2012. So combined this info should give you what you want. Though in general I think this should be taken into account for extensibility points to the engine: it's of no use if data is available but there are no ways to extend the engine to begin with ;).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants