AW: Journaling

[Ruslan Zasukhin]

On 4/20/12 2:55 PM, "Fabian Kneubuehl" <support at ysd.ch> wrote:

> Ivan,
> 
> Me again. If I use transaction control I use it specifically, as in the
> example mentioned in this mail. But in another simple example I wouldn't:
> 
> The user has to enter 1000 patient addresses. She/he will work the whole day
> entering these addresses. If I never call DB-Flush she/he loses all entries.
> Now I flush each entry - but I see no sense for a transaction control here.
> OK I could make my own timer routine or flush only each 10th entry...

Fabian,

I do not understand all these questions :(((((

WHY ??? Why you will not make db.Flush in above scneario?


Even in 4.9 you should have some flush for above app
On each OK click.

SHE types  address 1, click something OK or NEW button
And your app do db.Flush()

What wonders you ??

Why you think that during few hours nobody save data to disk?


> You see this small overhead with how much connections? I have no small
> example. I run a lot of procedures at the same time (all as used in all day
> work, like inserting BLOBs, Pictures, deleting, generating invoices,
> inserting appointments, deleting them...

-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]