Typed Datasets and Multiple Databases

[JoshLindenmuth]

Is there a way the strongly typed dataset wizard will create classes that are usable across multiple databases?

 

We are writing an application that can use Oracle, PostgreSQL, or Sql Server as the database. We have setup a DAL (using IDBConnection, IDBDataAdapter, etc.) to facilitate database portability. We can now use the DAL for all our database functions, which is great.

 

However, we can't figure out how we to utilize the auto-generated strongly typed dataset classes across multiple databases. Is it possible? Our app has 1000's of columns, so this would be a MASSIVE time saver vs. creating all the classes by hand or hand-writing all the SQL.

 

Thanks,

Josh

[AlexCode]

If I'm developing an isolated/specific application, I use a component from DevExpress called XPO that does exactly what you need.

 

It doesn't use ADO.net/Datasets/DataTables... nothing we're used to...

Used a structure of classes (XPObjects and XPCollections) that will represent Rows and Tables.

The DB is created automaticly (SQL, Access, MySQL, Oracle, Postgre,...)

 

-- // --

 

On another hand, I'm currently developing a dynamic DB-DS-DB syncronizer.

Simply explaining the way it's working right now, I can say that the user creates a generic DB schema and can syncronize it with the DB and create a DataSet from it. Along with the DS, the DataAdapters with all its commands (SELECT, INSERT, DELETE, UPDATE) are also created.

 

Last thing... DataSets, specially the auto-generated onesare quite static and won't allow what u need... you can pesist the schema there but you'll have to create the commands at runtime to interact with the DB

 

Alex :p