If you look at the logic that builds the search arg logic you will see the section:
<@ROWS ARRAY=arg_names>
<@ASSIGN arg_name "<@COL 1>" SCOPE=LOCAL>
<@IF "'<@LEFT @@arg_name 1>' != '_'">
<@COMMENT> Ignore args beginning with '_'; they'll be passed manually.</@COMMENT>
You may be upsetting this logic by changing _function to function
<P><@COMMENT>
----- BEGIN NEXT/PREV BUTTONS -----
</@COMMENT>
<@IF "<@MAXROWS> > 0">
<@COMMENT>
If a max. number of records was specified, show Next and/or Previous buttons.
</@COMMENT>
<@COMMENT>
----- BUILD SEARCH VALUES -----
The Next and Previous buttons must pass to Tango all the search values entered by the user. This
section loops through all the args received -- via form fields (postargs) and the URL (searchargs) --
and creates hidden form fields for them. The resulting HTML is used in the form for each button.
</@COMMENT>
<@ASSIGN arg_names <@ARGNAMES> SCOPE=LOCAL>
<@ASSIGN search_vals_HTML "" SCOPE=LOCAL>
<@ASSIGN crlf "<@CHAR 13><@CHAR 10>" SCOPE=LOCAL> <@COMMENT>line ending</@COMMENT>
<@ROWS ARRAY=arg_names>
<@ASSIGN arg_name "<@COL 1>" SCOPE=LOCAL>
<@IF "'<@LEFT @@arg_name 1>' != '_'">
<@COMMENT> Ignore args beginning with '_'; they'll be passed manually.</@COMMENT>
<@ASSIGN arg_values "<@ARG @@arg_name TYPE=ARRAY>" SCOPE=LOCAL>
<@COMMENT>
Assign the current argument's values to a variable. Use
TYPE=ARRAY to get all the values for multi-select lists.
</@COMMENT>
<@ROWS ARRAY=arg_values>
<@COMMENT>
Loop through all the values for the current arg. Build a hidden form field for each.
Append field HTML to existing HTML.
</@COMMENT>
<@ASSIGN search_vals_HTML '@@search_vals_HTML<INPUT TYPE="HIDDEN" NAME="<@VAR arg_name>" VALUE="<@COL 1>">@@crlf' SCOPE=LOCAL>
</@ROWS>
</@IF> <@COMMENT>End ignoring args beginning with _ </@COMMENT>
</@ROWS>
<@COMMENT>
----- END BUILD SEARCH VALUES -----
</@COMMENT>
On 29/7/03 10:06 PM, "Ted Wolfley" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I noticed that there is a real drop off in speed is when displaying webpages
> after page 9, no matter what the number of records is being retrieved is.
> So I am going to limit the search results to 9 pages by dividing the total
> number of records by 9 and putting that answer in a variable to use in the
> Limit To: box on the Results tab in the Search Action.
>
> Ted
>
> -----Original Message-----
> From: Web Dude [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 28, 2003 4:55 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Witango-Talk: Search reterivial follow up
>
>
> I have found the same result as Ben when using the search builder. In
> fact, if you turn debug on you can see the variables being loaded.
> If you have 500 items and list only 2 per page, then start scrolling
> through the pages, you will notice that the variable
> local$search_vals_HTML keeps appending <input type="HIDDEN"
> Name="function" value="list"> After scrolling through 10 pages of
> lists you end up with....
>
> local$search_vals_HTML=<input type="HIDDEN" Name="function"
> value="list"> <input type="HIDDEN" Name="function" value="list">
> <input type="HIDDEN" Name="function" value="list"> <input
> type="HIDDEN" Name="function" value="list"> <input type="HIDDEN"
> Name="function" value="list"> <input type="HIDDEN" Name="function"
> value="list"> <input type="HIDDEN" Name="function" value="list">
> <input type="HIDDEN" Name="function" value="list"> <input
> type="HIDDEN" Name="function" value="list"> <input type="HIDDEN"
> Name="function" value="list"> <input type="HIDDEN" Name="function"
> value="list"> <input type="HIDDEN" Name="function"
> value="list"><input type="HIDDEN" Name="function" value="list"><input
> type="HIDDEN" Name="function" value="list"><input type="HIDDEN"
> Name="function" value="list"> <input type="HIDDEN" Name="function"
> value="list"> <input type="HIDDEN" Name="function" value="list">
> <input type="HIDDEN" Name="function" value="list"> <input
> type="HIDDEN" Name="function" value="list"> <input type="HIDDEN"
> Name="function" value="list"> <input type="HIDDEN" Name="function"
> value="list"> <input type="HIDDEN" Name="function" value="list">
> etc. etc. etc. etc.
>
> If you have 1000 records and are try to display 5 per page, it can
> get extrmely slow. Pretty soon it can take minutes for the next list
> to display. Has anyone else found this? I just noticed it when doing
> some testing...
>
> Does anyone have a work around for this?
>
>
>
>> Witango is taking the results and placing them in a variable (file on
>> server) and then starting at 1 counting to 100 and sending that to the
>> browser. This works very quickly, but as you get farther away from
>> record 1 it takes longer to sequentially count down the file.
>>
>> Ben Johansen - http://www.pcforge.com
>> Authorized Witango Reseller http://www.pcforge.com/WitangoGoodies.htm
>> Authorized MDaemon Mail Server Reseller http://www.pcforge.com/AltN.htm
>>
>>
>> -----Original Message-----
>> From: Ted Wolfley [mailto:[EMAIL PROTECTED]
>> Sent: Monday, July 28, 2003 12:02 PM
>> To: '[EMAIL PROTECTED]'
>> Subject: Witango-Talk: Search reterivial follow up
>>
>>
>> I just ran an experiment with about 50,000 records, retrieving 1000 at
>> a time. I had the same results so it isn't the quantity of records,
>> it's when page 10 + (10,000+ records) is retrieved.
>>
>> Anyone have any ideas?
>>
>> Ted
>> -----Original Message-----
>> From: Ted Wolfley [mailto:[EMAIL PROTECTED]
>> Sent: Monday, July 28, 2003 2:10 PM
>> To: '[EMAIL PROTECTED]'
>> Subject: Witango-Talk: Search reterivial
>>
>>
>> Hi,
>>
>> In a search action, I am retrieving 1949 records in alphabetical order,
>> 100 records at a time. The first 1000 records (10 web pages) are
>> returned quickly. It is after the 1000 record that performance goes
>> down hill with
>> each sequential page taking longer. Does any one know why this would
>> be
>> happening and how to improve performance?
>>
>> Ted
>> _______________________________________________________________________
>> _
>> TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
>> ________________________________________________________________________
>> TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
>>
>> _______________________________________________________________________
>> _
>> TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
>
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
