Re: [WebDNA] Variable mystery
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 102639
interpreted = N
texte = Frank Nordberg wrote: > Here's a really weird puzzle. Can anybody explain how a variable can > work in a textstring but not in a search command? > > I was struggling with this command: > [SEARCH db=ads.db&woanKWdatarq=[PAGEKW]] > It should have shown two matches but came empty and it was soon obvious > that the [PAGEKW] variable was the problem. However, removing the > opening and edning square brackets: > SEARCH db=ads.db&woanKWdatarq=[PAGEKW] > showed the text string correctly with the variable replaced with the > right value. > > I eventually figured out what I did wrong (needed a [INTERPRET] context > for the variable definition earlier on the page) so the question isn't > why the search command didn't work but rather why the text string did. I > mean, a variable is either defined or not defined, isn't it? I had no > idea there was anything inbetween. what is the value of [PAGEKW] that breaks? btw, I've always used the rest of the appropriate parameters when dealing with 'word or' searches... &
Word=ww&wbrk=&type=num/date etc. Donovan -- Donovan D. Brooke PH/FAX: 1 (608) 770-3822 ---------------------------------------------- VP WebDNA Software Corporation 16192 Coastal Highway Lewes, DE 19958
Associated Messages, from the most recent to the oldest:
Frank Nordberg wrote: > Here's a really weird puzzle. Can anybody explain how a variable can > work in a textstring but not in a search command? > > I was struggling with this command: > [SEARCH db=ads.db&woanKWdatarq=[PAGEKW]] > It should have shown two matches but came empty and it was soon obvious > that the [PAGEKW] variable was the problem. However, removing the > opening and edning square brackets: > SEARCH db=ads.db&woanKWdatarq=[PAGEKW] > showed the text string correctly with the variable replaced with the > right value. > > I eventually figured out what I did wrong (needed a [interpret] context > for the variable definition earlier on the page) so the question isn't > why the search command didn't work but rather why the text string did. I > mean, a variable is either defined or not defined, isn't it? I had no > idea there was anything inbetween. what is the value of [PAGEKW] that breaks? btw, I've always used the rest of the appropriate parameters when dealing with 'word or' searches... &Word=ww&wbrk=&type=num/date etc. Donovan -- Donovan D. Brooke PH/FAX: 1 (608) 770-3822 ---------------------------------------------- VP WebDNA Software Corporation 16192 Coastal Highway Lewes, DE 19958
Donovan Brooke
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Limitations on fields? Server is crashing (1997)
Re:no [search] with NT (1997)
can anyone confirm this behavior? (2003)
RE: Sum of Quantities (1997)
Bug? (1997)
Problems appending to database (1997)
Weird happenings (1998)
[WebDNA] [OT] Talk list (2009)
Multiple SSL Keys (1998)
Separate SSL Server (1997)
Newbie needs advice to learn to use WebDNA (2003)
Sendmail Excel Attachment (2006)
[LOOKUP] (1997)
WebCat2 - many [carts] on one template page? (1997)
More to Expire (1998)
Browser Info.txt (1997)
Newbie Help Needed (1998)
how many users (2000)
Using Plug-In while running 1.6.1 (1997)
Credit card arrangement (2005)