Exeption in table.Flush

[Thomas Flemming]

Hi Ruslan,

I tried again:
Just doing database.flush every 100 records, but the crash still remains at 
almost the same filesize.

Seems like the vdb cant grow beyond 2,1 GB.

Can you please check this?
At least 4gb should be possible on Windows XP/NTFS.

Regards,
Tom


Am 17.05.2010 16:31, schrieb Ruslan Zasukhin:
> On 17/5/10 4:31 PM, "Thomas Flemming"<tf at ttqv.com>  wrote:
>
> Hi Thomas,
>
>>> 2) what cache size ?
>> 1MB
>
> Wow
>
> Why so small ???
> For such big db as 2 GB only 1MB cache ...
>
>
> Recommended size is 10-20 Mb.
> And if you have big db then you can go up to 30-50Mb and more easy.
>
>
>>> 3) if db.Flush() give the same error?
>>> It is a good idea to have in your loop db.Flush() for each N records,
>>> Where N can be 100 or 1000, up to you.
>>
>>
>> didnt try, but will do so now.
>> Currently I have table.flush after every single addrecord.
>> Maybe not good?
>
> Aha, after each record this is best possible from point of stability but
> slow.
>
> If you will set N = 100 you can go faster.
>
>
>> Btw: do I always have to take care about the "flushing" on my own?
>> Or do you anyway flush on vdb.Close?
>
> We do flush on close, but you better have own.
>
> Future flushes places will be replaced on COMMITs.
>
>

-- 
/****************************************
**   Dipl.-Ing. Thomas Flemming
**   Software Development
**
**   Touratech AG
**   Auf dem Zimmermann 7-9
**   D-78078 Niedereschach
**
**   mail  tf at ttqv.com
**   fon   +49 (0) 7728 9279-206
**   fax   +49 (0) 7728 9279-29
**
**   http://www.ttqv.com
**   http://www.touratech.de
**
**   ... und immer dem Pfeil nach!
***************************************/