On 2/26/08, Aitor Gómez González <[EMAIL PROTECTED]> wrote:
> Is there any reason to return an incorrect result instead of raising a
> NotSupportedException?
I have not designed this. But according to ADO.NET abstract classes
and "expected" way of using this, I think, is this implemented as it
is.
Maybe throwing exception is better from architecture POV, but change
this now will create huge breaking-change, and this is probably
impossible.
--
Jiri {x2} Cincura (CTO x2develop)
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Firebird-net-provider mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
