Re: Closing Databases
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 16596
interpreted = N
texte = On 3/18/98 12:38 AM, Sjoerd Jan ter Welle wrote:>Sorry, I still do not understand why I would have to close of flush the >database afterwards. Closing/Flusing a database writes what's in memory >back to disk. If I first upload a new file and then close or flash the >database, to my understanding the file in memory is overwriting the new >file with old data?! What's wrong with my way of thinking.Your thinking that the database is written regardless of whether it has changed or not. If I understand the new feature correctly, only those databases that have changed in ram are written to the drive. Therefore when you choose to close the database and no changes have been made to that database, no database is written to the drive.When someone asks for that database, webcat then picks up the new one.TadaJust for the sake of superior engineering, I would like to see it write the changes to the drive without dropping the database from ram. Then use another command to write and drop those databases that have changed in order to pickup new ones. That would be Robert Minor__________________________________________________________CyberMill Website Designers & Publishers8616 Joseph AveSt. Louis, MO 63144voice 314-962-4024email: webmaster@cybermill.comhttp://www.cybermill.com/__________________________________________________________We are not responsible for any misspelling or misinformationplease check with your internet provider for defects.
Associated Messages, from the most recent to the oldest:
On 3/18/98 12:38 AM, Sjoerd Jan ter Welle wrote:>Sorry, I still do not understand why I would have to close of flush the >database afterwards. Closing/Flusing a database writes what's in memory >back to disk. If I first upload a new file and then close or flash the >database, to my understanding the file in memory is overwriting the new >file with old data?! What's wrong with my way of thinking.Your thinking that the database is written regardless of whether it has changed or not. If I understand the new feature correctly, only those databases that have changed in ram are written to the drive. Therefore when you choose to close the database and no changes have been made to that database, no database is written to the drive.When someone asks for that database, webcat then picks up the new one.TadaJust for the sake of superior engineering, I would like to see it write the changes to the drive without dropping the database from ram. Then use another command to write and drop those databases that have changed in order to pickup new ones. That would be Robert Minor__________________________________________________________CyberMill Website Designers & Publishers8616 Joseph AveSt. Louis, MO 63144voice 314-962-4024email: webmaster@cybermill.comhttp://www.cybermill.com/__________________________________________________________We are not responsible for any misspelling or misinformationplease check with your internet provider for defects.
Bob Minor
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:
Search Help Please (1998)
Mozilla/4. and Browser Info.txt (1997)
unsubscribe (2004)
[WebDNA] Single Sign On using SAML (2015)
GuestBook example (1997)
RandSeed (2003)
[ShowIf] and empty fields (1997)
Grep Help (2007)
Hyperboard/bulletin board available (1998)
Umm...about those log files? (Off Topic) (1997)
The beginning (1997)
Multiple prices (1997)
Public beta 2 for WebCatalog 4.0 is now available. (2000)
Document Contains No Data! (1997)
Banner Ad example (Typhoon) and WebCatalog (1997)
2nd WebCatalog2 Feature Request (1996)
show all problem (1997)
Re[2]: Field Problem (2000)
using showpage and showcart commands (1996)
Admin Edit prob. (1997)