Re: Database changes
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 16154
interpreted = N
texte = >The correct procedure when uploading a new replacement db file to the >server is to perform the $flushdatabases command first, THEN upload the >file. > >But this only works when no one happens to request a page that calls that >database in the meantime, because if that happens, WebCat will reload the >old db back into RAM before you're finished replacing the old db with the >new one... and then, once that old db is in RAM again, there's no way to >purge that RAM data without rewriting it to disk. > >So on a busy server, this generally means having to suspend new >connections or quitting the server in order to make absolutely sure that >your newly-uploaded db does not get overwritten by WebCat.We use two different techniques for updating .dbs, depending on the size of the db.1. Upload a new copy of the .db with a different name, like new.db. Search the old.db for all records and delete them. Then search the new.db for all records and append them to the old.db. Close the new.db. Replace new.db with a new new.db next time you have to update.2. Upload a new copy of the .db called something different. Close the old.db and delete it (either by [APPLESCRIPT] or with WebCat 2.1's [DeleteFile] tag. Rename the new.db to old.db with [APPLESCRIPT] or [CopyFile] new.db to old.db with WebCat 2.1 and [DeleteFile] new.db.On a really busy server or with really big db.s you might to embed an [APPLESCRIPT] in the beginning of the template that tells Web* to refuse connections and one [APPLESCRIPT] in the end telling Web* to accept connections again. ************************************************************* Christer Olsson Stora Nygatan 21 Phone +46 40 791 50 Art director S-211 37 Malmoe Fax +46 40 97 99 77 Ljusa Ideer AB Sweden http://www.ljusaideer.se
Associated Messages, from the most recent to the oldest:
>The correct procedure when uploading a new replacement db file to the >server is to perform the $flushdatabases command first, THEN upload the >file. > >But this only works when no one happens to request a page that calls that >database in the meantime, because if that happens, WebCat will reload the >old db back into RAM before you're finished replacing the old db with the >new one... and then, once that old db is in RAM again, there's no way to >purge that RAM data without rewriting it to disk. > >So on a busy server, this generally means having to suspend new >connections or quitting the server in order to make absolutely sure that >your newly-uploaded db does not get overwritten by WebCat.We use two different techniques for updating .dbs, depending on the size of the db.1. Upload a new copy of the .db with a different name, like new.db. Search the old.db for all records and delete them. Then search the new.db for all records and append them to the old.db. Close the new.db. Replace new.db with a new new.db next time you have to update.2. Upload a new copy of the .db called something different. Close the old.db and delete it (either by [APPLESCRIPT] or with WebCat 2.1's
[deletefile] tag. Rename the new.db to old.db with [APPLESCRIPT] or
[copyfile] new.db to old.db with WebCat 2.1 and
[deletefile] new.db.On a really busy server or with really big db.s you might to embed an [APPLESCRIPT] in the beginning of the template that tells Web* to refuse connections and one [APPLESCRIPT] in the end telling Web* to accept connections again. ************************************************************* Christer Olsson Stora Nygatan 21 Phone +46 40 791 50 Art director S-211 37 Malmoe Fax +46 40 97 99 77 Ljusa Ideer AB Sweden http://www.ljusaideer.se
Christer Olsson
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:
A question about security (1998)
Input appreciated (2000)
What folder??? (1999)
Upgrade on MacOSX 3.05 to 3.08 (2000)
taxrate - off by 1 cent (1997)
PCS Frames (1997)
Check boxes (1997)
Beta 18 (1997)
OK, here goes... (1997)
WebCat2 - storing unformatted date data? (1997)
A question on sub-categories (1997)
[WebDNA] Upgrade 4.5.1 to 6.0a (2009)
Interfacing WebMerchant to www.fedex.com (1997)
Narrowing NT Crashing error (2000)
Lookup question (2001)
WebCatalog can't find database (1997)
emailer don't work (1998)
More on the email templates (1997)
Custom Shipping Charges (1997)
WebCat2b13MacPlugIn - More limits on [include] (1997)