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 = 105620
interpreted = N
texte = BTW, we fixed the small bug when the [math] variable name includes a = number ([math]thetest3=3D43[/math]) and we added the new requested tag = [thirurlplusget] so the [thisurl] tag will produce this: /x/y/z/index.dna and the [thirurlplusget] tag will produce this: /x/y/z/index.dna?a=3Db&c=3Dd We are working on the [append] tag that writes to disk and should not. = This behaviour has obviously been previously added to prevent database = loss of data in case of crash, but we think the Administration = configuration that says "Automatically commit databases to disk after = modification", the [closedatabase] tag and the [commitdatabase] provide = security enough. - chris On Jul 19, 2010, at 8:23, Kenneth Grome wrote: >> Ken, i am not sure if you are using [replace] or=20 >> [replacefounditems]. Do not forget [replacefounditems]=20 >> is much faster than the old technique of nesting a [replace]=20 >> context inside a [founditems] context. >=20 > 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.=20 >=20 > 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. >=20 > 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. >=20 > 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. >=20 > Sincerely, > Kenneth Grome >=20 >=20 >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list
. > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
BTW, we fixed the small bug when the [math] variable name includes a = number ([math]thetest3=3D43[/math]) and we added the new requested tag = [thirurlplusget] so the [thisurl] tag will produce this: /x/y/z/index.dna and the [thirurlplusget] tag will produce this: /x/y/z/index.dna?a=3Db&c=3Dd We are working on the [append] tag that writes to disk and should not. = This behaviour has obviously been previously added to prevent database = loss of data in case of crash, but we think the Administration = configuration that says "Automatically commit databases to disk after = modification", the [closedatabase] tag and the [commitdatabase] provide = security enough. - chris On Jul 19, 2010, at 8:23, Kenneth Grome wrote: >> Ken, i am not sure if you are using [replace] or=20 >> [replacefounditems]. Do not forget [replacefounditems]=20 >> is much faster than the old technique of nesting a [replace]=20 >> context inside a [founditems] context. >=20 > 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.=20 >=20 > 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. >=20 > 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. >=20 > 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. >=20 > Sincerely, > Kenneth Grome >=20 >=20 >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
christophe.billiottet@webdna.us
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:
New Web Site Developers Database (1996)
Multi-Row Tables from a search. (1997)
Hello??? (1997)
Webstar 1.3.1 PPC (1997)
Appending Record Prob (2001)
sort links (2002)
[search] in formulas.db (1997)
WebDNA install on Tiger doesn't work ... (2005)
Duplicate Carts (2006)
More on the email templates (I like it) (1997)
SiteEdit Pro Update Announcement (1997)
instant cookies? (1999)
tracking no. of downloads (2006)
Fw: Linux w/ apache (2000)
Orderfile Question (2003)
date stamp (2003)
database visibility (2000)
WebCatalog2 Feature Feedback (1996)
EmailFolder Correct Permissions ? (2003)
Random Sort Problem (2003)