Re: [WebDNA] Triggers.db wiped completely blank
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 107868
interpreted = N
texte = > > It just occurred to me that a remote backup script > > filled my storage allotment on this VPS recently. I > > deleted the backup files a couple hours later, but > > might the fact that the disk was full have caused this > > problem? > > perhaps in case the internal method is to write the new > copy *and then* erase the old copy... but somehow, in > the shuffle while lacking disk space, the former failed > but the latter still fired. > > (Or (more crazy) the method is: erase/rename the old > copy and then write the new copy?) > > We need a budget for a webdna developer so such a person > would actually dig in and find the real answer.. and > tweak if needed. I agree that it would be very useful to hire someone to dig into the internal code and find out how this actually works. Then fix it so that instead of wiping a perfectly good db clean when there is not enough disk space, it posts an error or send an email error to the admin -- and saves the original data without change. It would also be nice to see an explanation of how the internal code actually works in this situation. Then at the very least we can understand it ourselves, and possibly develop systems that prevent such data loss in the future. Sincerely, Kenneth Grome
Associated Messages, from the most recent to the oldest:
> > It just occurred to me that a remote backup script > > filled my storage allotment on this VPS recently. I > > deleted the backup files a couple hours later, but > > might the fact that the disk was full have caused this > > problem? > > perhaps in case the internal method is to write the new > copy *and then* erase the old copy... but somehow, in > the shuffle while lacking disk space, the former failed > but the latter still fired. > > (Or (more crazy) the method is: erase/rename the old > copy and then write the new copy?) > > We need a budget for a webdna developer so such a person > would actually dig in and find the real answer.. and > tweak if needed. I agree that it would be very useful to hire someone to dig into the internal code and find out how this actually works. Then fix it so that instead of wiping a perfectly good db clean when there is not enough disk space, it posts an error or send an email error to the admin -- and saves the original data without change. It would also be nice to see an explanation of how the internal code actually works in this situation. Then at the very least we can understand it ourselves, and possibly develop systems that prevent such data loss in the future. Sincerely, Kenneth Grome
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:
Creating main- and sub-category search (1997)
& problem (1999)
problems with 2 tags (1997)
Separate SSL Server (1997)
[WebDNA] El Capitan (2017)
Multiple security dbs (1997)
carriage returns in data (1997)
Emailer port change (1997)
[WebDNA] Successful, working WebDNA7/CentOS install? (2013)
Looking up two prices in Formulas.db (1997)
Editing two databases in one form using [replace]? (1998)
Searching,Brain Dead! (1999)
[WebDNA] Carriage Return/Line Feed Issue (2009)
Re:2nd WebCatalog2 Feature Request (1996)
Showif Error Generated... (2003)
Setting up shop (1997)
WebCat2b15MacPlugin - [protect] (1997)
wrong input values? (1997)
WC Database Format (1997)
Pay by Mail (CC, Check, Money Order) (2001)