Re: Sku numbers

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 11628
interpreted = N
texte = Just to add more complexity to this issue, I probably will encourage users to use the back button to return to an add_record.tmpl to add more records since for my application most of the information in the previous record will be needed in the next added record as well and they can just return to the previous page with that redundent info already filled and only re-key what is different in the newer record.But I agree with everyone that the Date=SKU scheme has a couple of flaws: the possible duplication of SKUs if two users enter records at the exact same second, and if the servers clock is reset to an earlier time AND a user enters a record at a time which synchronizes it to the second with a previously entered record.But I've found it useful to use the Date=SKU scheme from a database management standpoint because I can use one field for both SKU and date of record entry. What I might do is incorporate Ken's ideas for doing a [lookup] to verify that the date/sku value is indeed unique (thanks Ken) and if not respond with an error and return the user to a screen which would ask them to re-submit their record (and thus generating a newer/different Date value).I think the chances (at least in my application) of users entering records at the exact same second are extremely remote to begin with, and if I couple that with a unique SKU number lookup - I think I'd feel pretty comforatble with that.What do you guys think? -marty ____________________________________ | Marty Schmid | | -Artwerks- | | Design/Advertising/Web Publishing | | | | T. 619.274.5029 | | F. 619.274.5656 | | e-mail: marty@artwerks.com | |____________________________________| Associated Messages, from the most recent to the oldest:

    
  1. Re: Unique SKU Numbers (Joseph D'Andrea 2000)
  2. Re: Unique SKU Numbers (Kenneth Grome 2000)
  3. Re: Unique SKU Numbers (Glenn Busbin 2000)
  4. Re: Unique SKU Numbers (Glenn Busbin 2000)
  5. Re: Unique SKU Numbers (Aaron Chute 2000)
  6. Re: Unique SKU Numbers (Joseph D'Andrea 2000)
  7. Re: Unique SKU Numbers (Joseph D'Andrea 2000)
  8. Re: Unique SKU Numbers (Glenn Busbin 2000)
  9. Re: Unique SKU Numbers (Peter Ostry 2000)
  10. Re: Unique SKU Numbers (Joseph D'Andrea 2000)
  11. Re: Unique SKU Numbers (Clint Davis 2000)
  12. Re: Unique SKU Numbers (Derrick Puckett 2000)
  13. Re: Unique SKU Numbers (Joseph D'Andrea 2000)
  14. Re: Unique SKU Numbers (Glenn Busbin 2000)
  15. Re: Unique SKU Numbers (Nicolay Ramm 2000)
  16. Re: Unique SKU Numbers (Peter Ostry 2000)
  17. Re: Unique SKU Numbers (Joseph D'Andrea 2000)
  18. Unique SKU Numbers (Aaron Chute 2000)
  19. Re: Sku numbers (Kenneth Grome 1997)
  20. Re: Sku numbers (Marty Schmid 1997)
  21. Re: Sku numbers (Kenneth Grome 1997)
  22. Re: Sku numbers (Grant Hulbert 1997)
  23. Re: Sku numbers (Kenneth Grome 1997)
  24. Re: Sku numbers (Kenneth Grome 1997)
  25. Re: Sku numbers (Marty Schmid 1997)
  26. Re: Sku numbers (Kenneth Grome 1997)
  27. Re: Sku numbers (Marty Schmid 1997)
  28. Sku numbers (Grant Hulbert 1997)
Just to add more complexity to this issue, I probably will encourage users to use the back button to return to an add_record.tmpl to add more records since for my application most of the information in the previous record will be needed in the next added record as well and they can just return to the previous page with that redundent info already filled and only re-key what is different in the newer record.But I agree with everyone that the Date=SKU scheme has a couple of flaws: the possible duplication of SKUs if two users enter records at the exact same second, and if the servers clock is reset to an earlier time AND a user enters a record at a time which synchronizes it to the second with a previously entered record.But I've found it useful to use the Date=SKU scheme from a database management standpoint because I can use one field for both SKU and date of record entry. What I might do is incorporate Ken's ideas for doing a [lookup] to verify that the date/sku value is indeed unique (thanks Ken) and if not respond with an error and return the user to a screen which would ask them to re-submit their record (and thus generating a newer/different Date value).I think the chances (at least in my application) of users entering records at the exact same second are extremely remote to begin with, and if I couple that with a unique SKU number lookup - I think I'd feel pretty comforatble with that.What do you guys think? -marty ____________________________________ | Marty Schmid | | -Artwerks- | | Design/Advertising/Web Publishing | | | | T. 619.274.5029 | | F. 619.274.5656 | | e-mail: marty@artwerks.com | |____________________________________| Marty Schmid

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:

PIXO support (1997) Problems getting parameters passed into email. (1997) Summing fields (1997) SiteGaurd file Cache vs webcatalog cache (1997) user submitted data REPOST (2000) Counting LineItems (2000) Are you an WC expert? (1997) [movefile] (1999) NT License trade for Mac (2000) Questions To Answer (1997) WebCat2: Formulas.db question (1997) [WebDNA] Emailer & SMTP (2009) WebCatalog2 Feature Feedback (1996) [WebDNA] Major grep/convertchars linux issues when writing to db (2010) international time (1997) Banners (1997) Is there a way to just get to the last record in the database? (1997) Authenticate (1997) PCS Emailer's role ? (1997) [Announce]: Web server security and password protection (1997)