Closed csroli closed 7 years ago
No reasons using the legacy one. Maybe there was no v2 when it's written first time? Anyway, I'll work on it. Thanks for reporting!
Check this commit out. https://github.com/iwongu/sqlite3pp/commit/4d1386971e5570b0a072d34844c470b31251ff9b The change is published in v1.0.8
Hello!
Do you have a specific reason for using sqlite3_prepare instead of
sqlite3_prepare_v2
?The
v2
form has an advantage, that it can recompile the statement on schema change, instead of returning SQLITE_SCHEMA error code. I had a problem related to this, and changingsqlite3_prepare
tosqlite3_prepare_v2
resolved that.Also, the documentation states: