On 2/28/08, Aitor Gómez González <[EMAIL PROTECTED]> wrote:
> I think it's a good idea but don't know if it's feasible (record size,
> fetch caching, performance, etc.), reality is "we can live without
I have roughly looked into code for some implementation. It shouldn't
be huge change. We can try it in 2.5 Alpha X versions, so if somebody
is interested in, create ticket in tracker.
> reader.HasRows()". About the breaking change, do you really think is
> anybody relying on a method that always return true? And if it was the
Not always. From some time it returns true only for selects. But it
cannot be changed in a second, no matter how it's now, some people are
used to have this as it's now.
> case, it shoud be better (my opinion) declaring the method as not
> supported and forcing people to clean (fix) their current code. By
> the way, FbCommand.Cancel is a similar case, a NotSupportedException
> is thrown instead of leaving the method empty.
Well, I haven't made this decision. But for Cancel, we cannot do
something inteligent, 'cause it's not working (the functionality) at
all. And it's not the base function. But the HasRows is used in many
common scenarios and examples, so I think, that was the reason not to
throw exception and return some "fake" value.
--
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
