"Bill Dargel" <
[hidden email]> wrote in message
news:
[hidden email]...
> Just found that DBResultSet>>isEmpty isn't working right. The test is
> answering "numRows ~~ 0". This is backwards. The test for being empty
> should be "numRows == 0".
According to our bugs database, this should have been patched in release
4.01.4. There was no such version, and the fix was not carried forward into
5.0, even though it appears in the release notes. I've re-opened issue #300.
Once again, thanks.
Blair