On 1 Jul 2014, at 2:22am, Keith Medcalf <kmedc...@dessus.com> wrote:
> IF ResultCode == A_OK YipeeKiAiii else OhShitItDidntWork; > > Seems pretty straightforward to me. You handle the result codes you know > what to do with, and everything that remains means your program should > explode immediately and very very loudly dumping ALL relevant information > (ie, error code, statement, inout data, output data, etc.) > > In other words, there is no point checking for error conditions which you > cannot handle. Instead you just die. Okay, right. Now, where in the documentation does it tell us "what to do with" each error ? Or alternatively, how should my app die ? Suppose _step() gets a result of SQLITE_PROTOCOL. Can I just execute _step() again and assume I didn't miss a row ? Or will the next _step() always just return SQLITE_DONE ? Should I actually _reset() and start again ? Or is my statement so messed up I can only _finalize() it ? Is it necessary to _finalize() it ? Or is my whole database connection now invalid and I should quit without having to even _close() ? It's this sort of documentation which is not present. And it's that sort of thing that I think Eric is asking about. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
