Re: [cart]'s ever get recycled?
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 31741
interpreted = N
texte = On 5/10/00 3:21 PM, Somebody asked:S >> SM (or anyone) can you *guarantee* that if I use cart numbers for a >> few hundred >> thousand recordIDs that in 10 years+ there will be no chance that >> when an admin creates >> a new record and goes to assign its ID that the [cart] will not load >> a duplicate that >> was used before?And Kenneth Grome at ken@simplewebstores.com suggested: > If you're that concerned about getting an absolutely unique value > every time, why don't you use a database to store the last number > used as a unique value, and increment it by one each time someone new > visits the site? You won't be able to use the [cart] tag if you do > this, so you won't have to be concerned about whether or not the > [cart] tag is going to give you what you want, because you'll be > dealing with that yourself ... :)My technique of choice is to create a record ID by slapping [cart] and [date %Y%m%d%H%M%S] together. Yes, this results in a number that looks like the National Debt, but it exponentially increases the number of possible unique numbers. You'd be hard-pressed to generate a duplicate value this way. Also, since WebCat treats everything as text anyway, you could even use the encrypt context to hash the [cart] value. As long as you provide a seed, the hash encrypt generates will be unique even if you crypt the same string multiple times. Providing a seed is key for this to work-- If you don't use one, the hash will be the same every time you crypt the same text, as if it were a password in your users.db.-- Andrew Vernon avernon@dramatols.net------------------------------------------------------------- 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://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
On 5/10/00 3:21 PM, Somebody asked:S >> SM (or anyone) can you *guarantee* that if I use cart numbers for a >> few hundred >> thousand recordIDs that in 10 years+ there will be no chance that >> when an admin creates >> a new record and goes to assign its ID that the [cart] will not load >> a duplicate that >> was used before?And Kenneth Grome at ken@simplewebstores.com suggested: > If you're that concerned about getting an absolutely unique value > every time, why don't you use a database to store the last number > used as a unique value, and increment it by one each time someone new > visits the site? You won't be able to use the [cart] tag if you do > this, so you won't have to be concerned about whether or not the > [cart] tag is going to give you what you want, because you'll be > dealing with that yourself ... :)My technique of choice is to create a record ID by slapping [cart] and [date %Y%m%d%H%M%S] together. Yes, this results in a number that looks like the National Debt, but it exponentially increases the number of possible unique numbers. You'd be hard-pressed to generate a duplicate value this way. Also, since WebCat treats everything as text anyway, you could even use the encrypt context to hash the [cart] value. As long as you provide a seed, the hash encrypt generates will be unique even if you crypt the same string multiple times. Providing a seed is key for this to work-- If you don't use one, the hash will be the same every time you crypt the same text, as if it were a password in your users.db.-- Andrew Vernon avernon@dramatols.net------------------------------------------------------------- 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://search.smithmicro.com/
Andrew Vernon
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:
Re[2]: Support suggestions - Response (2000)
Ampersand (1997)
How do I write this search? (2006)
Secure server question (1997)
Colocator Upgrading OS (2004)
hidden databases (2000)
Requiring that certain fields be completed (1997)
Check boxes (1997)
Core Database integration (2001)
searching problem (1998)
RAM variables (1997)
Saving Text Areas with Orders (1997)
RE: [WebDNA] WebDNA Crashing or Not **YES** (2008)
Public Beta for WebCatalog 4.0 is Available (2000)
Server IP address? (1998)
Bug or syntax error on my part? (1997)
Fun with Dates - revisited (1997)
[WebDNA] feature suggestion (2011)
HELP WITH DATES (1997)
[defined]ish (1997)