Re: [WebDNA] To Commitdatabase or Not to Commitdatabase
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 108405
interpreted = N
texte = Hi Govinda, 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] ? And how do you normally avoid data loss? Are you using the = [commitdatabase...] ?? Palle=20 On 01/02/2012, at 20.23, Govinda wrote: >> Hi all, >>=20 >> I have set up a WebNDA 7 server using Mac OS X Lion Client. I sort of = performs ok but I have had a problem where Apache has closed down on me = twice over the past 24 hours and since my data is stored in RAM and I do = not commit to database at every change to the content of RAM - well I = loose data - heavily. >>=20 >> So what is the best alternative to "Automatically commit databases to = disk after modification" ? And with an ambition of NOT loosing any data. >>=20 >> Any good suggestions? >>=20 >=20 >=20 > Hi Palle >=20 > Just use [commitdatabase...], in code, when where you want to be sure = the data in a db, in RAM, gets written to disk, like e.g. after a = [replace]/[append]. >=20 > -G >=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
Associated Messages, from the most recent to the oldest:
Hi Govinda, 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] ? And how do you normally avoid data loss? Are you using the = [commitdatabase...] ?? Palle=20 On 01/02/2012, at 20.23, Govinda wrote: >> Hi all, >>=20 >> I have set up a WebNDA 7 server using Mac OS X Lion Client. I sort of = performs ok but I have had a problem where Apache has closed down on me = twice over the past 24 hours and since my data is stored in RAM and I do = not commit to database at every change to the content of RAM - well I = loose data - heavily. >>=20 >> So what is the best alternative to "Automatically commit databases to = disk after modification" ? And with an ambition of NOT loosing any data. >>=20 >> Any good suggestions? >>=20 >=20 >=20 > Hi Palle >=20 > Just use [commitdatabase...], in code, when where you want to be sure = the data in a db, in RAM, gets written to disk, like e.g. after a = [replace]/[append]. >=20 > -G >=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
Palle Bo Nielsen
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:
suffix mapping for NT? (1997)
generating unique IDs (2000)
Separate SSL Server (1997)
Re[4]: Problem with new formvariables (2000)
Test (2003)
Cookies (1999)
New Line In grep (2003)
OPEN MARKET PATENTS SOUND ECOMMERCE ALARM (1998)
group searching problem (2002)
Refering page (1998)
' add to cart ' or ' sku ' problem (1998)
Webcat/Webmerchant part II (1998)
Instructions for Digest (1997)
Languages (1997)
How far do [showif]s go? (1997)
WebCatalog Work (2001)
Plugin or CGI or both (1997)
Bad cookie (1998)
Date problems-more (1997)
[subtotal] and others (1997)