Thanks for the help. That makes a lot of sense. So, I guess I should create
my own structure to store the prepared statements and then iterate over them
in my close method :)
Thanks again.
- Jon
Roger Binns wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> junkJon wrote:
>> here is how I close my DB:
>> --------------------------------------------
>> void MySqlite::Close()
>> {
>> sqlite3_stmt *stmt;
>> while((stmt = sqlite3_next_stmt(m_db, 0)) != 0)
>> {
>> sqlite3_finalize(stmt);
>> }
>>
>> sqlite3_close(m_db);
>> m_db = NULL;
>> }
>
> That is generally not a good way to close things if other components are
> involved. Basically you finalized all prepared including those
> belonging to fts. Then when fts went to clean up after itself, it
> finalized its own statements again and you got the crash.
>
> Roger
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFI3Y5YmOOfHg372QQRAt6KAKCNicX3foQM5Utl1+w0mlRd/+5vPACffrMe
> IRH1K8K2flpGH2w9ShV17iM=
> =2j6F
> -----END PGP SIGNATURE-----
> _______________________________________________
> sqlite-users mailing list
> [email protected]
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
>
--
View this message in context:
http://www.nabble.com/Issue-when-enabling-fts3-in-sqlite3-tp19698347p19698820.html
Sent from the SQLite mailing list archive at Nabble.com.
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
