I've been using the System.Data; namespace, and in one place I have a factory for connections that dips into the more specific namespace (in this case .SqlClient)...
Everything's worked out so far, but I haven't needed, nor had the opportunity to try it out on a different DB. Anyone run into any issues using this technique and going from SqlServer to Oracle, or even the TDS wrapper to OleDb ? ~Phill -----Original Message----- From: Joel Mueller [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 30, 2002 3:24 PM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] How are you supporting multiple DB vendors? I'm sure there is variation, but the architecture I described isolates that variation from the rest of the application, while still allowing one to code specifically for the database one is targeting. For example, one might support Oracle with OleDb at first, then switch to using the native Oracle provider when it comes out of beta - the rest of the code in the application doesn't have to know or care. > -----Original Message----- > From: dotnet discussion [mailto:[EMAIL PROTECTED]] > On Behalf Of Murphy, James > Sent: Tuesday, April 30, 2002 4:52 PM > To: [EMAIL PROTECTED] > Subject: Re: [DOTNET] How are you supporting multiple DB vendors? > > > > Have you found any variation in invoking stored procedures > accross DB vendors? If so how do you select the right > strings? Or does populating a OleDbCommand with parmaater > objects handle it? Do you use the OleDbCommand.CommandText property? > > Jim > > You can read messages from the DOTNET archive, unsubscribe > from DOTNET, or subscribe to other DevelopMentor lists at > http://discuss.develop.com. > > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
