Re: Simple Database close connection
This WebDNA talk-list message is from 2001
It keeps the original formatting.
numero = 39267
interpreted = N
texte = >Samuel Renkert wrote: > > > > shutdown webcat and webserver > > swap databases > > startup webcat and webserver > > > > Anyone trying to get to a page will just have to wait until your > > webserver is back up, shouldn't be long, seconds, maybe. I don't see > > how else you can keep people from opening your db's between steps 2 > > and 3. > > > >Bad for us; all of our sites run 100% through WebCat so no pages at all >get served while it is down. And in one case, the file is being FTP'd >over a relatively slow WAN link, so we are talking minutes not seconds.I think if you are uploading to an active db you have trouble brewing. Webcat can close a db whenever it feels it needs more ram ([closedatabase] docs). So you run into a spot where webcat may have closed your db, and you've began uploading, now a user forces the db open. Webcat opens the db with half the data.It might be working ok for now, but it's by chance, not design.A safer alternative is to upload the file to a different location, then swap it in, thus you avoid opening an incomplete db AND you don't have to rely on a speedy upload time.A variation on what I said before, with more context... Assuming your directory structure looks like this... .../activedbs/ first.db second.db0. create a new directory .../newdbs1. upload the new DBs into newdbs. (1 hour, but who cares!) 2. kill webcat / webserver. 3. move files from newdbs into activedbs. 4. start webcat / webserver.HTHs -Sam------------------------------------------------------------- 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://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
>Samuel Renkert wrote: > > > > shutdown webcat and webserver > > swap databases > > startup webcat and webserver > > > > Anyone trying to get to a page will just have to wait until your > > webserver is back up, shouldn't be long, seconds, maybe. I don't see > > how else you can keep people from opening your db's between steps 2 > > and 3. > > > >Bad for us; all of our sites run 100% through WebCat so no pages at all >get served while it is down. And in one case, the file is being FTP'd >over a relatively slow WAN link, so we are talking minutes not seconds.I think if you are uploading to an active db you have trouble brewing. Webcat can close a db whenever it feels it needs more ram ([closedatabase] docs). So you run into a spot where webcat may have closed your db, and you've began uploading, now a user forces the db open. Webcat opens the db with half the data.It might be working ok for now, but it's by chance, not design.A safer alternative is to upload the file to a different location, then swap it in, thus you avoid opening an incomplete db AND you don't have to rely on a speedy upload time.A variation on what I said before, with more context... Assuming your directory structure looks like this... .../activedbs/ first.db second.db0. create a new directory .../newdbs1. upload the new DBs into newdbs. (1 hour, but who cares!) 2. kill webcat / webserver. 3. move files from newdbs into activedbs. 4. start webcat / webserver.HTHs -Sam------------------------------------------------------------- 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://search.smithmicro.com/
Samuel Renkert
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:
5.0 Pricing (2003)
Database Options (1997)
Replacing a Word (1999)
Searchable Archives? (2000)
[OT] Snow Ctd. :) (2004)
Getting total number of items ordered (1997)
ThreadMem ignored? (1998)
WC2.0 Memory Requirements (1997)
Security for malls with different webmasters (1998)
sku, title, price not showing up (1998)
WebCat2 - Getting to the browser's username/password data (1997)
Another bug to squash (WebCat2b13 Mac .acgi) (1997)
Summing a field full of numbers ... (1997)
Duplicates (1998)
Single Link browsing (1997)
Using Cookie for client specific info? (1997)
Duplicate Cart #'s (1998)
Now you see it now you donīt (1997)
remotely add + sign (1997)
TCPSend/Replace DB Records (2002)