At 15:37 20.04.2009, D. Richard Hipp wrote: >Ticket #3811 has been addressed by enhancing the documentation to >explain that journal_mode changes are only guaranteed to work if they >occur prior to the first transaction. Whether or not a journal_mode >change works after the start of the first transaction is undefined.
Thanks! >Even as I type this message, it occurs to me that we should probably >lock down the journal_mode at the start of the first transaction. >Otherwise, there are a bazillion cases of journal_mode changes at >strange times (such as in the middle of a nested transaction) that >could cause problems (segfaults) even if their behavior is undefined. In this case, it would make sense IMO that setting the journal_mode should generally (and especially after the 1st transaction) report the active mode so applications can check if the journal_mode change was in fact effective. Ralf _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
