*Dood*  This is great.  I'd still love to find a natural way to resolve the
SQL dialect problem.  I'm favoring Dan's suggestion about storing all query
strings in DBMS flavored XML files and loading them at runtime.  I bet they
could be structured neatly...

Jim



> -----Original Message-----
> From: Justin Rudd [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, April 30, 2002 7:05 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [DOTNET] How are you supporting multiple DB vendors?
>
>
> > How am I expected to use this thing ?
>
> Two ways.
>
> 1.)You use OleDb for all your access losing the speed that
> you gain from the Sql managed provider.
>
> 2.)You can use my project :-)
> http://abstractadonet.sourceforge.net/
>
> I've wrapped almost everything so far.  All the wrappers
> throw a common exception (DataException for now).  In
> addition to that, I also have a Mock ADO.NET implementation
> for unit testing purposes.
>
> Justin Rudd
> http://www.pinetree-tech.com/
> http://radio.weblogs.com/0107260/
>
> 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.

Reply via email to