Thanks. I'll hold off on checking the result of every sqlite3_bind_* for now.
It's unlikely I'm using a finalized statement otherwise I believe I would get a given crash much more often. The sqlite3_prepare_v2 statements that are failing only fail occasionally, not every time. But I'll double check. Rick On Jul 19, 2012, at 12:19 PM, Pavel Ivanov wrote: > SQLite is written in such a way that no call to sqlite3_bind_* can > cause memory corruption per se. It can return error if you are trying > to bind wrong parameter and your app can corrupt memory if along with > call to sqlite3_bind_* it changes some internal structures. But calls > to sqlite3_* functions can cause corruption only if you try to work > with already closed connection or with already finalized statement. > > > Pavel _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
