On Thu, Jun 23, 2011 at 10:18:05AM +0200, Thorsten Kersting scratched on the
wall:
> i finalizeevery statement right before closing the database, and every
> finalize returns sqlite_ok. but then closing returns sqlite_busy.
Then you're missing some. You can use sqlite3_next_stmt() to find it.
i finalizeevery statement right before closing the database, and every
finalize returns sqlite_ok. but then closing returns sqlite_busy.
Am 22.06.2011 19:04, schrieb Pavel Ivanov:
>> there are no statements open, as far as i can see.
> Your eyes can miss something. Does sqlite3_close return SQLIT
> there are no statements open, as far as i can see.
Your eyes can miss something. Does sqlite3_close return SQLITE_OK or
something else?
Pavel
On Wed, Jun 22, 2011 at 12:36 PM, Thorsten Kersting
wrote:
> there are no statements open, as far as i can see.
>
> On 06/22/2011 05:29 PM, Pavel Iva
there are no statements open, as far as i can see.
On 06/22/2011 05:29 PM, Pavel Ivanov wrote:
> Do you check result code of connection closing? Is it successful?
> If it's not successful then some statements are still active and
> reading transaction is still open. That could be the reason of err
Do you check result code of connection closing? Is it successful?
If it's not successful then some statements are still active and
reading transaction is still open. That could be the reason of error
in write process.
Pavel
On Wed, Jun 22, 2011 at 10:58 AM, Thorsten Kersting
wrote:
> i use ope
i use openmpi fo parallelization, an c++ as the interface to sqlite.
in my program one process only writes into the database, and the other
processes read at the beginning, and then never do anything with it. But
even when i close the database-connection of the non-writing processes,
my write pr
6 matches
Mail list logo
