Re: Shopping with Accounts
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 48307
interpreted = N
texte = I use the same names for several reasons ... first it's easy to pass and stuff values with variables of the same name formatted __shiptoaddress1 for example, and second it's easier to remember exactly what data you're dealing with when you have multiple databases. Another reason I do this is that the code becomes much more portable as in an HTML form for billing and shipping info.For me it's much easier than trying to remember all the unique or arbitrary header names you thought you'd created in the first place to avoid this confusion. You'll end up with lots of databases for various tasks, tracking, billing, promo, whatever, the list just keeps growing, and you'll save yourself a lot of headaches by developing a standard for header and variable names.Just an opinion ... some will disagree.On Tuesday, March 4, 2003, at 09:49 AM, Clint Davis wrote:> I use separate names to avoid confusion. > > > > On 3/4/03 11:43 AM, Kimberly D. Walls
wrote: > >> I am looking for direction here... >> >> When you have a shopping site, where the shoppers' information (name, >> address, etc.) are stored in a database... do most of you use the same >> fieldnames to match the orderfile or not? For example, in the account >> database, should I use shiptoaddress1 or should I use >> address1ship? I >> can see how using the same names would save confusion, but at the >> same time, >> I can see how it would create confusion... any feedback or opinion on >> this? >> >> Thanks, >> KimSigned: Marc Kaiwi ------------------------------------------------------------- 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 use the same names for several reasons ... first it's easy to pass and stuff values with variables of the same name formatted __shiptoaddress1 for example, and second it's easier to remember exactly what data you're dealing with when you have multiple databases. Another reason I do this is that the code becomes much more portable as in an HTML form for billing and shipping info.For me it's much easier than trying to remember all the unique or arbitrary header names you thought you'd created in the first place to avoid this confusion. You'll end up with lots of databases for various tasks, tracking, billing, promo, whatever, the list just keeps growing, and you'll save yourself a lot of headaches by developing a standard for header and variable names.Just an opinion ... some will disagree.On Tuesday, March 4, 2003, at 09:49 AM, Clint Davis wrote:> I use separate names to avoid confusion. > > > > On 3/4/03 11:43 AM, Kimberly D. Walls wrote: > >> I am looking for direction here... >> >> When you have a shopping site, where the shoppers' information (name, >> address, etc.) are stored in a database... do most of you use the same >> fieldnames to match the orderfile or not? For example, in the account >> database, should I use shiptoaddress1 or should I use >> address1ship? I >> can see how using the same names would save confusion, but at the >> same time, >> I can see how it would create confusion... any feedback or opinion on >> this? >> >> Thanks, >> KimSigned: Marc Kaiwi ------------------------------------------------------------- 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/
marc@kaiwi.com (Marc Kaiwi)
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:
[WebDNA] cron - curl to replace triggers.. (2009)
Showif Context combined with Search (1997)
DB Size - MAX (2004)
Newbie questions (1999)
Max Record length restated as maybe bug (1997)
https validation (2001)
OT: javascript help (2003)
Re:[off] Promotions Co? (1997)
Parsing args without ? (2003)
RE: Symantec VIsual Page 1.0.3 (1997)
Database changes (1998)
form data submission gets truncated (1997)
WebMerchant Only reads 1.4 order files error (1997)
Where is eudora plugin? (1998)
X etc.... (1999)
Re[2]: 2nd WebCatalog2 Feature Request (1996)
Text Area - Line Breaks (1998)
Java and WebDNA (2002)
PCS Frames (1997)
[ModDate] & [ModTime] ? (1997)