Re: [lookup] speed sales pitch
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 53508
interpreted = N
texte = No prob on the phone number entry part... I figured I would either [grep] out all non-numeric chars in the [lookup] as you suggested, or force input in the way I need it ... I'll cross that bridge when/if I come to it.. that's not really my concern...my concern is with the speed of a [lookup] on a large .db...WOULD it slow down the server noticeably? (Assume the server is a good/fast one ... not interested in debating server specs/brands...maybe later :) )Thanks,-Dan------------------------------------------------------------http://www.StrongGraphicDesign.com(208) 319-0137 | Toll-free p/f 877-561-1656------------------------------------------------------------On Tue, 21 Oct 2003 11:12:12 -0500 Donovan Brooke
wrote:>I think you might have a problem with phone numbers. People enter them>in all sorts of ways. You would probably have to strip out all non-alpha>numeric characters before doing the lookup.>>I haven't dealt with 4 million records but if your going to use lookup>it is not really only one I think.>>I suppose you could do.>>[showif [UserEnteredPhone]=[lookup >db=customers.db&lookinfield=USER&value=[url][UserEnteredUser][/url]&returnfield=PHONE]]>[text multi=T]status=success&theID=[lookup >db=customers.db&lookinfield=USER&value=[url][UserEnteredUser][/url]&returnfield=ID][/text]>[/showif]>>(that's kindof two lookups with another search needed to grab user info)>"[UserEnteredPhone]" would have to be cleaned and "USER" would have>to be uppercased and have code to gaurantee its uniqueness.>(registration would have to uppercase "user" also)>>Donovan>>>>Dan Strong wrote:>>>A client has asked that I build his login scheme so that his clients' >>phone numbers are the password ...>>He was worried that this might bog down the server since he has '4 >>million' phone numbers (hey, that's what he said).>>>>I told him that the technique [lookup] I am using could handle this just >>fine as it is not, technically, 'searching' 4 million phone numbers at >>once, but rather 'looking for 1 phone number'.>>>>I know my explanation was simplistic, but any more detail would have >>been lost on him..>>>>Is my explanation basically true? Would 4 million (theoretically... I'm >>sure he was exagerating...) records bog down a [lookup]?>>>>Now onto explaining to him that phone number-based passwords are >>insecure... (if I know your name, chances are I know your phone number >>or can get it relatively easily...)>>>>TIA,>>>>-Dan>>-- > =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o> DONOVAN D. BROOKE> Eucalyptus Design> WWW Developer / Consultant> <-Web Development (specializing in eCommerce), ->> <-Graphic Design, and Pre-Press Consultation ->>> ADDRESS:> Donovan Brooke> DBA Eucalyptus Design> N2862 Summerville Park Rd.> Lodi, WI 53555>> PH:> 1.608.592.3567> email:> dbrooke(AT)euca.us> Web:> http://www.euca.us> =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o>>>------------------------------------------------------------->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:
No prob on the phone number entry part... I figured I would either [grep] out all non-numeric chars in the [lookup] as you suggested, or force input in the way I need it ... I'll cross that bridge when/if I come to it.. that's not really my concern...my concern is with the speed of a [lookup] on a large .db...WOULD it slow down the server noticeably? (Assume the server is a good/fast one ... not interested in debating server specs/brands...maybe later :) )Thanks,-Dan------------------------------------------------------------http://www.StrongGraphicDesign.com(208) 319-0137 | Toll-free p/f 877-561-1656------------------------------------------------------------On Tue, 21 Oct 2003 11:12:12 -0500 Donovan Brooke wrote:>I think you might have a problem with phone numbers. People enter them>in all sorts of ways. You would probably have to strip out all non-alpha>numeric characters before doing the lookup.>>I haven't dealt with 4 million records but if your going to use lookup>it is not really only one I think.>>I suppose you could do.>>[showif [UserEnteredPhone]=[lookup >db=customers.db&lookinfield=USER&value=[url][UserEnteredUser][/url]&returnfield=PHONE]]>[text multi=T]status=success&theID=[lookup >db=customers.db&lookinfield=USER&value=[url][UserEnteredUser][/url]&returnfield=ID][/text]>[/showif]>>(that's kindof two lookups with another search needed to grab user info)>"[UserEnteredPhone]" would have to be cleaned and "USER" would have>to be uppercased and have code to gaurantee its uniqueness.>(registration would have to uppercase "user" also)>>Donovan>>>>Dan Strong wrote:>>>A client has asked that I build his login scheme so that his clients' >>phone numbers are the password ...>>He was worried that this might bog down the server since he has '4 >>million' phone numbers (hey, that's what he said).>>>>I told him that the technique [lookup] I am using could handle this just >>fine as it is not, technically, 'searching' 4 million phone numbers at >>once, but rather 'looking for 1 phone number'.>>>>I know my explanation was simplistic, but any more detail would have >>been lost on him..>>>>Is my explanation basically true? Would 4 million (theoretically... I'm >>sure he was exagerating...) records bog down a [lookup]?>>>>Now onto explaining to him that phone number-based passwords are >>insecure... (if I know your name, chances are I know your phone number >>or can get it relatively easily...)>>>>TIA,>>>>-Dan>>-- > =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o> DONOVAN D. BROOKE> Eucalyptus Design> WWW Developer / Consultant> <-Web Development (specializing in eCommerce), ->> <-Graphic Design, and Pre-Press Consultation ->>> ADDRESS:> Donovan Brooke> DBA Eucalyptus Design> N2862 Summerville Park Rd.> Lodi, WI 53555>> PH:> 1.608.592.3567> email:> dbrooke(AT)euca.us> Web:> http://www.euca.us> =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o>>>------------------------------------------------------------->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/
"Dan Strong"
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:
Country & Ship-to address & other fields ? (1997)
WebCat2b14MacPlugIn - [include] doesn't hide the search string (1997)
WebCat2b13MacPlugIn - [include] doesn't allow creator (1997)
Looping Search Results - Duh! (2000)
FW: WebDNA-Talk searchable? (1997)
[SearchString] problem with [search] context (1997)
writing db to disk (1997)
Need relative path explanation (1997)
HTML Editors (1997)
Size limit for tmpl editor ? (1997)
Multiple catalog databases and showcart (1997)
related data (2003)
PC Auth Hub+Merchant (1998)
Https not showing products (2004)
PWS suffix mapping (2000)
RSS Feeds; basic info (2005)
Not really WebCat (1997)
WC2b15 - [HTMLx]...[/HTMLx] problems (1997)
Problem with Formulas.db (1998)
quantity minimum problem (1997)