Re: [sqlite] help: there is some error

You should try with an ARM library. I think the ARM linker should not appreciate an X86 library. On 3/21/06, 杰 张 <[EMAIL PROTECTED]> wrote: > > hello everyone, > I just want to test the connection between C and sqlite3, When I > cross compile my program there is an error baffled me? > >

Re: [sqlite] SQLITE_ENABLE_MEMORY_MANAGEMENT: AV when Open / Close DB in different threads

You have to call open & close in the same thread, and in each thread if needed. " The returned sqlite3* can only be used in the same thread in which it was created. It is an error to call sqlite3_open() in one thread then pass the resulting

Re: [sqlite] Busy management

I'm currently writing a C wrapper (yes, I know, yet another ... ;) for my applications. But it's a good training to learn. So I was looking at the best generic way to manage busy statement. My first idea was to use the callback option as it seems to be much simplier and it would benefit to all

Re: [sqlite] Busy management

I was wondering if there was limitations for one of the 2 methods. If they are identicals, I know which one I will use. Thanks a lot. On 3/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > "Ludovic Ferrandis" <[EMAIL PROTECTED]> wrote: > > Thanks for yo

Re: [sqlite] Busy management

an polling. It does however assume that there > are co-operating threads and processes. > JS > > Jay Sprenkle wrote: > > On 3/3/06, Ludovic Ferrandis <[EMAIL PROTECTED]> wrote: > > > >>I want to manage the SQLITE_BUSY error like this: If it fails, sl

[sqlite] Busy management

Hi, Newbie to SQLite, so maybe my question will seems trivial. I want to manage the SQLITE_BUSY error like this: If it fails, sleep X ms then try the command Y times. I found 2 ways to do it: - First is to manage a loop like: tryIt = X; do { err = sqlite3_exec(...) } while (err ==