Re: Lookups
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 30551
interpreted = N
texte = In general page design, I approach [Search] as the rule and [Lookup] as theexception. If I need to retrieve more than 1 or 2 fields from a secondarydatabase, I try and rewrite the page to use two nested [Search] contexts.We had a site built by a contractor who was used to SQLServer and they used[Lookup] for every single field from every database. It made me completely nutsto see all that duplicated code so I spent about a half a day rewriting thecode. The only troublesome page was one which could be called in an impliedsearch context from two different databases (Authors and Books). I am still nothappy with that one; YMMV.Hope this helpsJohn Peacock____________________Reply Separator____________________Subject: Lookups Author:
(WebCatalog Talk)Date: 4/15/2000 12:56 PMWhat is the maximum lookups you experts would put in a page before it wouldbe better to do a search?I have a product detail page that brings back information about the rep thathas consigned the item, I have first name, last name, address1, address2,city, state, zip, tel, fax. Is it better(faster) to do a lookup for each oris it better(faster) to do one nested search?This may be more opinion than anything, but in the pursuit of ever moreefficient code I would like to get some feedback.Paul Fowler-------------------------------------------------------------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:
In general page design, I approach [search] as the rule and [lookup] as theexception. If I need to retrieve more than 1 or 2 fields from a secondarydatabase, I try and rewrite the page to use two nested [search] contexts.We had a site built by a contractor who was used to SQLServer and they used[lookup] for every single field from every database. It made me completely nutsto see all that duplicated code so I spent about a half a day rewriting thecode. The only troublesome page was one which could be called in an impliedsearch context from two different databases (Authors and Books). I am still nothappy with that one; YMMV.Hope this helpsJohn Peacock____________________Reply Separator____________________Subject: Lookups Author: (WebCatalog Talk)Date: 4/15/2000 12:56 PMWhat is the maximum lookups you experts would put in a page before it wouldbe better to do a search?I have a product detail page that brings back information about the rep thathas consigned the item, I have first name, last name, address1, address2,city, state, zip, tel, fax. Is it better(faster) to do a lookup for each oris it better(faster) to do one nested search?This may be more opinion than anything, but in the pursuit of ever moreefficient code I would like to get some feedback.Paul Fowler-------------------------------------------------------------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
jpeacock@univpress.com
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:
[ModDate] & [ModTime] ? (1997)
Calculating multiple shipping... (1997)
Where is f2? (1997)
Out of the woodwork (2007)
Running _every_ page through WebCat ? (1997)
Email template names (1997)
all records returned. (1997)
update on wn searching (1997)
Forms Search Questions (1997)
StoreBuilder: cart is full (2003)
Reversed words (1997)
Another option (2005)
A question on sub-categories (1997)
New Website with Redakto CMS (2003)
killing white space (1998)
displaying New products (using [date]) (1997)
Searching for more than one catagory (2000)
Public beta 4 of WebCatalog 4.0 is now available (2000)
Webcat/Webmerchant part II (1998)
webcatalog 3.0 upgrade (1998)