Re: [WebDNA] Enhancements to "list" contexts ...
This WebDNA talk-list message is from 2015
It keeps the original formatting.
numero = 111838
interpreted = N
texte = Very nice concept Ken :) Regards Stuart Tremain IDFK Web Developments AUSTRALIA webdna@idfk.com.au > On 3 Jan 2015, at 11:46 pm, Kenneth Grome
= wrote: >=20 > Hi Chris, >=20 > You asked for our suggestions to improve WebDNA. Here are a few > of my thoughts (with more to come in later posts): >=20 > - Since [formvariables] and [listfiles] both offer the optional > parameters "name=3Dxxx&exact=3DT/F" as a way to limit what they find, > it would be nice to have the same optional parameters in a few of > our other "list" contexts too, such as: >=20 > listmimeheaders > listvariables > listdatabases > listfields > listcookies >=20 > - For all contexts that offer the "name=3Dxxx&exact=3DT/F" options, a > new "opposite=3DT" parameter would be useful when we want to return > the opposite results. >=20 > - Sorting options would be useful in these list contexts, too. We > already use these sort options in our searches, so adding them to > our list contexts would keep the syntax consistent: >=20 > asnamesort=3D1/2/3/etc. > denamesort=3D1/2/3/etc. > assizesort=3D1/2/3/etc. > desizesort=3D1/2/3/etc. > asmoddatesort=3D1/2/3/etc. > demoddatesort=3D1/2/3/etc. >=20 > BY THE WAY, TO GET REALLY SERIOUS ABOUT THIS KIND OF ENHANCEMENT: >=20 > Just add an optional "search=3DT" parameter to all our list > contexts. This would tell WebDNA to recognize the same parameters > we already use in our regular database/table searches. This would > allow us to do things like this: >=20 > [listfiles > = path=3D/to/server/logs/&search=3DT&bwnamedatarq=3Derror.log&gemoddatedatar= q=3D12/21/2014&moddatetype=3Ddate&gesizedatarq=3D1200000&assizesort=3D1&as= moddatesort=3D2] >=20 > Obviously this is a far more powerful enhancement than simply > adding the "name=3Dxxx&exact=3DT/F" and "opposite=3DT" parameters to = our > list contexts, and for this reason it may be a little "too much". > But it would definitely make the WebDNA syntax more consistent > across all contexts that create lists. >=20 > - Another thought I have is to add a new [notfound] context to our > searches. This would list all the database/table records that are > not listed in the [founditems] context. Would this feature be > useful to anyone other than me? >=20 >=20 > Happy New Year everyone! >=20 > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Management > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
Very nice concept Ken :) Regards Stuart Tremain IDFK Web Developments AUSTRALIA webdna@idfk.com.au > On 3 Jan 2015, at 11:46 pm, Kenneth Grome = wrote: >=20 > Hi Chris, >=20 > You asked for our suggestions to improve WebDNA. Here are a few > of my thoughts (with more to come in later posts): >=20 > - Since [formvariables] and [listfiles] both offer the optional > parameters "name=3Dxxx&exact=3DT/F" as a way to limit what they find, > it would be nice to have the same optional parameters in a few of > our other "list" contexts too, such as: >=20 > listmimeheaders > listvariables > listdatabases > listfields > listcookies >=20 > - For all contexts that offer the "name=3Dxxx&exact=3DT/F" options, a > new "opposite=3DT" parameter would be useful when we want to return > the opposite results. >=20 > - Sorting options would be useful in these list contexts, too. We > already use these sort options in our searches, so adding them to > our list contexts would keep the syntax consistent: >=20 > asnamesort=3D1/2/3/etc. > denamesort=3D1/2/3/etc. > assizesort=3D1/2/3/etc. > desizesort=3D1/2/3/etc. > asmoddatesort=3D1/2/3/etc. > demoddatesort=3D1/2/3/etc. >=20 > BY THE WAY, TO GET REALLY SERIOUS ABOUT THIS KIND OF ENHANCEMENT: >=20 > Just add an optional "search=3DT" parameter to all our list > contexts. This would tell WebDNA to recognize the same parameters > we already use in our regular database/table searches. This would > allow us to do things like this: >=20 > [listfiles > = path=3D/to/server/logs/&search=3DT&bwnamedatarq=3Derror.log&gemoddatedatar= q=3D12/21/2014&moddatetype=3Ddate&gesizedatarq=3D1200000&assizesort=3D1&as= moddatesort=3D2] >=20 > Obviously this is a far more powerful enhancement than simply > adding the "name=3Dxxx&exact=3DT/F" and "opposite=3DT" parameters to = our > list contexts, and for this reason it may be a little "too much". > But it would definitely make the WebDNA syntax more consistent > across all contexts that create lists. >=20 > - Another thought I have is to add a new [notfound] context to our > searches. This would list all the database/table records that are > not listed in the [founditems] context. Would this feature be > useful to anyone other than me? >=20 >=20 > Happy New Year everyone! >=20 > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Management > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Stuart Tremain
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:
Problem with updating 2.1b7 -> 2.1.1 (1998)
Lost and Recovered. (1998)
Multiple security dbs (1997)
Shipping Calculation Problem (1997)
WebCat2b12 - nesting [tags] (1997)
WebDNA deletes major DB data big time (2004)
Why do extra quotation marks sometimes appear in my databases? (1998)
About WebDNA (2006)
[WebDNA] Feature Request: [returnhtml] (2016)
I forgot (1998)
[append] vs. [appendfile] delta + question? (1997)
Pithy questions on webcommerce & siteedit (1997)
[WebDNA] WebDNA glitch, no response required ... (2009)
BIG PROBLEMS with Checkboxes!!! (1998)
Replace Statement (1997)
Date search - yes or no (1997)
Search returns all, not 20 (1997)
[WebDNA] END processing (2014)
Sorting by date (1997)
Fwd: 502 Bad Gateway (1998)