Hi, Simon,
On Thu, Sep 19, 2013 at 5:16 AM, Simon Slavin <slav...@bigfraud.org> wrote: > > On 19 Sep 2013, at 9:09am, Stephan Beal <sgb...@googlemail.com> wrote: > > > What's the > > difference between &errmsg and calling sqlite3_errmsg()? > > No difference in terms of the result, they're just to cope with two > different programming styles. The function is provided for situations > where you have already lost touch with &errmsg or never kept it to start > with. > > By the way, Igor, if this code is being shipped away from your own > personal computer you should theoretically be checking the result returned > by the execution of BEGIN too. Depending on what goes wrong, it may be the > BEGIN which fails, and the result code from subsequent operations wouldn't > tell you what the real problem is. Though you may have just simplified > your code for posting. > Yes, the check code omitted for simplicity. And thank you for clarification. It is hard to imagine the situation when the variable will go out of scope, but that's OK. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
