Woody Wu wrote: > The manual says that it should to rollback after sqlite3_step() returns > SQLITE_BUSY as long as > the current statment is in a transaction. Is this true?
Yes. If you have a transaction, you must _eventually_ commit or rollback. > Why I cannot just sleep for a while and redo the sqlite3_step()? In theory, you could do this, but sqlite3_step() can fail again. Anyway, sleeping is better done in a callback registered with sqlite3_busy_handler(). If you have such a callback, the only cases where you can get SQLITE_BUSY is when your callback decides that sleeping does not make sense, or when there is a deadlock. Regards, Clemens _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
