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:
PDF Example (2003)
[OT] What System Software? (2003)
Formatting ModDate (2000)
Help with ShowNext (1998)
Another option (2005)
shownext problems (1998)
Multiple Merchant Accounts? (1997)
WebCatalog-NT?'s (1996)
[setcookie] & [redirect] (1998)
Date Sorting (1997)
IE 6 weirdness ??? (2002)
[TaxableTotal] - not working with AOL and IE (1997)
[protect admin] (1997)
input problem (1999)
Multi-processor Mac info ... (1997)
[addlineitems] display (1997)
[WebDNA] reverse rank=off (2008)
Banner Ads (2000)
Separate SSL Server (1997)
[OT] Creating HTML Emails (not using WebDNA) (2003)