Re: Correlating the record found with the fieldname
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 29914
interpreted = N
texte = on 4/3/2000 12:40 PM, Dennis J. Bonsall, Jr. at dbonsall@webbuilders.com wrote:> Is there any way that, when a record is found, I can figure out what > field in the database that record was found in? I have a database that > contains about 300 date fields in it, and I am doing a group search on > all the date fields at once. My customer wants to know what field the > matching date was found in, so she can determine what jobs need done, or > stages need complete. The search is suprisingly fast, but there are not > very many records yet. But, I don't know of any way to determine what > field the match was found in. Anyone got any pointers? > > Also, can I expect any performance troubles once this database gets > populated, especially on this particular search? The entire database > currently has 338 fields, and most of them are date fields, and I need > to search them all at once. Will this cause any problems? > > Thanks, > > Dennis > You might try using the [listfields] context to determine which field is getting the match.====== Untested ======= [search ...] [founditems] [text]record[index]=[listfields ...] [showif [interpret][[fieldname]][/interpret]=[url][searchstring][/url]] [fieldname], [/showif] [/listfields][/text] [/founditems] [/search] ========================(without the line breaks, of course)I think this would give you a list of text variables that were a comma delimited list of all the fieldnames that matched the search string.I would be curious to know how much of a performance hit this method would create, especially on a large database. When you get your db populated, let us know how it performs.Mike ------------------------------------------------------------- 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
Associated Messages, from the most recent to the oldest:
on 4/3/2000 12:40 PM, Dennis J. Bonsall, Jr. at dbonsall@webbuilders.com wrote:> Is there any way that, when a record is found, I can figure out what > field in the database that record was found in? I have a database that > contains about 300 date fields in it, and I am doing a group search on > all the date fields at once. My customer wants to know what field the > matching date was found in, so she can determine what jobs need done, or > stages need complete. The search is suprisingly fast, but there are not > very many records yet. But, I don't know of any way to determine what > field the match was found in. Anyone got any pointers? > > Also, can I expect any performance troubles once this database gets > populated, especially on this particular search? The entire database > currently has 338 fields, and most of them are date fields, and I need > to search them all at once. Will this cause any problems? > > Thanks, > > Dennis > You might try using the [listfields] context to determine which field is getting the match.====== Untested ======= [search ...] [founditems] [text]record[index]=[listfields ...] [showif [interpret][[fieldname]][/interpret]=[url][searchstring][/url]] [fieldname], [/showif] [/listfields][/text] [/founditems] [/search] ========================(without the line breaks, of course)I think this would give you a list of text variables that were a comma delimited list of all the fieldnames that matched the search string.I would be curious to know how much of a performance hit this method would create, especially on a large database. When you get your db populated, let us know how it performs.Mike ------------------------------------------------------------- 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
Mike Davis
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:
Summaries (1999)
Nested vs conditional (1997)
linetiems in thankyou.tpl (1997)
RE: MacFinder -- a new WebDNA web site (1998)
Setting up WebCatalog with Retail Pro data (1996)
The text on this page exceeds 1 MB in length error (2000)
Nested tags count question (1997)
Help with ShowNext (1998)
[WebDNA] Does not understand 'search' command? (2014)
Trouble with my database (1998)
Stopping a [Loop] in mid-stream ... (1997)
WebCat2 several catalogs? (1997)
PhotoMill -> PhotoMaster (1997)
Sorting by date (1997)
Force a number (1998)
Setting up the server (1997)
pop up building with summarize (1998)
Thanks for tips, more quest (1997)
4.0 image uploading /features (2000)
Using [random] (1999)