Re: [WebDNA] "Safe Write for Database" setting....

This WebDNA talk-list message is from

2016


It keeps the original formatting.
numero = 112637
interpreted = N
texte = 220 Make sure your client doesn't have two people working on stuff at the=20 same time. That could lead to trouble if they're both updating the=20 same record. Terry W On Tue, 15 Mar 2016 22:09:31 -0500 Donovan Brooke wrote: If a reboot doesn=92t fix it, maybe write some troubleshooting code. =20 On the form, write to a debug file exactly what webdna is going to write to the database. Directly after, do a search on that database and write to the debug file the result of what happened after the database transaction. Surround the entire thing in [elapsedtime] and record that as well. =20 Sincerely, Donovan =20 =20 =20 =20 =20 On Mar 15, 2016, at 9:52 PM, Rich Kwas wrote: =20 > Like usual, it happened 2x on 2 different ad listings I'm being told,=20 >and been stable ever since. > That's what makes it so frustrating. Can't seem to pin down the why. >=20 > I'll keep my eye on those error logs.. >=20 >=20 >=20 >=20 > On Tuesday, March 15, 2016 7:45 PM, Donovan Brooke =20 >wrote: >=20 >=20 > This means that you haven't had any issues with your database. (No=20 >need to mess with safe write) =20 >=20 > Watch that your error logs don't get too big, now that you've turned=20 >them on.=20 >=20 > Lots of stuff can change on a server in 10 years ;-) (Even if you=20 >don't touch it) >=20 > I'd start with Stuart's suggestion.=20 >=20 > D. Brooke Mobile >=20 > On Mar 15, 2016, at 5:13 PM, Rich Kwas =20 >wrote: >=20 >> I don't seem to have any .db-tmp files anywhere . >> They would be in the same "globals " folder as the main database=20 >>right? >>=20 >> I did not have error logging turned on. >> Just enabled that. >>=20 >> Nothings changed in this site really for years and years. Same db,=20 >>same admin area, same everything. Just every now and then this occurs. >>=20 >>=20 >>=20 >>=20 >> On Tuesday, March 15, 2016 4:43 PM, Stuart Tremain=20 >> wrote: >>=20 >>=20 >> Are you getting a lot of .db-tmp files being written for the db ? >>=20 >> If you are then there could be a problem with either your code or=20 >>some of the content, based on the fact that the site has been=20 >>operational for many years, I would open the .db file and check the=20 >>content, also check your error log.txt >>=20 >> Kind regards >>=20 >> Stuart Tremain >> IDFK Web Developments >> AUSTRALIA >> webdna@idfk.com.au >>=20 >>=20 >>=20 >>=20 >>=20 >>> On 16 Mar 2016, at 08:09, Rich Kwas =20 >>>wrote: >>>=20 >>> I already using [COMMITDATABASE db=3DFileName] in all the admin pages= =20 >>>where they edit these ads... >>>=20 >>> Problem still pops up every now and then, like today again. >>>=20 >>> Thoughts on the "Safe Write" setting? >>>=20 >>>=20 >>> On Tuesday, March 15, 2016 4:01 PM, Stuart Tremain=20 >>> wrote: >>>=20 >>>=20 >>> From memory, there was a bug in =93Automatically commit databases to=20 >>>disk after modification=94, I wonder if this was associated with your=20 >>>problem ? >>>=20 >>> You can always add [COMMITDATABASE db=3DFileName] after the=20 >>>modification just to make sure. >>>=20 >>> Kind regards >>>=20 >>> Stuart Tremain >>> IDFK Web Developments >>> AUSTRALIA >>> webdna@idfk.com.au >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>>> On 16 Mar 2016, at 07:15, Rich Kwas =20 >>>>wrote: >>>>=20 >>>> Is it safe to disable ""Safe Write for Database" in Preferences??? >>>>=20 >>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>> Safe Write DB: >>>> Enabled by default. Sets the WebDNA engine to create a temporary fil= e=20 >>>>when writing the contents of a database to disk. The temporary file=20 >>>>contents are then moved to the original database file after the entir= e=20 >>>>database is completely flushed to disk. This helps to eliminate=20 >>>>corruption of the original database file if there is an interruption=20 >>>>during the database write process. >>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D >>>>=20 >>>> If I disable this setting will all changes be written to the db on=20 >>>>the HD immediately, without that need for a temporary file? >>>>=20 >>>> I've been having this issue "again" where a client says they make=20 >>>>changes to ad listings stored in the database, but then all the=20 >>>>changes are gone a few moments later. Like they never were altered in= =20 >>>>the first place.... >>>>=20 >>>> This site has been for over 10 years and the admin area has not been= =20 >>>>changed recently or much over that time span... >>>>=20 >>>> There is no consistency to this issue. >>>> It happens (like today) but may not happen for days or weeks. >>>>=20 >>>> I'm wondering if this "temporary file" and the original database on=20 >>>>disk are somehow under some circumstances getting out of sync. >>>>=20 >>>> The db isn't that large, having 2,111 records,151 Fields and using=20 >>>>4,759K of ram. >>>>=20 >>>> I'm wondering if disabling "Safe Write" might be an option to try an= d=20 >>>>prevent this in the future. >>>>=20 >>>> Very frustrating for the client.I can't seem to duplicate it=20 >>>>myself,but I believe them when they say it happens.I may have posted=20 >>>>about this issue in the past as well. >>>>=20 >>>>=20 >>>> I'm on Windows Server2008 using vers.6.2 >>>> I have nearly 1gb of unused ram on the server, plenty of hard drive=20 >>>>space.... >>>>=20 >>>>=20 >>>> I've attached a screen capture of my Preferences in case anything=20 >>>>else can be tinkered with. >>>>=20 >>>>=20 >>>> --------------------------------------------------------- This=20 >>>>message is sent to you because you are subscribed to the mailing list= =20 >>>>. To unsubscribe, E-mail to: archives:=20 >>>>http://mail.webdna.us/list/talk@webdna.us Bug Reporting:=20 >>>>support@webdna.us >>>=20 >>> --------------------------------------------------------- This=20 >>>message is sent to you because you are subscribed to the mailing list=20 >>>. To unsubscribe, E-mail to: archives:=20 >>>http://mail.webdna.us/list/talk@webdna.us Bug Reporting:=20 >>>support@webdna.us >>>=20 >>>=20 >>> --------------------------------------------------------- This=20 >>>message is sent to you because you are subscribed to the mailing list=20 >>>. To unsubscribe, E-mail to: archives:=20 >>>http://mail.webdna.us/list/talk@webdna.us Bug Reporting:=20 >>>support@webdna.us >>=20 >> --------------------------------------------------------- This=20 >>message is sent to you because you are subscribed to the mailing list=20 >>. To unsubscribe, E-mail to: archives:=20 >>http://mail.webdna.us/list/talk@webdna.us Bug Reporting:=20 >>support@webdna.us >>=20 >>=20 >> --------------------------------------------------------- This=20 >>message is sent to you because you are subscribed to the mailing list=20 >>. To unsubscribe, E-mail to: archives:=20 >>http://mail.webdna.us/list/talk@webdna.us Bug Reporting:=20 >>support@webdna.us > --------------------------------------------------------- This=20 >message is sent to you because you are subscribed to the mailing list=20 >. To unsubscribe, E-mail to: archives:=20 >http://mail.webdna.us/list/talk@webdna.us Bug Reporting:=20 >support@webdna.us >=20 >=20 > --------------------------------------------------------- This=20 >message is sent to you because you are subscribed to the mailing list=20 >. To unsubscribe, E-mail to: archives:=20 >http://mail.webdna.us/list/talk@webdna.us Bug Reporting:=20 >support@webdna.us =20 --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us . Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] "Safe Write for Database" setting.... (Terry Wilson 2016)
  2. Re: [WebDNA] "Safe Write for Database" setting.... ("Terry Wilson" 2016)
  3. Re: [WebDNA] "Safe Write for Database" setting.... (Donovan Brooke 2016)
  4. Re: [WebDNA] "Safe Write for Database" setting.... (Rich Kwas 2016)
  5. Re: [WebDNA] "Safe Write for Database" setting.... (Donovan Brooke 2016)
  6. Re: [WebDNA] "Safe Write for Database" setting.... (Stuart Tremain 2016)
  7. Re: [WebDNA] "Safe Write for Database" setting.... (Kenneth Grome 2016)
  8. Re: [WebDNA] "Safe Write for Database" setting.... (Rich Kwas 2016)
  9. Re: [WebDNA] "Safe Write for Database" setting.... (Stuart Tremain 2016)
  10. Re: [WebDNA] "Safe Write for Database" setting.... (Donovan Brooke 2016)
  11. Re: [WebDNA] "Safe Write for Database" setting.... (Rich Kwas 2016)
  12. Re: [WebDNA] "Safe Write for Database" setting.... (Stuart Tremain 2016)
