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:

    
  1. Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (christophe.billiottet@webdna.us 2010)
  2. Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (Kenneth Grome 2010)
  3. Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (Kenneth Grome 2010)
  4. Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (christophe.billiottet@webdna.us 2010)
  5. Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (Kenneth Grome 2010)
  6. Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (Kenneth Grome 2010)
  7. Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (christophe.billiottet@webdna.us 2010)
  8. Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (Kenneth Grome 2010)
  9. Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (christophe.billiottet@webdna.us 2010)
  10. Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (Kenneth Grome 2010)
  11. Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (christophe.billiottet@webdna.us 2010)
  12. Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (Kenneth Grome 2010)
  13. Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (christophe.billiottet@webdna.us 2010)
  14. [WebDNA] CORRECTION: 60% failure rate using replace in a loop (Kenneth Grome 2010)
> 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:

https bs (2004) RE: groups and [ShowNext] (1997) Directory Overload (1998) RE: (OFF TOPIC) System 8.5.1 FINDER ERROR (1999) authorize.net hex coded variables (2002) Intranet Edition (2004) Formating found categories (1997) Setting up WebCatalog with Retail Pro data (1996) Multiple catalog databases and showcart (1997) Crashes with recursion (2000) PCS Frames (1997) Preventing Merchant Settling ? (1997) Hello??? (1997) Revisit: speed test (2002) SV: [sendmail] (2000) Thanks ! (1997) remotely add + sign (1997) [BULK] [WebDNA] set HTTP-Status Code from webdna (2016) Associative lookup style? (1997) MASTER_STORE revision (2002)