advertisement

Article:
  Transparent Database Access with ADO.NET
Subject:   Can't be done
Date:   2003-03-02 18:06:20
From:   anonymous2
Still can't do this like JDBC. As already pointed out, parameter binding changes between data providers. Another one that will bite you is transactions. In SqlClient, you need to bind the transaction to each command. In ODP.NET command doesn't even have the methods to do this. According to their documentation, transactions are per connection and don't work like SqlClient. If you're doing select * from table where without bound parameters or transactions, you're ok. If not, you still need to recode for each DB type.
Full Threads Oldest First

Showing messages 1 through 2 of 2.

  • Can't be done
    2003-04-30 22:43:29  anonymous2 [Reply | View]

    yeah, i face the same problem with you. when we use IDbDataAdapter, we will lost many nice OverLoading method of "Fill". we left only IDbDataAdapter.Fill(DataSet)...... :(
    that's mean we cant Fill in DataTable, we cant Fill DataTable with a name....etc.
    • Can't be done
      2003-05-02 09:47:01  anonymous2 [Reply | View]

      you can get around this by writing your own overloaded versions. (Not great but works)

      Ie. MyDBAccess.Fill(IDbDataAdapter aDataAdapter, DataSet aDataSet, string aTableName)

      etc and determining the db used inside this function.
      works quite well really.

      bj