Re: Sku numbers
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 11629
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?I think you have an excellent handle on this. I don't think it's very likely that users will create new records on any site at the very same second - and if they did, it would only create a problem for a very few cases. You'd have to have an awfully busy web site in order for this to become a major problem ... or else maybe a lot of bad luck! :)Recommending use of the Back button is a good technique when most of the same data has to be entered again, especially when you're using a date/time sku instead of a [cart] value.Sincerely, Ken Grome ..... ken@iav.com http://usarea.net/home.html
Associated Messages, from the most recent to the oldest:
>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?I think you have an excellent handle on this. I don't think it's very likely that users will create new records on any site at the very same second - and if they did, it would only create a problem for a very few cases. You'd have to have an awfully busy web site in order for this to become a major problem ... or else maybe a lot of bad luck! :)Recommending use of the Back button is a good technique when most of the same data has to be entered again, especially when you're using a date/time sku instead of a
[cart] value.Sincerely, Ken Grome ..... ken@iav.com http://usarea.net/home.html
Kenneth Grome
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:
Tenon and PCS Partner (1998)
Cart questions (1997)
Problems reading files created by WC (1997)
2.0Beta Command Ref (can't find this instruction) (1997)
Searching multiple fields from one form field (1997)
HEADER AND FOOTER (1997)
webCat craps httpd (2005)
301 redirect (2008)
WebCatalog Technical Reference (1997)
update on wn searching (1997)
Authenticate (1997)
WebCat editing, SiteGuard WAS:SiteAssociative lookup style? (1997)
remove.htm from result (2005)
Suggestion: appendfounditems (2002)
Uh...can someone help me out with the b10? (1997)
Re:Copyright ? (1997)
NT [delete] - duh nevermind. (1998)
WebCat2_Mac RETURNs in .db (1997)
Referrer from multiple entry points (1998)
all records returned. (1997)