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:
>>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:
Searchable archives gone again??? (2000)
New public beta available (1997)
[WebDNA] SOS request (2019)
Can WebCatalog.debug solve my problem? (2000)
FORMS: Returning a specific page (1997)
SV: Mass Mail (2000)
[OT] Bookmarking code (2003)
Setting up WebCatalog with Retail Pro data (1996)
How fast is your server? (2002)
emailer w/F2 (1997)
PayFlow Pro (2003)
Date search - yes or no (1997)
[LOOKUP] (1997)
Physical Security for WebCatalog Directories (1997)
Configuring E-mail (1997)
Improved ISAPI extension (2004)
ODBC Performance? (2001)
Was 5.0 Pricing, now Sandbox versus Website and ruminating (2003)
Hiding a subsection of text (2002)
[WebDNA] Domain upgrade questions (2009)