Database-SQL-data-provider

Hi Erich,

It's hard to believe it but it's true :) We don't have a Database provider for WL7 yet because our manpower is limited and the backlog grows every day. Here's the wish list which doesn't even include many of the backlog items for extensions (such as "restore the Database provider"):

https://www.wealth-lab.com/wishlist

I've tagged your topic as #FeatureRequest so now it's in the queue, too!

In the WL6 version, a very convenient feature was that whatever database client the user installed on his machine was made available to the DB provider automatically. Whether he or she installed a commercial driver for MySQL or most recommended driver for PostreSQL, WL6 would pick it up and start creating a DataSet:
http://www2.wealth-lab.com/WL5WIKI/DatabaseProvider.ashx

It appears that in .NET Core we no longer can list all database clients installed on the machine because such global configuration is missing in this platform. So, potential WL7 provider cannot be this user-friendly anymore:
https://stackoverflow.com/questions/52007836/dbproviderfactories-getfactoryclasses-returns-no-results-after-installing-net-s

Just thinking out loud.

Hey everyone who voted for this request - since this is nearing the top of the Wish List we are looking for inspiration. What are you looking for out of a SQL Data Provider for WL7??

We're retiring this Request for the following reasons ...

1. Everyone will have their own DB schema
2. There's been little support here on the forum, no one answered my last call
3. Recent changes to .NET Core make it impossible to create a "generic" DB provider

... if anyone's interested in something more concrete, feel free to submit a new request.

Followup discussion moved to:
https://www.wealth-lab.com/Discussion/Read-static-data-and-live-quotes-from-file-7348

I'm interested in building a dataset provider extension that utilizes a database as a data source. It may take a bit to get up to speed, but the linked articles are helpful to see how the pre-WL7 feature was set up using ADO.net. Also noted that we need to register a factory for each provider before using the GetFactoryClasses method in .Net Core (not ideal). My focus is on SQL Server, but as I do some testing, I'll keep in mind that others will want to use other rdbm systems.

I just finished a Concierge job for another user who needed to access some indicator data from a SQL database. So it’s definitely doable.

@Paul, my legacy provider automatically detected any supported .NET driver installed in Windows by a RDBMS. It did use DbProviderFactory but you didn't have to register a factory by hand if this is what you mean.

Makes sense. Thank you. I'm starting with a basic design that will support only SQL Server. So far, I have a data provider extension working with hard coded sample data. I'm currently working on wiring this up to a local SQL instance.