220 Make sure your client doesn't have two people working on stuff at the=20 same time. That could lead to trouble if they're both updating the=20 same record. Terry W On Tue, 15 Mar 2016 22:09:31 -0500 Donovan Brooke wrote: If a reboot doesn=92t fix it, maybe write some troubleshooting code. =20 On the form, write to a debug file exactly what webdna is going to write to the database. Directly after, do a search on that database and write to the debug file the result of what happened after the database transaction. Surround the entire thing in [elapsedtime] and record that as well. =20 Sincerely, Donovan =20 =20 =20 =20 =20 On Mar 15, 2016, at 9:52 PM, Rich Kwas wrote: =20 > Like usual, it happened 2x on 2 different ad listings I'm being told,=20 >and been stable ever since. > That's what makes it so frustrating. Can't seem to pin down the why. >=20 > I'll keep my eye on those error logs.. >=20 >=20 >=20 >=20 > On Tuesday, March 15, 2016 7:45 PM, Donovan Brooke =20 >wrote: >=20 >=20 > This means that you haven't had any issues with your database. (No=20 >need to mess with safe write) =20 >=20 > Watch that your error logs don't get too big, now that you've turned=20 >them on.=20 >=20 > Lots of stuff can change on a server in 10 years ;-) (Even if you=20 >don't touch it) >=20 > I'd start with Stuart's suggestion.=20 >=20 > D. Brooke Mobile >=20 > On Mar 15, 2016, at 5:13 PM, Rich Kwas =20 >wrote: >=20 >> I don't seem to have any .db-tmp files anywhere . >> They would be in the same "globals " folder as the main database=20 >>right? >>=20 >> I did not have error logging turned on. >> Just enabled that. >>=20 >> Nothings changed in this site really for years and years. Same db,=20 >>same admin area, same everything. Just every now and then this occurs. >>=20 >>=20 >>=20 >>=20 >> On Tuesday, March 15, 2016 4:43 PM, Stuart Tremain=20 >> wrote: >>=20 >>=20 >> Are you getting a lot of .db-tmp files being written for the db ? >>=20 >> If you are then there could be a problem with either your code or=20 >>some of the content, based on the fact that the site has been=20 >>operational for many years, I would open the .db file and check the=20 >>content, also check your error log.txt >>=20 >> Kind regards >>=20 >> Stuart Tremain >> IDFK Web Developments >> AUSTRALIA >> webdna@idfk.com.au >>=20 >>=20 >>=20 >>=20 >>=20 >>> On 16 Mar 2016, at 08:09, Rich Kwas =20 >>>wrote: >>>=20 >>> I already using [COMMITDATABASE db=3DFileName] in all the admin pages= =20 >>>where they edit these ads... >>>=20 >>> Problem still pops up every now and then, like today again. >>>=20 >>> Thoughts on the "Safe Write" setting? >>>=20 >>>=20 >>> On Tuesday, March 15, 2016 4:01 PM, Stuart Tremain=20 >>> wrote: >>>=20 >>>=20 >>> From memory, there was a bug in =93Automatically commit databases to=20 >>>disk after modification=94, I wonder if this was associated with your=20 >>>problem ? >>>=20 >>> You can always add [COMMITDATABASE db=3DFileName] after the=20 >>>modification just to make sure. >>>=20 >>> Kind regards >>>=20 >>> Stuart Tremain >>> IDFK Web Developments >>> AUSTRALIA >>> webdna@idfk.com.au >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>>> On 16 Mar 2016, at 07:15, Rich Kwas =20 >>>>wrote: >>>>=20 >>>> Is it safe to disable ""Safe Write for Database" in Preferences??? >>>>=20 >>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>> Safe Write DB: >>>> Enabled by default. Sets the WebDNA engine to create a temporary fil= e=20 >>>>when writing the contents of a database to disk. The temporary file=20 >>>>contents are then moved to the original database file after the entir= e=20 >>>>database is completely flushed to disk. This helps to eliminate=20 >>>>corruption of the original database file if there is an interruption=20 >>>>during the database write process. >>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D >>>>=20 >>>> If I disable this setting will all changes be written to the db on=20 >>>>the HD immediately, without that need for a temporary file? >>>>=20 >>>> I've been having this issue "again" where a client says they make=20 >>>>changes to ad listings stored in the database, but then all the=20 >>>>changes are gone a few moments later. Like they never were altered in= =20 >>>>the first place.... >>>>=20 >>>> This site has been for over 10 years and the admin area has not been= =20 >>>>changed recently or much over that time span... >>>>=20 >>>> There is no consistency to this issue. >>>> It happens (like today) but may not happen for days or weeks. >>>>=20 >>>> I'm wondering if this "temporary file" and the original database on=20 >>>>disk are somehow under some circumstances getting out of sync. >>>>=20 >>>> The db isn't that large, having 2,111 records,151 Fields and using=20 >>>>4,759K of ram. >>>>=20 >>>> I'm wondering if disabling "Safe Write" might be an option to try an= d=20 >>>>prevent this in the future. >>>>=20 >>>> Very frustrating for the client.I can't seem to duplicate it=20 >>>>myself,but I believe them when they say it happens.I may have posted=20 >>>>about this issue in the past as well. >>>>=20 >>>>=20 >>>> I'm on Windows Server2008 using vers.6.2 >>>> I have nearly 1gb of unused ram on the server, plenty of hard drive=20 >>>>space.... >>>>=20 >>>>=20 >>>> I've attached a screen capture of my Preferences in case anything=20 >>>>else can be tinkered with. >>>>=20 >>>>=20 >>>> --------------------------------------------------------- This=20 >>>>message is sent to you because you are subscribed to the mailing list= =20 >>>>. To unsubscribe, E-mail to: archives:=20 >>>>http://mail.webdna.us/list/talk@webdna.us Bug Reporting:=20 >>>>support@webdna.us >>>=20 >>> --------------------------------------------------------- This=20 >>>message is sent to you because you are subscribed to the mailing list=20 >>>. To unsubscribe, E-mail to: archives:=20 >>>http://mail.webdna.us/list/talk@webdna.us Bug Reporting:=20 >>>support@webdna.us >>>=20 >>>=20 >>> --------------------------------------------------------- This=20 >>>message is sent to you because you are subscribed to the mailing list=20 >>>. To unsubscribe, E-mail to: archives:=20 >>>http://mail.webdna.us/list/talk@webdna.us Bug Reporting:=20 >>>support@webdna.us >>=20 >> --------------------------------------------------------- This=20 >>message is sent to you because you are subscribed to the mailing list=20 >>. To unsubscribe, E-mail to: archives:=20 >>http://mail.webdna.us/list/talk@webdna.us Bug Reporting:=20 >>support@webdna.us >>=20 >>=20 >> --------------------------------------------------------- This=20 >>message is sent to you because you are subscribed to the mailing list=20 >>. To unsubscribe, E-mail to: archives:=20 >>http://mail.webdna.us/list/talk@webdna.us Bug Reporting:=20 >>support@webdna.us > --------------------------------------------------------- This=20 >message is sent to you because you are subscribed to the mailing list=20 >. To unsubscribe, E-mail to: archives:=20 >http://mail.webdna.us/list/talk@webdna.us Bug Reporting:=20 >support@webdna.us >=20 >=20 > --------------------------------------------------------- This=20 >message is sent to you because you are subscribed to the mailing list=20 >. To unsubscribe, E-mail to: archives:=20 >http://mail.webdna.us/list/talk@webdna.us Bug Reporting:=20 >support@webdna.us =20 --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us . "Terry Wilson"

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:

WebCat2_Mac RETURNs in .db (1997) WebCat2b13MacPlugIn - [showif][search][/showif] (1997) Sending mail (2001) required fields (1998) Too Much Rootbeer Free Offer (1997) WebCatalog Mac 2.1b3 (1997) Date search - yes or no (1997) totals (1997) RE: Error: template (1997) Copy, Move, Create Folders (1998) Problem displaying search result (1997) Popup Menu Options (1998) WebCommerce: Folder organization ? (1997) Email notification to one of multiple vendors ? (1997) [OT] DOD again (2003) PSC recommends what date format yr 2000??? (1997) b12 cannot limit records returned and more. (1997) WC2.0 Memory Requirements (1997) WebCat/CyberStudio Compatibility (1998) Some Advise needed (1997)