Re: Database changes
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 16173
interpreted = N
texte = >My alternative was to set up a Kenlike procedure done at an off time. >I would suspend connections, close the databases and FTP some new >database file over and then release the server. This shouldn't take long >, after which the connections can be started again. If there is another >way to deal with this I like to know what it is. The upcoming 2.1 release is smarter about Merge-format files -- it will not overwrite them unless they have truly been modified. So simply uploading the new one and calling [CloseDatabase] should be enough.It will always overwrite a file that has been modified, though, and it concerns me that some people want to upload new files even if the WebCatalog-cached ones have been modified in RAM. This represents a serious consistency problem in general (not matter what product you use) -- if the changes are so unimportant that it's OK to overwrite them, then why bother changing the database at all?Grant Hulbert, V.P. Engineering | ==== eCommerce for the Rest of Us ==== Pacific Coast Software | WebCatalog, WebMerchant, 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, San Diego, CA 92128 | Typhoon 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/
Associated Messages, from the most recent to the oldest:
>My alternative was to set up a Kenlike procedure done at an off time. >I would suspend connections, close the databases and FTP some new >database file over and then release the server. This shouldn't take long >, after which the connections can be started again. If there is another >way to deal with this I like to know what it is. The upcoming 2.1 release is smarter about Merge-format files -- it will not overwrite them unless they have truly been modified. So simply uploading the new one and calling
[closedatabase] should be enough.It will always overwrite a file that has been modified, though, and it concerns me that some people want to upload new files even if the WebCatalog-cached ones have been modified in RAM. This represents a serious consistency problem in general (not matter what product you use) -- if the changes are so unimportant that it's OK to overwrite them, then why bother changing the database at all?Grant Hulbert, V.P. Engineering | ==== eCommerce for the Rest of Us ==== Pacific Coast Software | WebCatalog, WebMerchant, 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, San Diego, CA 92128 | Typhoon 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/
Grant Hulbert
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:
Has anyone built this already? (2003)
Sorting by date (1997)
date sorting and 'template (1997)
Help name our technology! (1997)
Incompatibility with WebCat 3 templates ... (2000)
PCS Frames (1997)
WebCat2 Append problem (B14Macacgi) (1997)
Starting WebCat under linux (2000)
Using Currencies other than Dollars (1997)
Color options - modified (1999)
Price and Formula.db (2002)
Problem when Inputing text (1999)
pop up menu's (1998)
append duplication help (2000)
possible, WebCat2.0 and checkboxes-restated (1997)
Multi vendor shop (2000)
Multiple FlushDatabases (2000)
WC2.0 Memory Requirements (1997)
Not really WebCat (1997)
Database Structure? (1998)