Stephan,

On Thu, Sep 19, 2013 at 12:46 AM, Stephan Beal <sgb...@googlemail.com>wrote:

> On Thu, Sep 19, 2013 at 8:55 AM, Igor Korot <ikoro...@gmail.com> wrote:
>
> > Can I reuse errmsg variable like this or do I have to call sqlite3_free()
>
> and then execute "ROLLBACK" statement?
> >
>
> Per the API docs:
>
> ** ^If an error occurs while evaluating the SQL statements passed into
> ** sqlite3_exec(), then execution of the current statement stops and
> ** subsequent statements are skipped.  ^If the 5th parameter to
> sqlite3_exec()
> ** is not NULL then any error message is written into memory obtained
> ** from [sqlite3_malloc()] and passed back through the 5th parameter.
> ** To avoid memory leaks, the application should invoke [sqlite3_free()]
> ** on error message strings returned through the 5th parameter of
> ** of sqlite3_exec() after the error message string is no longer needed.
> ** ^If the 5th parameter to sqlite3_exec() is not NULL and no errors
> ** occur, then sqlite3_exec() sets the pointer in its 5th parameter to
> ** NULL before returning.
>

OK, so I guess I have to call sqlite3_free().
Now, I do have to execute "ROLLBACK" statement, right?

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

Reply via email to