Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 105619
interpreted = N
texte = > Ken, i am not sure if you are using [replace] or > [replacefounditems]. Do not forget [replacefounditems] > is much faster than the old technique of nesting a [replace] > context inside a [founditems] context.I tried using replacefounditems but that wasn't working in some (but not all) of my code, so I switched the broken sections to replace -- and the code that wasn't working before suddenly started working. This made me think that maybe there's a bug in replacefounditems. I was going to report it but when I changed my code from replacefounditems to replace I over-wrote the failing replacefounditems code and I didn't have the time to go back and re-write it in order to post to the list for a confirmation of the problem/bug.BTW, last night I streamlined the "replace in a loop" code that was taking 10-15 seconds to replace 45 db records. I ended up shaving 1-2 seconds off the elapsedtime. That's not nearly enough of an improvement for what I need to do -- the response time was still way too slow -- so I had to rewrite everything anyways, but at least I got it to run a little bit faster.If I can find the time to test replacefounditems again this week I will give it another try. If I have problems again maybe I will think far enough ahead to save the problematic code and post it to the list this time around.Sincerely,Kenneth Grome
Associated Messages, from the most recent to the oldest:
> Ken, i am not sure if you are using
[replace] or >
[replacefounditems]. Do not forget
[replacefounditems] > is much faster than the old technique of nesting a
[replace] > context inside a
[founditems] context.I tried using replacefounditems but that wasn't working in some (but not all) of my code, so I switched the broken sections to replace -- and the code that wasn't working before suddenly started working. This made me think that maybe there's a bug in replacefounditems. I was going to report it but when I changed my code from replacefounditems to replace I over-wrote the failing replacefounditems code and I didn't have the time to go back and re-write it in order to post to the list for a confirmation of the problem/bug.BTW, last night I streamlined the "replace in a loop" code that was taking 10-15 seconds to replace 45 db records. I ended up shaving 1-2 seconds off the elapsedtime. That's not nearly enough of an improvement for what I need to do -- the response time was still way too slow -- so I had to rewrite everything anyways, but at least I got it to run a little bit faster.If I can find the time to test replacefounditems again this week I will give it another try. If I have problems again maybe I will think far enough ahead to save the problematic code and post it to the list this time around.Sincerely,Kenneth 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:
[/application] error? (1997)
[SearchString] usage (1997)
NewCart+Search with one click ? (1997)
problems with 2 tags shakur (1997)
Photo Album (2000)
How do I get Google to crawl a WebCat site? (2003)
Cancel Subscription (1996)
required fields (1999)
Hierarchy of form/text/math variables (renamed thread) (2000)
Calculating multiple shipping... (1997)
WebCatalog + WebMerchant 2.1 for Windows released (1998)
Nesting searches. (1998)
Developer Edition (2003)
Re:Help name our technology! (1997)
Webstar 1.3.1 PPC (1997)
Force a search at the default.tmpl page? (1997)
WebCatalog Hosting (1996)
Stumpted Again (1997)
Upgrading old WebCat Database Files (1997)
Default contains WEBDNA (1998)