Stephan, On Thu, Sep 19, 2013 at 1:09 AM, Stephan Beal <sgb...@googlemail.com> wrote:
> On Thu, Sep 19, 2013 at 10:06 AM, Igor Korot <ikoro...@gmail.com> wrote: > > > OK, so I guess I have to call sqlite3_free(). > > Now, I do have to execute "ROLLBACK" statement, right? > > > > Correct - IMO, you have all the pieces in the right place, you just need to > free the errmsg string. (i assume you have a corresponding COMMIT somewhere > down further).) > Yes, I do. ;-) > > But... you're not using the error message: > > printf( "Error executing query: %s", sqlite3_errmsg( m_handle ) ); > sqlite3_exec( handle, "ROLLBACK", 0, 0, &errmsg ); > > instead you're using sqlite3_errmsg(), which means you don't need errmsg > unless you use it at another place which isn't shown here. What's the > difference between &errmsg and calling sqlite3_errmsg()? i'm not sure there > is one, and one of the astute listers will probably see this and explain > the difference (if any) to us. > It would be interesting to know the difference (if any). At least I (and probably someone else) will know what is better to use. Thank you. > > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > http://gplus.to/sgbeal > _______________________________________________ > 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
