Re: forming a SKU
This WebDNA talk-list message is from 1999
It keeps the original formatting.
numero = 23531
interpreted = N
texte = >I believe you are right! > >Then a curiousity question... > >Is there any documentation on when WebCat is Switching Thread, or can you >force webcat to use 1 thread per page?Each page uses a single thread, the only time webcat will open a new thread is when you tell it to -- by using the [spawn] context.Therefore, the potential problem of duplicate SKU's comes in *only* when two or more people are using webcat at the same time to create new records. The probability of two simultaneous administrators appending new records to the same db at the exact same time is pretty slim, especially when most admin tasks are done by a single admin person.Still, using the [cart] value as part of every new SKU eliminates even the remotest possibility that two SKU's might have the same values -- except in two situations I can think of:1- Passing a [cart] value from another page to the page doing the [append] instead of making webcat create a new [cart] value on that page, and ...2- Turning the computer's clock BACK, which would allow webcat to generate a previously-created [cart] value since the date and time of the append might be 'revisited' in this scenario.Of course, you can always check the db for the existence of the new value, and if it's already there, try again until you get an unused value. That would eliminate both of these issues as potential problems ... :)Sincerely, Ken Grome
Associated Messages, from the most recent to the oldest:
>I believe you are right! > >Then a curiousity question... > >Is there any documentation on when WebCat is Switching Thread, or can you >force webcat to use 1 thread per page?Each page uses a single thread, the only time webcat will open a new thread is when you tell it to -- by using the
[spawn] context.Therefore, the potential problem of duplicate SKU's comes in *only* when two or more people are using webcat at the same time to create new records. The probability of two simultaneous administrators appending new records to the same db at the exact same time is pretty slim, especially when most admin tasks are done by a single admin person.Still, using the
[cart] value as part of every new SKU eliminates even the remotest possibility that two SKU's might have the same values -- except in two situations I can think of:1- Passing a
[cart] value from another page to the page doing the
[append] instead of making webcat create a new
[cart] value on that page, and ...2- Turning the computer's clock BACK, which would allow webcat to generate a previously-created
[cart] value since the date and time of the append might be 'revisited' in this scenario.Of course, you can always check the db for the existence of the new value, and if it's already there, try again until you get an unused value. That would eliminate both of these issues as potential problems ... :)Sincerely, Ken Grome
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:
Sort & Shownext (1999)
More on the email templates (1997)
Logical and or in [hideif] (1997)
Re:Change WebDNA-Talk Mail due to no digest for 1wk (1997)
Pass a form (2003)
WebCatalog2 Feature Feedback (1996)
tcpSend variables not seen (2006)
Re:2nd WebCatalog2 Feature Request (1996)
WebCat2 beta 11 - new prefs ... (1997)
Thankyou Ronny (2003)
webcat- multiple selection in input field (1997)
combine search (1998)
Help :( (2001)
writefile to create static pages (2003)
I'm new be kind (1997)
ANother SHOWIF problem (1997)
Format of Required fields error message (1997)
Shopping Cart Limits? (1998)
WebCatalog Upgrade Pricing? (1997)
docs for WebCatalog2 (1997)