Govinda; sorry about the = mess in my latest mail - I got tired = yesterday.
*** last = question from yesterday - clarified ***
Do you know if <Automatically commit databases to disk = after modification> is the same as having a <commitdatabase = ...> at the end of all/any [append] / [replace] within a = codebase.
Yes, AFAIK, this is correct = ^^^.
Meaning that they are equal but = absolute better than Flushdatabases.
But this ^^^ , = I do not understand what you are asking.
*** = last question from yesterday - clarified = ***
The reason for my question = above was to figure out if my next move should be = enabling <Automatically commit databases to disk after = modification> or just taking on the task of doing a = <commitdatabase...> after (more or less) all of my [append] or = [replace] tags.
If I was to gain speed / = performance by choosing one over the other then that is what I am = looking = for.
/Palle
On = 01/02/2012, at 19.21, Palle Bo Nielsen wrote:
Hi all,
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.
So what is the best = alternative to "Automatically commit = databases to disk after modification" ? And with an ambition of NOT = loosing any data.
Any good = suggestions?
= --Apple-Mail=_90A65EBA-D326-498B-833D-F5636480DC43--
Associated Messages, from the most recent to the oldest:
--Apple-Mail=_90A65EBA-D326-498B-833D-F5636480DC43 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Govinda, Thanks. I seem to remember that the
actually commits after a certain amount of changes. Let's = say it actually commits after 1.000 changes - anyone has any info on = this. And even better; maybe a way to set this variable to example = commit every 50 changes or some other value (controlled by the WebDNA = host - in this case me) /Palle On 02/02/2012, at 19.38, Palle Bo Nielsen wrote: > Govinda; sorry about the mess in my latest mail - I got tired = yesterday. >=20 >=20 > *** last question from yesterday - clarified *** >=20 >> Do you know if is the same as having a at the end of = all/any [append] / [replace] within a codebase. >=20 > Yes, AFAIK, this is correct ^^^. >=20 >> Meaning that they are equal but absolute better than Flushdatabases. >=20 > But this ^^^ , I do not understand what you are asking. >=20 > *** last question from yesterday - clarified *** >=20 >=20 > The reason for my question above was to figure out if my next move = should be enabling or just taking on the task of doing a = after (more or less) all of my [append] or [replace] tags. >=20 > If I was to gain speed / performance by choosing one over the other = then that is what I am looking for. >=20 > /Palle >=20 >=20 > On 01/02/2012, at 19.21, Palle Bo Nielsen wrote: >=20 >> 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 >> /Palle >> --------------------------------------------------------- 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 >=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 --Apple-Mail=_90A65EBA-D326-498B-833D-F5636480DC43 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii