Re: SMSI -- a [notfound] context?
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 41099
interpreted = N
texte = This would be fairly easy to implement. But it should probably be qualifiedby a new [search] parameter....[Search db=......&Unmatched=T] then insteadof a new [NotFound] context, just use the existing [FoundItems] context todisplay the 'UnMatched' records. This way, other search attributes andaggregates could still be applied.Thanks for the suggestion.Anyone else who is interested in this feature, please 'speak up'.> -----Original Message-----> From: WebCatalog Talk> [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf> Of Kenneth Grome> Sent: Sunday, June 30, 2002 11:44 PM> To: WebCatalog Talk> Subject: SMSI -- a [notfound] context?>>> SMSI,>> I asked Grant this question privately -- because he's the one who> programmed most of the webdna code. But he never replied to my> direct email inquiry, so I'm asking you now ...>> How difficult would it be to create a [notfound] tag that's used> inside a search context -- to list all the records in the db that are> not found by the search?>> My desktop Panorama database has this feature built into it. It is> very useful, and I can imagine situations where it would be useful on> the web as well.>> Since webdna uses the index values to identify the founditems, it> seems like it could be coded to easily identify the records that are> notfound as well, then it could list those records in a [notfound]> context ... right?>> Then instead of only being able to see the matching records, we could> also see the records that do not match -- on the same page if> necessary. This would be great for debugging, but it would also be> useful when we need to see the non-matching records along with the> matching ones, for example to quickly see what's in the db that> doesn't match the search parameters.>> What do you think?>>> Sincerely,> Kenneth Grome>> -------------------------------------------------------------> Kenneth Grome & Associates US-Asian Business Specialists> Philippine Business Office +63 (32) 255-6921> Primary Email Address owner@kengrome.com> Alternate Email Address kengrome@webdna.net> ------------------------------------------------------------->> -------------------------------------------------------------> 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> > Web Archive of this list is at: http://search.smithmicro.com/-------------------------------------------------------------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 Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
This would be fairly easy to implement. But it should probably be qualifiedby a new [search] parameter....[Search db=......&Unmatched=T] then insteadof a new [NotFound] context, just use the existing [founditems] context todisplay the 'UnMatched' records. This way, other search attributes andaggregates could still be applied.Thanks for the suggestion.Anyone else who is interested in this feature, please 'speak up'.> -----Original Message-----> From: WebCatalog Talk> [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf> Of Kenneth Grome> Sent: Sunday, June 30, 2002 11:44 PM> To: WebCatalog Talk> Subject: SMSI -- a [notfound] context?>>> SMSI,>> I asked Grant this question privately -- because he's the one who> programmed most of the webdna code. But he never replied to my> direct email inquiry, so I'm asking you now ...>> How difficult would it be to create a [notfound] tag that's used> inside a search context -- to list all the records in the db that are> not found by the search?>> My desktop Panorama database has this feature built into it. It is> very useful, and I can imagine situations where it would be useful on> the web as well.>> Since webdna uses the index values to identify the founditems, it> seems like it could be coded to easily identify the records that are> notfound as well, then it could list those records in a [notfound]> context ... right?>> Then instead of only being able to see the matching records, we could> also see the records that do not match -- on the same page if> necessary. This would be great for debugging, but it would also be> useful when we need to see the non-matching records along with the> matching ones, for example to quickly see what's in the db that> doesn't match the search parameters.>> What do you think?>>> Sincerely,> Kenneth Grome>> -------------------------------------------------------------> Kenneth Grome & Associates US-Asian Business Specialists> Philippine Business Office +63 (32) 255-6921> Primary Email Address owner@kengrome.com> Alternate Email Address kengrome@webdna.net> ------------------------------------------------------------->> -------------------------------------------------------------> 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> > Web Archive of this list is at: http://search.smithmicro.com/-------------------------------------------------------------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 Web Archive of this list is at: http://search.smithmicro.com/
Scott Anderson
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:
Auth.net and SIM (2003)
Repost: pulldown menu (2000)
Keep away (1997)
Site Builder & IE Mac (2004)
UPPERCASE (1997)
Odd linefeed problem (2003)
suggestion (1997)
SearchTitle Question (1998)
carriage returns in data (1997)
cart file creation (2003)
[isfile] ? (1997)
[searchString] (1997)
Customizing WebDelivery.html (1998)
Webstar 1.3.1 PPC (1997)
NetSplat and WebCat2 (1997)
SetHeader not Working (2006)
PixelPipe for Windows? (2003)
Frames and WebCat (1997)
Time Display from Database (1997)
How is it done? (1998)