Re: [WebDNA] "Safe Write for Database" setting....
This WebDNA talk-list message is from 2016
It keeps the original formatting.
numero = 112638
interpreted = N
texte = 221 Also, this reminds of the same problem that happened with me long ago = when I cleverly let two different domains access the same database. In = the eyes of WebDNA, each domain had its own path the the DB, and thus = two different ram-based instances of the same DB. If one updated the DB, = then the other one had no knowledge of this, and if it did an update, it = would overwrite what the other one did. I resolved this by putting it in = the globals folder and used a global path. You don't have something like that going on, do you? Terry On Mar 15, 2016, at 8:18 PM, Terry Wilson
wrote: > Make sure your client doesn't have two people working on stuff at the = same time. That could lead to trouble if they're both updating the same = record. >=20 > Terry W >=20 > On Tue, 15 Mar 2016 22:09:31 -0500 > Donovan Brooke wrote: > If a reboot doesn=92t fix it, maybe write some troubleshooting code. > 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. > Sincerely, > Donovan > 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, = and been stable ever since. >> That's what makes it so frustrating. Can't seem to pin down the why. >> I'll keep my eye on those error logs.. >> On Tuesday, March 15, 2016 7:45 PM, Donovan Brooke = wrote: >> This means that you haven't had any issues with your database. (No = need to mess with safe write) Watch that your error logs don't get too = big, now that you've turned them on. Lots of stuff can change on a = server in 10 years ;-) (Even if you don't touch it) >> I'd start with Stuart's suggestion. D. Brooke Mobile >> On Mar 15, 2016, at 5:13 PM, Rich Kwas = wrote: >>> I don't seem to have any .db-tmp files anywhere . >>> They would be in the same "globals " folder as the main database = right? >>> I did not have error logging turned on. >>> Just enabled that. >>> Nothings changed in this site really for years and years. Same db, = same admin area, same everything. Just every now and then this occurs. >>> On Tuesday, March 15, 2016 4:43 PM, Stuart Tremain = wrote: >>> Are you getting a lot of .db-tmp files being written for the db ? >>> If you are then there could be a problem with either your code or = some of the content, based on the fact that the site has been = operational for many years, I would open the .db file and check the = content, also check your error log.txt >>> Kind regards >>> Stuart Tremain >>> IDFK Web Developments >>> AUSTRALIA >>> webdna@idfk.com.au >>>> On 16 Mar 2016, at 08:09, Rich Kwas = wrote: >>>> I already using [COMMITDATABASE db=3DFileName] in all the admin = pages where they edit these ads... >>>> Problem still pops up every now and then, like today again. >>>> Thoughts on the "Safe Write" setting? >>>> On Tuesday, March 15, 2016 4:01 PM, Stuart Tremain = wrote: >>>> =46rom memory, there was a bug in =93Automatically commit databases = to disk after modification=94, I wonder if this was associated with your = problem ? >>>> You can always add [COMMITDATABASE db=3DFileName] after the = modification just to make sure. >>>> Kind regards >>>> Stuart Tremain >>>> IDFK Web Developments >>>> AUSTRALIA >>>> webdna@idfk.com.au >>>>> On 16 Mar 2016, at 07:15, Rich Kwas = wrote: >>>>> Is it safe to disable ""Safe Write for Database" in Preferences??? >>>>> =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 = file when writing the contents of a database to disk. The temporary file = contents are then moved to the original database file after the entire = database is completely flushed to disk. This helps to eliminate = corruption of the original database file if there is an interruption = 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 >>>>> If I disable this setting will all changes be written to the db on = the HD immediately, without that need for a temporary file? >>>>> I've been having this issue "again" where a client says they make = changes to ad listings stored in the database, but then all the changes = are gone a few moments later. Like they never were altered in the first = place.... >>>>> This site has been for over 10 years and the admin area has not = been changed recently or much over that time span... >>>>> There is no consistency to this issue. >>>>> It happens (like today) but may not happen for days or weeks. >>>>> I'm wondering if this "temporary file" and the original database = on disk are somehow under some circumstances getting out of sync. >>>>> The db isn't that large, having 2,111 records,151 Fields and using = 4,759K of ram. >>>>> I'm wondering if disabling "Safe Write" might be an option to try = and prevent this in the future. >>>>> Very frustrating for the client.I can't seem to duplicate it = myself,but I believe them when they say it happens.I may have posted = about this issue in the past as well. >>>>> I'm on Windows Server2008 using vers.6.2 >>>>> I have nearly 1gb of unused ram on the server, plenty of hard = drive space.... >>>>> I've attached a screen capture of my Preferences in case anything = else can be tinkered with. >>>>> --------------------------------------------------------- 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 >>>> --------------------------------------------------------- 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 >>> --------------------------------------------------------- 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 >> --------------------------------------------------------- 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 > --------------------------------------------------------- > 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:
221 Also, this reminds of the same problem that happened with me long ago = when I cleverly let two different domains access the same database. In = the eyes of WebDNA, each domain had its own path the the DB, and thus = two different ram-based instances of the same DB. If one updated the DB, = then the other one had no knowledge of this, and if it did an update, it = would overwrite what the other one did. I resolved this by putting it in = the globals folder and used a global path. You don't have something like that going on, do you? Terry On Mar 15, 2016, at 8:18 PM, Terry Wilson wrote: > Make sure your client doesn't have two people working on stuff at the = same time. That could lead to trouble if they're both updating the same = record. >=20 > Terry W >=20 > On Tue, 15 Mar 2016 22:09:31 -0500 > Donovan Brooke wrote: > If a reboot doesn=92t fix it, maybe write some troubleshooting code. > 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. > Sincerely, > Donovan > 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, = and been stable ever since. >> That's what makes it so frustrating. Can't seem to pin down the why. >> I'll keep my eye on those error logs.. >> On Tuesday, March 15, 2016 7:45 PM, Donovan Brooke = wrote: >> This means that you haven't had any issues with your database. (No = need to mess with safe write) Watch that your error logs don't get too = big, now that you've turned them on. Lots of stuff can change on a = server in 10 years ;-) (Even if you don't touch it) >> I'd start with Stuart's suggestion. D. Brooke Mobile >> On Mar 15, 2016, at 5:13 PM, Rich Kwas = wrote: >>> I don't seem to have any .db-tmp files anywhere . >>> They would be in the same "globals " folder as the main database = right? >>> I did not have error logging turned on. >>> Just enabled that. >>> Nothings changed in this site really for years and years. Same db, = same admin area, same everything. Just every now and then this occurs. >>> On Tuesday, March 15, 2016 4:43 PM, Stuart Tremain = wrote: >>> Are you getting a lot of .db-tmp files being written for the db ? >>> If you are then there could be a problem with either your code or = some of the content, based on the fact that the site has been = operational for many years, I would open the .db file and check the = content, also check your error log.txt >>> Kind regards >>> Stuart Tremain >>> IDFK Web Developments >>> AUSTRALIA >>> webdna@idfk.com.au >>>> On 16 Mar 2016, at 08:09, Rich Kwas = wrote: >>>> I already using [COMMITDATABASE db=3DFileName] in all the admin = pages where they edit these ads... >>>> Problem still pops up every now and then, like today again. >>>> Thoughts on the "Safe Write" setting? >>>> On Tuesday, March 15, 2016 4:01 PM, Stuart Tremain = wrote: >>>> =46rom memory, there was a bug in =93Automatically commit databases = to disk after modification=94, I wonder if this was associated with your = problem ? >>>> You can always add [COMMITDATABASE db=3DFileName] after the = modification just to make sure. >>>> Kind regards >>>> Stuart Tremain >>>> IDFK Web Developments >>>> AUSTRALIA >>>> webdna@idfk.com.au >>>>> On 16 Mar 2016, at 07:15, Rich Kwas = wrote: >>>>> Is it safe to disable ""Safe Write for Database" in Preferences??? >>>>> =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 = file when writing the contents of a database to disk. The temporary file = contents are then moved to the original database file after the entire = database is completely flushed to disk. This helps to eliminate = corruption of the original database file if there is an interruption = 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 >>>>> If I disable this setting will all changes be written to the db on = the HD immediately, without that need for a temporary file? >>>>> I've been having this issue "again" where a client says they make = changes to ad listings stored in the database, but then all the changes = are gone a few moments later. Like they never were altered in the first = place.... >>>>> This site has been for over 10 years and the admin area has not = been changed recently or much over that time span... >>>>> There is no consistency to this issue. >>>>> It happens (like today) but may not happen for days or weeks. >>>>> I'm wondering if this "temporary file" and the original database = on disk are somehow under some circumstances getting out of sync. >>>>> The db isn't that large, having 2,111 records,151 Fields and using = 4,759K of ram. >>>>> I'm wondering if disabling "Safe Write" might be an option to try = and prevent this in the future. >>>>> Very frustrating for the client.I can't seem to duplicate it = myself,but I believe them when they say it happens.I may have posted = about this issue in the past as well. >>>>> I'm on Windows Server2008 using vers.6.2 >>>>> I have nearly 1gb of unused ram on the server, plenty of hard = drive space.... >>>>> I've attached a screen capture of my Preferences in case anything = else can be tinkered with. >>>>> --------------------------------------------------------- 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 >>>> --------------------------------------------------------- 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 >>> --------------------------------------------------------- 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 >> --------------------------------------------------------- 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 > --------------------------------------------------------- > 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:
Database Security (1998)
SKU (1997)
PCS Frames (1997)
New WebDNA Solutions ... (1997)
do you have a webcatalog tool you want to sell? (1999)
How do I pass [cart] when user clicks back (2000)
Almost a there but..bye bye NetCloak (1997)
WebCat 5 Admin Bug (2004)
Separate SSL Server (1997)
[WebDNA] Search using CL (2017)
text size limitation (1997)
SKU (1997)
Looking for a host (1997)
Math (1997)
RE: Cart Template (1997)
AD Error Msg (1997)
Re[2]: running WebCatalog under Apache on NT? (2000)
forms and variables (1998)
[OT] How'd it go, Sal? (2006)
getting URL variable with '%20' in the variable name (2006)