Thiago Mello wrote:
Yes, in my callback() functions I have some sqlite_exec() functions.
How I can avoid this?
Well you have to rewrite your code, store the complete result of one
query before calling sqlite_exec* again. You can probably achieve a
similar result with some SQL wizardry, but I
Thiago Mello wrote:
Yes, in my callback() functions I have some sqlite_exec() functions.
How I can avoid this?
It is safe to call sqlite_exec() from within a callback. By "safe"
I mean that you should never get back an SQLITE_MISUSE. But if you
are trying to use an inner sqlite_exec() to
Yes, in my callback() functions I have some sqlite_exec() functions.
How I can avoid this?
Thanks,
Thiago
Em Dom, 2004-03-07 às 15:10, Peter escreveu:
> Thiago Mello wrote:
> > about the sqlite_compile(), Im using simple call back function.
>
> Are you calling any other sqlite_* function
Thiago Mello wrote:
about the sqlite_compile(), Im using simple call back function.
Are you calling any other sqlite_* function within the callback? Doing
that will probably get you the "call out of sequence" error.
Regards
P.
Hello Thiago,
http://www.sqlite.org/cvstrac/wiki?p=MultiThreading
Regards,
-- Tito
On 24 feb 2004, at 10:31, Thiago Mello wrote:
Hi,
Im using Sqlite in my application, and I want to two process bem able
to
insert records in a table, SQLite support process concurrence, or I
have
to do this
Hi,
Im using Sqlite in my application, and I want to two process bem able to
insert records in a table, SQLite support process concurrence, or I have
to do this in my program?
If I have to do this in my program some one have a idea how can I do
this I tried to use some things already.
Thanks,
6 matches
Mail list logo
