I emailed oterro Log files and an explanation of this problem to RBTI on Thursday or Friday. This morning, I saw the proof that the problem I described with SQL_MAX_ROWS has been fixed, and the fix will be in the official release of Oterro 3.0, "Real Soon Now."
It's amazing how well and how quickly things like this get repaired. All we have to do is document the problem in such a way that the development team can replicate the problem.
Bill
At 03:39 PM 3/11/2004, you wrote:
Following up for the benefit of Alan, Steve F, Chuck, and any other lurking R:Tango developers:
I know that Wayne is working on this issue with Oterro 3.0. A quick summary:
Witango search actions allow you to set your "Results" to be limited to "n" rows, and for results to be shown starting at row "x". This is used to enable results in html pages, with next/previous buttons. With the newest, most stable version of Witango server (build .065), however,Oterro returns the whole data set, not limited to stop at the "n"th row.
