Am Wed, 9 Jan 2008 10:20:31 -0800 (PST) schrieb Ken: > Definately use 3.5.4. > > Not sure how to determine at compile time if the threadsafe part is > enabled. You can always compile yourself to guarantee its set, thats > what I do. > > sqlite will lock the database file for you automatically. Your > threads do not need to implement locking. But they do need to handle > in some fashion. SQLITE_BUSY and/or SQLITE_LOCKED error codes. > > You should also look at "Begin", "Begin Exlusive" and "Begin > Immediate" sql commands. > > As a user you don't get to pick the lock state, sqlite does that > automatically for you. You must handle the return codes suche as > SQLITE_BUSY, SQLITE_LOCKED etc. > > I don't have any simple examples available, sorry.
I don't understand how to use the sqlite3_io_methods. It seems I need a sqlite3_file. Not sure I get it from the API. The sqlite3_open call returns an int. So how do I use this? Perhaps you could sketch some pseudo code or paste some code where locking with SQLITE_BUSY and SQLITE_LOCKED is used. regards Andreas ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
