Re: Multithreading of [replace]

This WebDNA talk-list message is from

1999


It keeps the original formatting.
numero = 23112
interpreted = N
texte = >>Now that I've made all these comments, I have an even faster solution. The >>fact of the matter is that you don't need the search context at all. >>Therefore I would get rid of it completely. You can perform the same tasks >>shown above with a single replace and a single lookup, like this: >> >>[replace >>append=t&db=carts.db&eqCARTdata=[cart]&allcase=t]cart=[cart]&date=[date >>%Y/%m/%d]&firstpage=[lookup >>db=carts.db&value=[cart]&lookinfield=cart&returnfield=firstpage¬found=[thisu >>r >>l]] ]&lastpage=[thisurl][/replace] > >If I really, really had to stick with the original db solution I would >split that db into 10 different ones and store visitor 1 in db 1, visitor 2 >in db 2 and so on. The info of which db a visitor belongs to I would pass >in the URI.Good idea! An easy way to select which cart.db to use (cart0.db, cart1.db, cart2.db ... cart9.db) would be to grab the last digit of the cart value and use the db with that digit in its name, like this:[replace db=cart[getchars start=1&end=1&from=end][cart][/getchars].db& ...Of course, this assumes the visitor carries the cart value throughout his entire visit ... :)Sincerely, Ken Grome Associated Messages, from the most recent to the oldest:

    
  1. Re: Multithreading of [replace] (Kenneth Grome 1999)
  2. Re: Multithreading of [replace] (Christer Olsson 1999)
  3. Re: Multithreading of [replace] (Kenneth Grome 1999)
  4. Re: Multithreading of [replace] (Brian B. Burton 1999)
  5. Re: Multithreading of [replace] (Grant Hulbert 1999)
  6. RE: Multithreading of [replace] (Olin Lagon 1999)
  7. Re: Multithreading of [replace] (Brian B. Burton 1999)
  8. RE: Multithreading of [replace] (Olin Lagon 1999)
  9. Multithreading of [replace] (Brian B. Burton 1999)
>>Now that I've made all these comments, I have an even faster solution. The >>fact of the matter is that you don't need the search context at all. >>Therefore I would get rid of it completely. You can perform the same tasks >>shown above with a single replace and a single lookup, like this: >> >>[replace >>append=t&db=carts.db&eqCARTdata=[cart]&allcase=t]cart=[cart]&date=[date >>%Y/%m/%d]&firstpage=[lookup >>db=carts.db&value=[cart]&lookinfield=cart&returnfield=firstpage¬found=[thisu >>r >>l]] ]&lastpage=[thisurl][/replace] > >If I really, really had to stick with the original db solution I would >split that db into 10 different ones and store visitor 1 in db 1, visitor 2 >in db 2 and so on. The info of which db a visitor belongs to I would pass >in the URI.Good idea! An easy way to select which cart.db to use (cart0.db, cart1.db, cart2.db ... cart9.db) would be to grab the last digit of the cart value and use the db with that digit in its name, like this:[replace db=cart[getchars start=1&end=1&from=end][cart][/getchars].db& ...Of course, this assumes the visitor carries the cart value throughout his entire visit ... :)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:

Setting up shop (1997) Extended [ConvertChars] (1997) Summing fields (1997) Ticket Ordering Question (2003) To Err or Not Custom Error (1999) WebCat hosting providers? (1997) New servers and new inline cache (1997) WC1.6 to WC2 date formatting (1997) Help! WebCat2 bug (1997) New Mac Emailer... (1997) Searching multiple fields from one form field (1997) WC Database Format (1997) [OT] Friday Time Waster (2003) WebCat2 - [format thousands] (1997) user selectable sort order (2000) [date format] w/in sendmail (1997) authenticating a second user (1997) Email notification to one of multiple vendors ? (1997) Cart Number sequence (1997) Choices (2000)