Re: [WebDNA] To Commitdatabase or Not to Commitdatabase
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 108408
interpreted = N
texte = > So would a FlushDatabases, which I understand is All DB Written to = Disk be a "slower" task compared to a [commitdatabas....] after every = [replace/append] ? I would assume that flushing all databases to disk would be slower. = About [FLUSHDATABASES] the manual says it, "causes all databases to be = written and closed". Why would you want to *close* the database just = to make sure the data is on disk? Then upon the very next operation = that involves that database, you have to load it all back into RAM = again. I would not close the database (remove it from RAM) unless = there was a reason to do so. I would also not commit to disk, nor = remove from RAM, ALL databases at once, unless there was a reason to do = so. =20 [COMMITDATABASE..] lets you precisely write to disk (but not flush from = RAM) *just the database you specify*. >=20 > And how do you normally avoid data loss? Are you using the = [commitdatabase...] ?? Well my clients are all over the map.. on different hosts, etc. Some = have auto-commit turned on via the admin interface.. Other = times/places I do use [commitdatabase...], specifically, when/where = needed. -G=
Associated Messages, from the most recent to the oldest:
> So would a FlushDatabases, which I understand is All DB Written to = Disk be a "slower" task compared to a [commitdatabas....] after every = [replace/append] ? I would assume that flushing all databases to disk would be slower. = About
[flushdatabases] the manual says it, "causes all databases to be = written and closed". Why would you want to *close* the database just = to make sure the data is on disk? Then upon the very next operation = that involves that database, you have to load it all back into RAM = again. I would not close the database (remove it from RAM) unless = there was a reason to do so. I would also not commit to disk, nor = remove from RAM, ALL databases at once, unless there was a reason to do = so. =20 [COMMITDATABASE..] lets you precisely write to disk (but not flush from = RAM) *just the database you specify*. >=20 > And how do you normally avoid data loss? Are you using the = [commitdatabase...] ?? Well my clients are all over the map.. on different hosts, etc. Some = have auto-commit turned on via the admin interface.. Other = times/places I do use [commitdatabase...], specifically, when/where = needed. -G=
Govinda
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:
WebCatalog for guestbook ? (1997)
WC TableGrinder (1997)
Displaying photo attached to first record (1997)
Single Link browsing (1997)
WebCat2 several catalogs? (1997)
06/06/2000 bug warning ... (2000)
URL encoding -- still a problem (1998)
Summing fields (1997)
WebCat2 - many [carts] on one template page? (1997)
WebCatalog can't find database (1997)
WebCat Code and WebStar Search? (2000)
date (2002)
Quick Question (1997)
Can I do these? (1997)
spreadsheet interface (1998)
Thanks Grant (1997)
Mac app. that converts e-mails (2000)
Plugin causes type 2 error on WebStar startup (2000)
A workaround for handling date range search in yyyy/mm/dd form (1997)
ReturnRaw and redirect one last question (1997)