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:

    
  1. Re: [cart]'s ever get recycled? (John Butler 2000)
  2. Re: [cart]'s ever get recycled? (Kenneth Grome 2000)
  3. Re: [cart]'s ever get recycled? (WebDNA Support 2000)
  4. Re: [cart]'s ever get recycled? (Andrew Vernon 2000)
  5. Re: [cart]'s ever get recycled? (Kenneth Grome 2000)
  6. Re: [cart]'s ever get recycled? (John Butler 2000)
  7. Re: [cart]'s ever get recycled? (Stuart Tremain 2000)
  8. Re: [cart]'s ever get recycled? (Kenneth Grome 2000)
  9. Re: [cart]'s ever get recycled? (Stuart Tremain 2000)
  10. Re: [cart]'s ever get recycled? (Kenneth Grome 2000)
  11. Re: [cart]'s ever get recycled? (Stuart Tremain 2000)
  12. Re: [cart]'s ever get recycled? (Kenneth Grome 2000)
  13. Re: [cart]'s ever get recycled? (Stuart Tremain 2000)
  14. [cart]'s ever get recycled? (John Butler 2000)
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:

WebCatalog for guestbook ? (1997) Country & Ship-to address & other fields ? (1997) [showif] or-ing (1999) [WebDNA] mac osx permissions problem (2010) WebCatalog 2.0 & WebDNA docs in HTML ... (1997) question: search return in order (1997) Emailer choke (1997) More on the email templates (1997) Fun with Dates - revisited (1997) Custom Tags or Modular Code (2001) weight based shipping cost questions (1997) I can help! (1996) 2cd pair of eyes (2003) suffix mapping, use of cache, etc. (1997) BUG: Switch inside ListFields context (2005) [OT] What System Software? (2003) COST? WebCatalog Training Class July 23-24 in San Diego (2001) problems with WebCat-Plugin (1997) WebTEN vs webSTAR (1998) 2.1b3 --> way slow (1997)