[Mono-list] Swap out M$'s System.Data.SqlClient and substitute Mono's System.Data.SqlClient

Aleksandar Dezelin dezelin32@fastmail.fm
Fri, 17 Dec 2004 13:09:09 +0100


Daniel Morgan wrote:
> What kind of bugs are you getting?
> 
> Please create small re-createable test cases attached to a bug in Bugzilla.
> This is the only way these bugs will get fixed.  
> 
> http://bugzilla.ximian.com/
> 
> Just saying it's a "little big buggy" does not solve anything.
> 

Please use the latest SVN version of classes that you need, older 
versions had a giant bug regarding uniqueidentifer Null fields in M$ SQL 
Server.

Also, if you use the whole System.Data namespace from Mono, pay 
attention that ConnectionPool is working somewhat "different" than .NET 
implementation - when you reach the Max Pool Size limit it just locks 
the execution of your application until you manually call Close method 
of some of your Connections in the ConnectionPool - this is from my 
experience.

Actually I've used a whole System.Data namespace from Mono, compiled it 
with csc.exe and executed it under .NET 1.1 in my application instead of 
Microsoft System.Data becouse it didn't work under Mono CLR, trying to 
find what's cousing the crash of my application under Mono.



Cheers,
Aleksandar Dezelin

-- 
Linux is like wigwham - no windows, no gates, and apache inside...