[lookup] vs. [search]

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 16524
interpreted = N
texte = Grant, what would you guess is the break-even point, in terms of speed and/or processing demands, between using a series of lookups and using a search context?Here's what I'm getting at. Let's say, for example, that I want to display some of the field data in a user's database record.Now, I can obviously do it more *easily* with a search context, especially when there's more than one or two fields values I want to display. The search syntax is just easier to write when there are more than a couple of field values to be retrieved from the same db record.But maybe I can use 10 or 20 lookups in place of that search, and maybe those lookups will display faster than if I had used an equivalent search context.I think a series of lookups would be faster, but only to a point. Because with too many lookups, the sheer number of those lookups will likely slow WebCat down more than a single search.So my question is this:What would you guess is the cutoff point where a search context actually becomes equally as fast as a series of lookups? Would that break-even point come when displaying data from 10 fields? 100 fields? 1000 fields? More?Or would it actually be faster to use a search whenever there are more than only one or two field values to display?Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net Associated Messages, from the most recent to the oldest:

    
  1. Re: [lookup] vs. [search] (Kenneth Grome 1998)
  2. Re: [lookup] vs. [search] (Grant Hulbert 1998)
  3. [lookup] vs. [search] (Kenneth Grome 1998)
Grant, what would you guess is the break-even point, in terms of speed and/or processing demands, between using a series of lookups and using a search context?Here's what I'm getting at. Let's say, for example, that I want to display some of the field data in a user's database record.Now, I can obviously do it more *easily* with a search context, especially when there's more than one or two fields values I want to display. The search syntax is just easier to write when there are more than a couple of field values to be retrieved from the same db record.But maybe I can use 10 or 20 lookups in place of that search, and maybe those lookups will display faster than if I had used an equivalent search context.I think a series of lookups would be faster, but only to a point. Because with too many lookups, the sheer number of those lookups will likely slow WebCat down more than a single search.So my question is this:What would you guess is the cutoff point where a search context actually becomes equally as fast as a series of lookups? Would that break-even point come when displaying data from 10 fields? 100 fields? 1000 fields? More?Or would it actually be faster to use a search whenever there are more than only one or two field values to display?Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net Kenneth Grome

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:

WC Database Format (1997) Database Upload (2000) SSL, WebSTAR, WebCatalog (1998) Nested tags count question (1997) RE: Cart Template (1997) database freeze (1997) pc (1997) WebCat Hosting (1998) WebCat editing, SiteGuard WAS:SiteAssociative lookup style? (1997) Webcat/Webmerchant (1998) OT pipe - was can webcat determine an image's pixel dimensions? (2000) Other then credit cards-how? (1997) wrong input values? (1997) search command (1999) WCS Newbie question (1997) Listing Words Backwords (2001) [protect] on NT? (1997) [listfiles] with max? (2000) Lost and Recovered. (1998) New Plug-in and Type 11 errors (1997)