On Wed, Jul 3, 2013 at 12:36 PM, HERNAN MARTINEZ FOFFANI
<[email protected]> wrote:
> I have a wrapper class that abstracts some layers and on some database
> engines (I don't remember which one, it might be SQLServer) if you call
> Close() on a command whose reader weren't consumed the Close() keeps
> reading the records up to the end. So as a sanity measure I added a Cancel()
That might be a lot of wasting, in case of huge resultset and blobs.
> in the Dispose() method of the wrapper.
>
> I've just modified the wrapper and instead of calling Cancel() unconditionally
> it first check if the DataReader was consumed or not and only cancel if it
> wasn't.
That's first step. ;)
--
Jiri {x2} Cincura (x2develop.com founder)
http://blog.cincura.net/ | http://www.ID3renamer.com
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Firebird-net-provider mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
