On Mar 6, 2009, at 1:48 PM, Marcus Grimm wrote: > I just want to add another hint that I learned yesterday: > > when sqlite3_step() returns SQLITE_LOCKED be aware > that sqlite3_reset() will most likely also return > SQLITE_LOCKED and thus it is necessary to repeat calling > it until it returns SQLITE_OK.
This is incorrect. If an error is encountered by sqlite3_step() and an error code returned, the same error code is returned by the subsequent call to sqlite3_reset() or sqlite3_finalize(). sqlite3_reset() returning SQLITE_LOCKED does not mean you have to call it again. > Maybe it would be agood idea to have these kind of > info somewhere bundled in the sqlite docs? > I found it sometimes difficult to get such issues > extracted or collected from the sqlite pages, resulting > in a lot of try and error loops and generating traffic > on the mailing list... :-) The website could be much improved by including examples. Feel free to create a wiki page or two if you have any ideas for them. Dan. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
