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 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 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.
2008/2/28, Jiri Cincura <[EMAIL PROTECTED]>: > On 2/28/08, Dean Harding <[EMAIL PROTECTED]> wrote: > > Instead of just returning true, couldn't you just attempt to fetch the > > first row? If there's no row, you can return false. If there's a row, > > you'll fetch it (and you'll have to cache it so the first call to > > MoveNext() works) and return true. > > > Yes. This is one of possibilities. It's better than exception. Please > add this to tracker, I'll look at it and add it if possible. > > I hope during weekend releasing next Alpha version of provider and other > stuff. ------------------------------------------------------------------------- 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
