> If the 'COMMIT' reports that no transaction is active, why is the
> JOURNAL_MODE pragma still complaining about it being within a transaction?
> Am I missing something here?
Probably you have some not finalized SELECT statements still active.
To check that you can call sqlite3_close - it will fail in such case
too.
Pavel
On Tue, Apr 12, 2011 at 9:17 AM, Jaco Breitenbach
<jjbreitenb...@gmail.com> wrote:
> Dear experts,
>
> My application makes use of several data files attached to the SQLite
> database. Data files are attached on demand as they become necessary. I'm
> experimenting with the WAL journalling mode as a speed/performance
> optimisation. Unfortunately I'm having some difficulty setting the journal
> mode to WAL on the attached databases.
>
> Here is some diagnostic output:
> Setting database 'DC2_DB_20110412' journal mode to WAL.
> sqlite3_exec('0x1f8f57a8','COMMIT',NULL,NULL,'cannot commit - no transaction
> is active') = SQLITE_ERROR
> sqlite3_exec('0x1f8f57a8','PRAGMA
> DC2_DB_20110412.JOURNAL_MODE=WAL',NULL,NULL,'cannot change into wal mode
> from within a transaction') = SQLITE_ERROR
>
> The two sqlite3_exec() statements are executed directly after each other.
> If the 'COMMIT' reports that no transaction is active, why is the
> JOURNAL_MODE pragma still complaining about it being within a transaction?
> Am I missing something here?
>
> I'm working with SQLite 3.7.3.
>
> Best regards,
> Jaco
> _______________________________________________
> 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
