Re: MetaKW tags from databases
This WebDNA talk-list message is from 2006
It keeps the original formatting.
numero = 67149
interpreted = N
texte = WJ Starck wrote: > I would parse the results into a table or a temp.db first, then search > that and append a fieldnamesumm=T onto the end of the search for those > fields you want to summarize which will factor out all your duplicates. > > If I'm understanding the question, I believe this is what you are after. Thanks, but I'm afraid that solution won't work in this case. One problem is the sheer volume. We're talking tens of thousands of page hits per day, each requiring a new table/temp file. That can be fixed if I can find a hundred percent reliable way to separate search spider visits from "real" hits but I'm not sure that's possible. Although most spiders are easily identifiable, I have this feeling some of them are cloaked as regular visitors. Another problem is that the fields that need to be summerised aren't single word fields. Something like this is not unlikely: Field1: value1 value2 value3 value1 value4 value1 Field2: value4 value3 value5 value6 Field3: value7 value1 value1 value2 So how do I get WebDNA to turn that into: value1 value2 value3 value4 value5 value6 value7 Frank Nordberg http://www.musicaviva.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:
WJ Starck wrote: > I would parse the results into a table or a temp.db first, then search > that and append a fieldnamesumm=T onto the end of the search for those > fields you want to summarize which will factor out all your duplicates. > > If I'm understanding the question, I believe this is what you are after. Thanks, but I'm afraid that solution won't work in this case. One problem is the sheer volume. We're talking tens of thousands of page hits per day, each requiring a new table/temp file. That can be fixed if I can find a hundred percent reliable way to separate search spider visits from "real" hits but I'm not sure that's possible. Although most spiders are easily identifiable, I have this feeling some of them are cloaked as regular visitors. Another problem is that the fields that need to be summerised aren't single word fields. Something like this is not unlikely: Field1: value1 value2 value3 value1 value4 value1 Field2: value4 value3 value5 value6 Field3: value7 value1 value1 value2 So how do I get WebDNA to turn that into: value1 value2 value3 value4 value5 value6 value7 Frank Nordberg http://www.musicaviva.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/
Frank Nordberg
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:
Re:Copyright ? (1997)
[WebDNA] Webdna and CMS (2012)
searching a range mea culpa (2000)
Protect (1997)
2.1b3 --> way slow (1997)
rotating thumbnails (1997)
Weird bug, or is there something amiss? (1997)
WebCat2b13MacPlugIn - [shownext method=post] ??? (1997)
delete some html code (2007)
Nested tags count question (1997)
Checkbox question (1997)
Almost a there but..bye bye NetCloak (1997)
Okay, I give up... (1999)
[WebDNA] triggers.db "next execute" fails to update (2012)
RE: Submitting ampersands in forms... (1998)
Resolving variables into field names (1998)
Drop Down Menus (2002)
ShipCost Data Base (1998)
WebCat2: Items xx to xx shown, etc. (1997)
Date Formats (1997)