On Apr 3, 2009, at 9:03 PM, Radcon Entec wrote: > According to the documentation, assuming I'm reading it correctly, > and assuming there are no locks on the database, and assuming the > query sent to sqlite3_prepare_v2() was valid, sqlite3_step() should > return either SQLITE_ROW or SQLITE_DONE. I am seeing a different > result after executing a DELETE query: it is returning SQLITE_OK. > This makes sense for a query that returns no rows, such as a DELETE > query, but it doesn't match the documentation. Is this normal > behavior? > Thank you very much.
On this page (http://www.sqlite.org/c3ref/step.html), it says: > In the legacy interface, the return value will be either SQLITE_BUSY, SQLITE_DONE, SQLITE_ROW, SQLITE_ERROR, or SQLITE_MISUSE. With the "v2" interface, any of the other result codes or extended result codes might be returned as well. That's how one gets SQLITE_OK, rather than SQLITE_DONE. d. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
