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:

    
  1. Re: SMSI -- a [notfound] context? (Donovan 2002)
  2. Re: SMSI -- a [notfound] context? (Kenneth Grome 2002)
  3. Re: SMSI -- a [notfound] context? (Aaron Lynch 2002)
  4. Re: SMSI -- a [notfound] context? (Stuart Tremain 2002)
  5. Re: SMSI -- a [notfound] context? (Alex McCombie 2002)
  6. Re: SMSI -- a [notfound] context? (Scott Anderson 2002)
  7. Re: SMSI -- a [notfound] context? (John Peacock 2002)
  8. Re: SMSI -- a [notfound] context? (Gary Krockover 2002)
  9. Re: SMSI -- a [notfound] context? (Clayton Randall 2002)
  10. Re: SMSI -- a [notfound] context? (Larry Goodhew 2002)
  11. Re: SMSI -- a [notfound] context? (Scott Anderson 2002)
  12. Re: SMSI -- a [notfound] context? (Tim Robinson 2002)
  13. SMSI -- a [notfound] context? (Kenneth Grome 2002)
> 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:

Sorting by date (1997) DB Updates don't take (1998) Linux Orderfile Error (2002) Emails are Stuck (2003) validatin on NT (sorry for the dups and etc) (1998) [WebDNA] getting a cookie to expire (2015) SKU Question (1999) One more time (1997) Whats going on with my SERIAL NUMBER??? (1998) limiting found items (2001) Sendmail truncation in Eudora Clients (1998) [OT] Domain Name Scam (2000) Write file (2000) Emailer (WebCat2) (1997) Looping through all records (2000) form image (2000) Problems w/ heavy use of cart header fields? (1998) Merging databases (1997) FlushDatabase Suggestion (1998) Who's going to MacWorld? (1999)