-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://www.sqlite.org/lang_corefunc.html
The hex line is out of alphabetical order and should be two lines earlier.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Those measurements asume that you store each blob in a seperate file. So
the raw file access seems slower for smaller blob sizes.
If you use external blob storage do it in raw clusters like i suggested
in a previous post (size limit 32/64 MB) and store your blobs on page
boundaries (page size
In reference to your needs one more suggestion :
>> If you put the blobs outside of a sqlite database and store your
householding, indexing data inside your sqlite data i would suggest to
use journal mode = on because your journal file and database file
without the blobs has a small amount
From : http://www.sqlite.org/pragma.html#pragma_journal_mode
The OFF journaling mode disables the rollback journal completely. No
rollback journal is ever created and hence there is never a rollback
journal to delete. The OFF journaling mode disables the atomic commit
and rollback
On 29.03.2013 20:17, Jeff Archer wrote:
I have previously made an apparently bad assumption about this so now I
would like to go back to the beginning of the problem and ask the most
basic question first without any preconceived ideas.
This use case is from an image processing application. I
On 29.03.2013 19:42, Jeff Archer wrote:
From: "James K. Lowden"
To: sqlite-users@sqlite.org
Your experiment is telling you different: transaction control costs more
than I/O.
But shouldn't transactions be disabled when journal_mode = off? Maybe that
is a faulty
6 matches
Mail list logo