Re: [lookup] speed sales pitch
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 53506
interpreted = N
texte = 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/
Associated Messages, from the most recent to the oldest:
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/
Donovan Brooke
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:
MATH TIME (1997)
Online reference (1997)
Semi OT: vbulletin and # viewing - how do that do that? (2003)
Adding insurance to an order, round 2 (2003)
Re[2]: Problem with new formvariables (2000)
Thanks for tips, more quest (1997)
E-mail Attachments (1997)
random within a specified range (2001)
NTbeta18 corrupted? (1997)
Seeking Better Display of results... (1997)
Redirect frame targets (1998)
CSS in HTML emails? (2003)
PARAMETER vs. OPERATOR (was The BUG is BACK ...) (1998)
back button loses cart (2000)
(1997)
Add a field to the error log? (1997)
WebDNA Solutions ... sorry! (1997)
Security Tip (1996)
Referrer problem - Truncation (1998)
multi-paragraph fields (1997)