Re: Database changes
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 16175
interpreted = N
texte = >It will always overwrite a file that has been modified, though, and 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?Well, for one thing, a WebCat developer usually creates test db's and replaces them with new test db's as each site is created. For those of us in this situation, the changes we make really are unimportant because we are only making those changes in order to prove to ourselves that WebCat is actually changing the data the way we expect it to.But on a live server, there may still be reasons why we would not want RAM-cached data overwriting our new data, whether or not it has been changed.For example, sometimes I take my db and load it into Panorama so I can make some global changes to a whole lot of records. I use Panorama because it's got a desktop interface and the tools I need to do things WebCat cannot -- and it's fast.Now, I want to upload my newly-changed and exported db to the server so WebCat can use it. But I don't want WebCat overwriting my new db with the old one when I replace it manually.However, WebCat *will* overwrite my new db as soon as my next web site visitor makes a change to this database thru one of WebCat's templates, because my new db will have a different mod date than the file it's replacing. :So I need to take special precautions to keep that from happening:1- Quit WebCat to prevent it from overwriting our new db files, or ... 2- Use one of Christer's suggestions, either of which work very well.I've used both of Christer's suggestions, but not in development except to test them. In development it's easier for me to quit WebCat, then replace the files manually, then restart WebCat.But on a live server his #2 suggestion is the one I've used the most, probably because it lets me change my db format (I can add new fields, change field names, etc.) ... :)Sincerely, Ken Grome ken@iav.com 808-737-6499 WebDNA Solutions http://webdna.net/
Associated Messages, from the most recent to the oldest:
>It will always overwrite a file that has been modified, though, and 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?Well, for one thing, a WebCat developer usually creates test db's and replaces them with new test db's as each site is created. For those of us in this situation, the changes we make really are unimportant because we are only making those changes in order to prove to ourselves that WebCat is actually changing the data the way we expect it to.But on a live server, there may still be reasons why we would not want RAM-cached data overwriting our new data, whether or not it has been changed.For example, sometimes I take my db and load it into Panorama so I can make some global changes to a whole lot of records. I use Panorama because it's got a desktop interface and the tools I need to do things WebCat cannot -- and it's fast.Now, I want to upload my newly-changed and exported db to the server so WebCat can use it. But I don't want WebCat overwriting my new db with the old one when I replace it manually.However, WebCat *will* overwrite my new db as soon as my next web site visitor makes a change to this database thru one of WebCat's templates, because my new db will have a different mod date than the file it's replacing. :So I need to take special precautions to keep that from happening:1- Quit WebCat to prevent it from overwriting our new db files, or ... 2- Use one of Christer's suggestions, either of which work very well.I've used both of Christer's suggestions, but not in development except to test them. In development it's easier for me to quit WebCat, then replace the files manually, then restart WebCat.But on a live server his #2 suggestion is the one I've used the most, probably because it lets me change my db format (I can add new fields, change field names, etc.) ... :)Sincerely, Ken Grome ken@iav.com 808-737-6499 WebDNA Solutions http://webdna.net/
Kenneth Grome
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:
Re:Emailer and encryption (1997)
WebCat hosting providers? (1997)
Ampersand Character (&) (1997)
[ShowNext] feature in 2.0 (1997)
Error Lob.db records error message not name (1997)
5.0 feature request: Sort for ListWords (2001)
Help name our technology! I found it (1997)
lineitem variables (1999)
shipcost (1997)
Time Tracking (2003)
WebCat B13 Mac CGI -- Frames question (1997)
WebCat/CyberStudio Compatibility (1998)
SSL, WebSTAR, WebCatalog (1998)
$Append for Users outside the ADMIN group (1997)
about this server and links to who (1997)
Associative lookup style? (1997)
[WebDNA] [OT] Updated (unofficial) WPT 2.0 (2014)
Hiding URL ? (1998)
[delete] problem (1997)
WebSTAR 2.1 freezes my Mac (1997)