Support Oracle / MySql / SqLite Databases
What are people's thoughts on this? Which is more important: Oracle, MySql or SqLite? Should the support be through custom Entity Framework-driven DataContexts or via automatic DataContexts?
Click Add Connection and ‘View More Drivers’
-
Anonymous commented
This may help, here is Linq to SQLite.
https://www.kellermansoftware.com/p-47-net-data-access-layer.aspx -
Anonymous commented
Joe Albahari
It looks like Kellerman Software has a MySQL LINQ Provider:
https://www.kellermansoftware.com/p-47-net-data-access-layer.aspx -
Anonymous commented
Joe Albahari
It looks like Kellerman Software has a MySQL LINQ Provider:
https://www.kellermansoftware.com/p-47-net-data-access-layer.aspx -
hapiec commented
I second the 'any 3rd party provider' option. I'd love to use LinqPad with Postgres (for those of you who don't know yet - Postgres has the best features of both MySQL and Oracle).
-
Ed Power commented
Why not start with System.Data.Sqlite? It supports LINQ and Entity Framework: http://sqlite.phxsoftware.com/
-
Pat Kujawa commented
MySQL
-
Salil commented
Oracle support would be great
-
Martin Kirk commented
MySQL is very well supported using the EntityFramework...
simply add Datacontext by DLL... there you go... very easy... i even think that Oracle is supported this way too, heck the EntityFramework supports Oracle + MySQL
http://www.hypertrends.com/Blog/post/2009/03/17/MySQL-with-Entity-Framework-in-NET35.aspx
-
Ben McCormack commented
I'm using Entity Framework to MySQL and it would be great to use LinqPad to query that database. Otherwise, I'm not going to really be able to use Linqpad :-(.
-
Lakario commented
MySQL support would be fantastic... My employer runs .NET solutions on MySQL and I have been using Entity Framework on one of my projects recently. I'd love to be able to load my EF context into LINQPad.
-
pthalacker commented
SqLite has a VS2008 provider that allows VS to create entity models from the database, so all one has to do is build the data context in VS and then LinqPad should be able to hook right up to it
-
Jason Short commented
How about just third party EF Providers? They all should be able to load dynamically using the EF interfaces, that was the whole point of EF.
Of course my vote is for VistaDB support (we are adding EF in the next release and LINQPad would be a great tool for our users).
-
chub commented
it would be nice to have oracle provider beside MS SQL
-
Tobias Twardon commented
Oracle Support would be great though its a widely used and highly sophisticated db-engine.
-
mckay.joe commented
The more backends you could support the better. MS Access should probably be right up there also.