vdbs destroyed because of out-of-memory

[Ruslan Zasukhin]

On 1/8/14, 12:00 PM, "Thomas Flemming" <tf at qvgps.com> wrote:

Hi Thomas,

> as you know, I'm not using VServer, just VNET with local vdb's.
> Is this journaling still working?

yes

This is great feature of Valentina DB :)

   local engine and vserver are 99% identical.


> Even if Windows crashes e.g. because of
> power failure (very common problem for our software, because its also used in
> car-pcs)?

right
 
> Tom
> 
> 
> Am 08.01.2014 08:44, schrieb Ruslan Zasukhin:
>> On 1/7/14, 2:45 PM, "Thomas Flemming" <tf at qvgps.com> wrote:
>> 
>> Hi Thomas,
>> 
>>>> This should not happens in 5.0 and better thanks to journal on db.
>>> 
>>> can you please explain more detailed, why 5 is more reliable then 4.9?
>>> What exactly makes the difference with journal on db?
>> 
>> Because in 5.0 added jornaling,
>> This means that new info go into DB, but prev modified pages go to journal.
>> Kind of double fixation of changes
>> 
>> If happens crash, then on the next db.open engine checks journal,
>> And if it see not completed app, it returns database in the latest good
>> state.

-- 
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]