Do I need to lock a table during a FLUSH when using VSDK C++ API in multi-threaded app?

[Matthew Jew]

On Aug 16, 2006, at 2:45 AM, Ivan Smahin wrote:

> Hello Matthew,
>
> Wednesday, August 16, 2006, 11:57:38 AM, you wrote:
>
>
>> I do use a lock for each table.
>
>> However, I am assuming that I can have one thread work with table 1,
>> and another thread working with table 2. This is okay in VSDK 2, yes?
>
> Hmm,  I don't think so at least for writing.
> Please,  take a look on Valentina server. It is ready-to-use solution
> for multi-usage environment.

I do not want to use Valentina server; I use the VSDK 2.x C++ API inside
my application that uses strictly local DBs.

My understanding was that there was some support for multiple threads
in version 2 of Valentina. If not, what is the point of record locking?

What exactly has changed from version 1 to version 2 of VSDK related
to multi-thread support? Anything? Version 1 required me to lock the
entire Valentina engine, so that only one thread at a time could do
a Valentina call. Has this changed in version 2 or not? It was my  
understanding
that it had. What is the story?

- Matthew