Re: Database Not Found Problem
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 55844
interpreted = N
texte = Wow. That worked too! Thanks. I definitely learned a lot today. Thanks =to everyone who chimed in on this.Justin CarrollOn Tuesday, March 23, 1943, John Peacock
wrote:>Justin Carroll wrote:>>> My hypothesis is that accessing too many db's cached in RAM sent back =this>> error every so often and that you shouldn't nest past two searches if>> possible. Technically the problem still exists because if you nest a>> [replace] inside too many searches, eventually this will>happen.>>Check out the [replacefounditems] context, which is intended to be used =inside a=20>[search] context. A normal [replace] performs all of the searching, as =well as=20>the updating, so it is massively slower to do a [replace]>inside a [search].>>John>>--=20>John Peacock>Director of Information Research and Technology>Rowman & Littlefield Publishing Group>4501 Forbes Boulevard>Suite H>Lanham, MD 20706>301-459-3366 x.5010>fax 301-429-5748>>>------------------------------------------------------------->This message is sent to you because you are subscribed to> the mailing list .>To unsubscribe, E-mail to: >To switch to the DIGEST mode, E-mail to >Web Archive of this list is at: http://webdna.smithmicro.com/>-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Wow. That worked too! Thanks. I definitely learned a lot today. Thanks =to everyone who chimed in on this.Justin CarrollOn Tuesday, March 23, 1943, John Peacock wrote:>Justin Carroll wrote:>>> My hypothesis is that accessing too many db's cached in RAM sent back =this>> error every so often and that you shouldn't nest past two searches if>> possible. Technically the problem still exists because if you nest a>> [replace] inside too many searches, eventually this will>happen.>>Check out the [replacefounditems] context, which is intended to be used =inside a=20>[search] context. A normal [replace] performs all of the searching, as =well as=20>the updating, so it is massively slower to do a [replace]>inside a [search].>>John>>--=20>John Peacock>Director of Information Research and Technology>Rowman & Littlefield Publishing Group>4501 Forbes Boulevard>Suite H>Lanham, MD 20706>301-459-3366 x.5010>fax 301-429-5748>>>------------------------------------------------------------->This message is sent to you because you are subscribed to> the mailing list .>To unsubscribe, E-mail to: >To switch to the DIGEST mode, E-mail to >Web Archive of this list is at: http://webdna.smithmicro.com/>-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Justin Carroll
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:
Netscape v. IE (1997)
Help! Odd, irreproducible happenings. (1998)
For those of you not on the WebCatalog Beta... (1997)
WC2b15 File Corruption (1997)
[blank] (2005)
jpeg upload compression (2002)
webmerch and serials - almost there (1997)
Calculating Shipping (1997)
SiteGuard Admin Feature ? (1997)
WC2b15 File Corruption (1997)
Associative lookup style? + bit more (1997)
Beta5??? (2000)
WebCatalog f2 Installation (1997)
Under Score (1999)
WC3 and SSL on NT (1998)
server2003 isolation mode (2004)
Strange Search Results (2004)
WebCat editing, SiteGuard & SiteEdit (1997)
Sense/Disallow HTML tags during $Append (1997)
Hosting Service (1998)