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 usersto use the back button to return to an add_record.tmpl to add morerecords since for my application most of the information in the previousrecord will be needed in the next added record as well and they can justreturn to the previous page with that redundent info already filled andonly 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 exactsame second, and if the servers clock is reset to an earlier time AND auser enters a record at a time which synchronizes it to the second with apreviously entered record.But I've found it useful to use the Date=SKU scheme from a databasemanagement standpoint because I can use one field for both SKU and date ofrecord 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 whichwould ask them to re-submit their record (and thus generating anewer/different Date value).I think the chances (at least in my application) of users entering recordsat the exact same second are extremely remote to begin with, and if Icouple that with a unique SKU number lookup - I think I'd feel prettycomforatble 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:
Just to add more complexity to this issue, I probably will encourage usersto use the back button to return to an add_record.tmpl to add morerecords since for my application most of the information in the previousrecord will be needed in the next added record as well and they can justreturn to the previous page with that redundent info already filled andonly 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 exactsame second, and if the servers clock is reset to an earlier time AND auser enters a record at a time which synchronizes it to the second with apreviously entered record.But I've found it useful to use the Date=SKU scheme from a databasemanagement standpoint because I can use one field for both SKU and date ofrecord 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 whichwould ask them to re-submit their record (and thus generating anewer/different Date value).I think the chances (at least in my application) of users entering recordsat the exact same second are extremely remote to begin with, and if Icouple that with a unique SKU number lookup - I think I'd feel prettycomforatble 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:
Add to Cart & List of Products (1997)
Shipping charges depending on tax rate? (1997)
Adding Shipping Costs based on percent of subtotal (1997)
Writing to triggers.db (2005)
How to find 100 most recent additions. (1997)
RequiredFields template (1997)
Pirated WebCat? My 2 cents worth.. (2003)
Price recalc based on quantity (1997)
Appending current [date] to a database (1997)
ADD a product without Database (1998)
system crashes, event log (1997)
RE: WebCat name recognition (was MacFinder -- a new WebDNAweb site) (1998)
Major Security Hole (1998)
A few questions. . . (1997)
Bug? (1997)
Variable prices and Formulas.db (1997)
expired beta (1997)
Getting the domain of every request ... (2003)
File Upload (1997)
Extended [ConvertChars] (1997)