In another thread talking about Commit, Tim mentioned that there was a commit interval that could be set depending on one's appetite for risk. I've been through the component reference and I can't seem to find any such setting. How do you specify that the server should not return until the commit is written to the disk (zero interval) ?

On 4/4/2013 8:09 AM, Arthur Williams wrote:
> In another thread talking about Commit, Tim mentioned that there was a commit interval that could be set depending on one's appetite for risk. I've been through the component reference and I can't seem to find any such setting. How do you specify that the server should not return until the commit is written to the disk (zero interval) ?

I believe you mean this :

http://www.elevatesoft.com/manual?action=viewtopic&id=edb2sql&topic=Transactions


and specifically the "Flushing Data to Disk During a Commit" section

Raul

Raul wrote:

>>
I believe you mean this :

http://www.elevatesoft.com/manual?action=viewtopic&id=edb2sql&topic=Transactions


and specifically the "Flushing Data to Disk During a Commit" section

Raul
<<

Actually no that wasn't it. However reading that led me to the Caching topic which led to the TEDBSession.ForceBufferFlush which is the setting for which I was looking.

Arthur,

<< In another thread talking about Commit, Tim mentioned that there was a
commit interval that could be set depending on one's appetite for risk. I've
been through the component reference and I can't seem to find any such
setting. How do you specify that the server should not return until the
commit is written to the disk (zero interval) ? >>

I think that was a discussion about the upcoming EDB 3.x.  In EDB 2.x, you
have the ForceBufferFlush setting, as you have found, that will make sure
that any writes are actually flushed to disk.

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com