Hello, The next problem occurs since switching to sqlite 3.8; it was never observed in 3.7.17 or earlier. I have an application in which I insert a lot of data in a transaction, started by executing "begin transaction", after having executed "PRAGMA synchronous = 0" and "PRAGMA journal_mode = MEMORY". After that the inserts take place. When I finally try to execute the "commit" statement, I get an SQLITE_BUSY status. This error does not happen when I remove the journal_mode statement. The latest version tested is 3.8.0.2. I build the library with the next defines: THREADSAFE=2 SQLITE_ENABLE_FTS4 SQLITE_ENABLE_FTS3_PARENTHESIS SQLITE_ENABLE_RTREE SQLITE_ENABLE_COLUMN_METADATA SQLITE_ENABLE_STAT3 SQLITE_CORE The application is built with the same defines, except SQLITE_CORE which is then ommitted.
Frank De prins [cid:image002.jpg@01CE45B7.374DA450] Advisory & Software for Real Estate & Facility Management Sneeuwbeslaan 20 b3 ∙ 2610 Antwerp ∙ Belgium t. +32 (0) 3 829 04 95 frank.depr...@mcs.fm<mailto:serge.vanginde...@mcs.fm> ∙ www.mcs.fm<http://www.mcs.fm> ------------------------------------------------------------ http://www.mcs.fm/legal/email-disclaimer/
_______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
