Re: SMSI -- a [notfound] context?
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 41105
interpreted = N
texte = > If I understand your concept above you would be able to add unmatched> records to the found set, but that essentially alters the> found set.The 'found' set would contain only those records that did not match thesearch query.> -----Original Message-----> From: WebCatalog Talk> [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf> Of Alex McCombie> Sent: Monday, July 01, 2002 12:54 PM> To: WebCatalog Talk> Subject: Re: SMSI -- a [notfound] context?>>> On 7/1/02 1:40 PM, Larry Goodhew
wrote:>> > This would be fairly easy to implement. But it should> probably be qualified> > by> >> a new [search] parameter....[Search db=......&Unmatched=T]> then instead of a> >> new [NotFound] context, just use the existing [FoundItems]> context to display> >> the 'UnMatched' records. This way, other search> attributes and aggregates> >> could> >> still be applied.> >>> >> Thanks for the suggestion.> >>> >> Anyone else who is interested in this feature, please 'speak up'.>> I understand where you're headed with the unmatched=T but> then again, one of> the things lost is the ability to have a found set and then> an unfound set.>> If I understand your concept above you would be able to add unmatched> records to the found set, but that essentially alters the> found set. If on> the other hand my goal was to compare the found set to the> unfound set, it> wouldn't work for that...barring 2 searches and temp Dbs.>>> Thinking there would great use for:> Search> founditems> /founditems> notfound> /notfound> /search>>>>>>> Alex J McCombie New World Media> Chief Information Officer Drawer 607> 800/724.8973 Fair Haven, NY 13064> Alex@NewWorldMedia.com http://OurClients.com>> Interface Designer WebDNA Programmer Database Designer>>>> -------------------------------------------------------------> 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:
> If I understand your concept above you would be able to add unmatched> records to the found set, but that essentially alters the> found set.The 'found' set would contain only those records that did not match thesearch query.> -----Original Message-----> From: WebCatalog Talk> [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf> Of Alex McCombie> Sent: Monday, July 01, 2002 12:54 PM> To: WebCatalog Talk> Subject: Re: SMSI -- a [notfound] context?>>> On 7/1/02 1:40 PM, Larry Goodhew wrote:>> > This would be fairly easy to implement. But it should> probably be qualified> > by> >> a new [search] parameter....[Search db=......&Unmatched=T]> then instead of a> >> new [NotFound] context, just use the existing [founditems]> context to display> >> the 'UnMatched' records. This way, other search> attributes and aggregates> >> could> >> still be applied.> >>> >> Thanks for the suggestion.> >>> >> Anyone else who is interested in this feature, please 'speak up'.>> I understand where you're headed with the unmatched=T but> then again, one of> the things lost is the ability to have a found set and then> an unfound set.>> If I understand your concept above you would be able to add unmatched> records to the found set, but that essentially alters the> found set. If on> the other hand my goal was to compare the found set to the> unfound set, it> wouldn't work for that...barring 2 searches and temp Dbs.>>> Thinking there would great use for:> Search> founditems> /founditems> notfound> /notfound> /search>>>>>>> Alex J McCombie New World Media> Chief Information Officer Drawer 607> 800/724.8973 Fair Haven, NY 13064> Alex@NewWorldMedia.com http://OurClients.com>> Interface Designer WebDNA Programmer Database Designer>>>> -------------------------------------------------------------> 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:
Friendly , quick 'security' check, please (2003)
Upgrading old WebCat Database Files (1997)
_ in front of field name (1998)
WebCat Error Log problem (2.0.1, acgi, Mac) (1997)
WebCatalog [FoundItems] Problem - AGAIN - (1997)
WebCat2b12 Mac.acgi--[searchstring] bug (1997)
Searching for OSX/Webstar installer for WebCat (2002)
Nested vs conditional (1997)
[OT] ISP Windows program (2005)
Webcat/Webmerchant part II (1998)
WebCat2b13MacPlugIn - [showif][search][/showif] (1997)
Me know logical no need Now totally OT (2002)
[WebDNA] Facebook Application - Custom Tab for Fan / Non-Fan (2011)
Couple of questions (1999)
WebCatalog2 Feature Feedback (1996)
Part Html part WebDNA (1997)
Timeout question .. (2003)
[sendmail] v. [writefile] (2000)
[WebDNA] [BULK] Web Merchant Authorize net issues (2011)
oops private message leaked into talk list (1997)