Re: Sorting by highest number of matches unique to a field
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 52140
interpreted = N
texte = I've just seen the end of this thread and have always wanted a [summnumfound] when searching and doing a summ=T Seems this would help a lot in this situation as well .. ? So [search db=mydb.db&neFIELDdata=find_all&FIELDsumm=T] [founditems] [field] : [sumnumfound] [/founditems] [/search] This would be quite easy to resort this data without a whole lot more nested searches .. Alain >> Glenn, thanks, but that won't work for my situation. It still doesn't put >> the highest number of results in order. The example you provided would sort >> the results of each group. I need a listing of summarized groups with the >> most per group listed first. (god, I'm confusing myself now). Besides, >> you're talking about nesting about 3,000 searches there. Yikes. >> > > If you can't find a code solution to solve your problem, you have a serious > problem with the data being used. > > Your options are > 1- Write code to sort the existing data as you want, even if it requires more > than one search > 2- Revise the db to include a field that contains data that will let you sort > as you want > 3- Write a new db that keeps metadata about the existing db that can be sorted > as you want. > > Pick one and go for it. > > Glenn > > > ------------------------------------------------------------- > 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://webdna.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://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
I've just seen the end of this thread and have always wanted a [summnumfound] when searching and doing a summ=T Seems this would help a lot in this situation as well .. ? So [search db=mydb.db&neFIELDdata=find_all&FIELDsumm=T] [founditems] [field] : [sumnumfound] [/founditems] [/search] This would be quite easy to resort this data without a whole lot more nested searches .. Alain >> Glenn, thanks, but that won't work for my situation. It still doesn't put >> the highest number of results in order. The example you provided would sort >> the results of each group. I need a listing of summarized groups with the >> most per group listed first. (god, I'm confusing myself now). Besides, >> you're talking about nesting about 3,000 searches there. Yikes. >> > > If you can't find a code solution to solve your problem, you have a serious > problem with the data being used. > > Your options are > 1- Write code to sort the existing data as you want, even if it requires more > than one search > 2- Revise the db to include a field that contains data that will let you sort > as you want > 3- Write a new db that keeps metadata about the existing db that can be sorted > as you want. > > Pick one and go for it. > > Glenn > > > ------------------------------------------------------------- > 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://webdna.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://webdna.smithmicro.com/
Alain Russell
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 Solutions ... sorry! (1997)
Database Strategy - more... (1998)
A Global Variable (1997)
Note added to [sendmail] in Docs (2004)
How To question on setting up downloads (1997)
WC2.0 Memory Requirements (1997)
linetiems in thankyou.tpl (1997)
Emailer Timing out (1999)
Initiating NewCart (1997)
FW: 2.01 upgrade problems (1997)
Credit card processing - UK (1997)
Single Link browsing (1997)
security (https) w webcat (1999)
Logging purchases (1997)
[protect] on NT? (1997)
taxRate is fine but taxTotal isn't (1997)
WebCat2b15MacPlugin - [protect] (1997)
Comments in db? (1997)
The word TYPE in search contexts and fields (1998)
New servers and new inline cache (1997)