Rafael Teixeira wrote:
That is because interest in the ODBC provider is low, as using
specific providers is much better
(performance/easy-of-use/easy-of-debugging wise).
When an application wants to interoperate with multiple databases
simultaneously or when you want to migrate between differe
Look at
http://www.mono-project.com/Database_Access
:)
On 8/10/05, Alfredo Jose Muela Romero <[EMAIL PROTECTED]> wrote:
> El Wed, 10 Aug 2005 11:29:46 -0300
> Rafael Teixeira <[EMAIL PROTECTED]> escribió:
>
> > That is because interest in the ODBC provider is low, as using
> > specific provider
El Wed, 10 Aug 2005 11:29:46 -0300
Rafael Teixeira <[EMAIL PROTECTED]> escribió:
> That is because interest in the ODBC provider is low, as using
> specific providers is much better
> (performance/easy-of-use/easy-of-debugging wise).
>
> What server are you using that possibly doesn't have a prop
That is because interest in the ODBC provider is low, as using
specific providers is much better
(performance/easy-of-use/easy-of-debugging wise).
What server are you using that possibly doesn't have a proper ADO.NET
provider implemented? Currently PostgreSQL, MySQL, Firebase, MS SQL
Server, Oracl
Hello,
I've been looking for doc about System.Data.Odbc trough
http://www.go-mono.com/docs/ and I have found none... I don't
see this as a bug but I thought it may be useful to say it.
Regards,
Alfredo.
___
