Also note that it's often possible to open a corrupted database and
operate on it with no error, nothing goes bad until you touch a
corrupted row/table/index. We've found that doing a PRAGMA
integrity_check is effective for discovering any/all corruption in a
database early and avoiding random
, at 6:50 PM, Bob Ebert wrote:
I wonder if anyone is in a position to compare and contrast the
journal_mode and synchronous settings with the various ext3 journal
modes?
Up until now we've been using ext3 with data=ordered, and sqlite3 with
synchronous=normal, journal_mode=delete. We're
I wonder if anyone is in a position to compare and contrast the
journal_mode and synchronous settings with the various ext3 journal
modes?
Up until now we've been using ext3 with data=ordered, and sqlite3 with
synchronous=normal, journal_mode=delete. We're on an embedded system
with a very high
Here's an example skeleton for a custom collation. (Using UTF8
encoding, change the declarations as necessary.)
// declarations
typedef int SQLiteCompare_t (void *, int, const void *, int,
const void *);
int MyCompare(void *userData, int str1Len, const UTF8 *str1, int
Look at the page_size pragma. I believe SQLite always reads/writes in
page_size chunks. You might also want to adjust cache_size.
http://sqlite.org/pragma.html
--Bob
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Is journal_mode a future optimization? The atomic commit documentation
(http://sqlite.org/atomiccommit.html) as well as the pragma docs
(http://www.sqlite.org/pragma.html) make tantalizing references to this
potentially useful optimization, but I've searched the 3.5.1 and 3.5.8
sources and I
To: General Discussion of SQLite Database
Subject: Re: [sqlite] PRAGMA journal_mode not implemented?
Bob Ebert wrote:
Is journal_mode a future optimization? The atomic commit
documentation
(http://sqlite.org/atomiccommit.html) as well as the pragma docs
(http://www.sqlite.org/pragma.html
