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:
RedHat Linux glibc version 2.1.2 or higher required (2000)
Mac Lockup Problems (1998)
protect tag on NT IIS (1997)
[Sum] function? (1997)
TRAINING videos - Prove IT. (1998)
FYI: virus alert (1996)
Can't load tmpl files (1997)
[WebDNA] [OT] Sorry just some email issues (2018)
[isfile] ? (1997)
HTML Editors (1997)
WebCat2.0 acgi vs plugin (1997)
Realtime Transaction Processing (1999)
.hdr in older Vers. (2003)
Re[3]: 2nd WebCatalog2 Feature Request (1996)
New commands in Final candidate (1997)
still having shipCost.db Problem (1997)
Email Spam a bit of Hell (2004)
[isfile] ? (1997)
Wonderin' whats the way (1998)
Tab Charactor (1997)