It's just like Scott says. Attempts are made to pass the bounds of the queries to the ODBC layer. Almost always this results in a repetition of the original query, and then certain rows are "fetched" from the result set. This isn't a very DB-friendly way to page through a large result set.
If you're more concerned about taxing your database than you are about using up memory, you can put your resultSet in a user var and hop around on it. See http://wildernessagency.com/~jparker/tango-examples/sortabletable.taf On Wed, 25 Sep 2002, Scott Cadillac wrote: > Hi Mark, > > From what I've always understood, the information you pass into the 'Limit > to:' and 'Start retrieval at row number:' goes directly into your ODBC or > database Client Drivers, which then control and limit the data returned by > the database. This is not happening at the same layer as the SQL statements > so you don't see anything in the debug. > > So as far as I understand it, the extra data you potentially could be > returning - is not returned to the Witango Server and therefore not > typically a performance hindrance. The database is another matter of course > :-) > > Hope this helps. Cheers... > > > > ----- Original Message ----- > From: "Mark Weiss Vancouver" <[EMAIL PROTECTED]> > To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]> > Sent: Wednesday, September 25, 2002 11:18 PM > Subject: Witango-Talk: What is really happening? > > > Hello All. > > What is really happening in Tango when you are using a "next 50 Matches" > button and the results tab says begin retrieval at <@ARG _start>? > > I don't see anything in the debug that says that the SQL has changed. > > So is Tango returning the entire string and then doing some kind of parsing > of the result set behind the scenes? > > > Thanks for your help. > > > Mark Weiss > Coolcontent.com > If you always do what you�ve always done, you�ll always get what you�ve > always got. > > Anonymous > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
