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 the search 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 the search 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:
[WebDNA] Need to convert unix date? (2009)
Requiring that certain fields be completed (1997)
WebMerchant problem (1998)
ShowNext for method=POST (1997)
&FieldNametype=time unnecessary? (2000)
Re:no [search] with NT (1997)
Next X hits (1996)
RE: IIS 4 (1998)
Doctype (2004)
Errata: WCS Newbie question (1997)
Limiting user access to .tmpl files (1997)
FW: Large File Uploads Impact WebDNA Performance (IIS) (2003)
Showif for mulitple variations (1997)
[WebDNA] writefile (2009)
[WebDNA] An unknown error occured // Deadlock avoided (2011)
country of origin from IPADDRESS??? (2001)
[WebDNA] NoSQL: sharing some ideas (2013)
code to phantom spacing (2001)
[WebDNA] timeout tests with [tcpconnect] (2011)
can webcat create directories on NT? (1997)