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:
Bug Report, maybe (1997)
Make sure I understand this??? (1997)
[shownext] and descending order (1997)
[WebDNA] [OT] Kickstarter feedback please? (2015)
WebCat2b13 Command Reference Doc error (1997)
Multiple Choices in One Entry - Clothing Sizes (2000)
WC2.0 Memory Requirements (1997)
Showif Context combined with Search (1997)
[SearchString] problem with [search] context (1997)
Looping control (1997)
show all problem (1997)
Multiple fields on 1 input (1997)
FTP via Shell Question (2005)
[WebDNA] WebDNA code displaying on page (2012)
Part Html part WebDNA (1997)
Duplicate Messages (1998)
billing system (2003)
New Mac Emailer... (1997)
WebCat2 Append problem (B14Macacgi) (1997)
Enhanced Master Counter? (1997)