Re: Scoping rules in WebDNA 4.0
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 29348
interpreted = N
texte = On 21/3/00 12:25, Grant Hulbert said:>New syntax: >[math]x=12[/math] >[search db=blah] > [founditems] > [GetMathVar name=x] <-- retrieves math variable from explicit math >context > [GetFoundItemsVar name=x] <-- retrieves database field x from >enclosing [search] > [/founditems] >[/search]This still doesn't fix a related problem with nested searches on the same database. There is no way to refer to fields in the outer search.The tags above are also ugly, unless you think about them in GUI terms as < GetFoundItemsVar name=x>, which would be easy to edit.So my suggestion is to have named contexts, eg
then refer to items explicitly such as < GetFoundItemsVar name=myinnersearch:x>. Of course without a name, the old rules of nesting apply, inside out.Also I'd imagine a shorthand should be available such as [myinnersearch:x].WebCat could take a very small step toward being object-oriented! Thomas Wedderburn-Bisshop CIO, Woomera Net Solutions www.woomeranet.com.au Sydney, Australia Phone +61 2 9633 5048 fax +61 2 9633 5248 ############################################################# This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to To switch to the INDEX mode, E-mail to Send administrative queries to
Associated Messages, from the most recent to the oldest:
On 21/3/00 12:25, Grant Hulbert said:>New syntax: >[math]x=12[/math] >[search db=blah] > [founditems] > [GetMathVar name=x] <-- retrieves math variable from explicit math >context > [GetFoundItemsVar name=x] <-- retrieves database field x from >enclosing [search] > [/founditems] >[/search]This still doesn't fix a related problem with nested searches on the same database. There is no way to refer to fields in the outer search.The tags above are also ugly, unless you think about them in GUI terms as < GetFoundItemsVar name=x>, which would be easy to edit.So my suggestion is to have named contexts, eg then refer to items explicitly such as < GetFoundItemsVar name=myinnersearch:x>. Of course without a name, the old rules of nesting apply, inside out.Also I'd imagine a shorthand should be available such as [myinnersearch:x].WebCat could take a very small step toward being object-oriented! Thomas Wedderburn-Bisshop CIO, Woomera Net Solutions www.woomeranet.com.au Sydney, Australia Phone +61 2 9633 5048 fax +61 2 9633 5248 ############################################################# This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to To switch to the INDEX mode, E-mail to Send administrative queries to
Thomas Wedderburn-Bisshop
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:
Grant, please help me ... (1997)
Sandbox DB permissions (2005)
AppleScript question (1997)
partial credits (2003)
[WebDNA] User sessions - cookies only or cookies and a sessions.db? (2016)
ReplaceFoundItems (2006)
Re:listfiles-looking for slick solution (1997)
form data submission gets truncated (1997)
WebCat2b13 Mac plugin - [sendmail] and checkboxes (1997)
Date Calulation (1997)
Secure Server (1997)
[delete] problem (1997)
Using Plug-In while running 1.6.1 (1997)
Exclude by date - multiple (1997)
WAP (2000)
Problems getting parameters passed into email. (1997)
[WebDNA] Test - no messages since 9th of June 2009. (2009)
-tmp files (2000)
Secure server question (1997)
WebCatalog [FoundItems] Problem - LONG - (1997)