Actually putting the <@assign> within the results
of the search action adds overhead.
the
default of a search action is to place the results in into a variable called
"resultSet" of scope Local/Request
adding
the <@assign> was so that you could move the data in the resultSet
variable into another variable because you had no control over the name, so any
subsequent Search action would write over the data from the previous search
action.
So by
placing the Name there you do not have to do the <@assign> within the
results.
that
is if you don't need the data to be scoped differently
this resultSet naming issue has been a long
standing request for change. This is the first attempt to deal with it. I
am sure as With gets feedback on this they will adjust.
Ben Johansen - http://www.pcforge.com
-Authorized WiTango
Reseller
http://www.pcforge.com/WitangoGoodies.htm
-Authorized Alt-N
Reseller
http://www.pcforge.com/AltN.htm
-----Original Message-----I have a question based on the discussion in this thread. It has been discussed many times that performing an operation using a meta tag is more efficient than performing the same operation using an action. For example, using <@ASSIGN NAME='foobar' VALUE='10' SCOPE=USER> is more efficient than using an Assign action.
From: Steve Smith [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 24, 2003 5:45 PM
To: [EMAIL PROTECTED]
Subject: Re: Witango-Talk: Dynamic ResultSet Naming
What about using the resultSet that is part of the Search action vs. using an <@ASSIGN> within the results of the same Search action. Which is more efficient?
Just curious,
Steve Smith
Oakbridge Information Solutions
Office: (519) 624-4388
GTA: (416) 606-3885
Fax: (519) 624-3353
Cell: (416) 606-3885
Email: [EMAIL PROTECTED]
Web: http://www.oakbridge.ca
On Tuesday, June 24, 2003, at 06:56 PM, Bryan Hughes wrote:
I started out by, and what I ultimately want to work, entering static and dynamic information in the Name field for the resultSet of my search action:
ResultSet Name=staticinfo_<@VAR request$dynamicinfo[@@request$moredynamicinfo,1]>
In my debugging and experimenting trying to get it to work I used an assign action to create a single variable for the name of the new variable:
Assign request$service= staticinfo_<@VAR request$dynamicinfo[@@request$moredynamicinfo,1]>
Resultset Name=<@VAR request$service>
But this still doesn't seem to work.
This was just an exercise to prove that any variable will not be resolved to it's value in the resultSet name field.
For now I'm just assigning the resultSet to "resultSet" then assigning that variable to a new one with the naming convention I originally wanted.
But now this isn't very streamline as now I have two variables with the exact same content. There are plenty of work a rounds to this problem. It just seemed to me that in just about every other place in the editor I can have a dynamic name except here.
On Tuesday, June 24, 2003, at 05:56 PM, Eric Weidl wrote:
Although you say you don't want to "create the name variable", according to my reading of your message, you are.
My understanding is that you want to name a resultSet according to the name in the variable <@VAR request$service>. Is that so?
Eric
At 09:31 AM 6/24/2003, you wrote:
That works, but as I said in my first post
<QUOTE>
I'd rather not have to create the name variable and I'd rather not have to give the resultSet a static name then rename it in a following action.</QUTOE>
On Tuesday, June 24, 2003, at 11:24 AM, Harpreet Matharu wrote:
try this</blockquote></x-html>
<@ASSIGN NAME="service" VALUE="<@VAR RESULTSET>" SCOPE="request">
in the search results html page.
-----Original Message-----
From: Bryan Hughes [<mailto:[EMAIL PROTECTED]>mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 24, 2003 9:21 AM
To: [EMAIL PROTECTED]
Subject: Witango-Talk: Dynamic ResultSet Naming
I am trying to dynamically name a search actions result set in a for loop.
The name of the resultSet (request$service) is assigned before the search action.
I name the search action resultSet varible "<@VAR request$service>" under the Output Variable Properties tab of the search action.
I get the following error when running the page:
An error occurred while processing your request:
File: run.eo
Position: Search_salon_subs_services
Class: Internal
Main Error Number: -52
The name of the result set variable cannot have a scope specifier
<@VAR request$service>
When I use "@@request$service" instead of "<@VAR request$service>" i get:
Error
An error occurred while processing your request:
File: run.eo
Position: Search_salon_subs_services
Class: Internal
Main Error Number: -52
The name of the result set variable cannot have a scope specifier
salon_service_Makeup
I'd rather not have to create the name variable and I'd rather not have to give the resultSet a static name then rename it in a following action.
Can I not dynamically assign resultSet names?
________________________________________________________________________
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
