Somewhat off topic, but if you wanted to use Mr. Hipp's suggestion for storing large data out of the DB, and wanted some form of fault-tolerant I/O, you might consider "libjio" (http://users.auriga.wearlab.de/~alb/libjio/). I've not personally used it, but it seems interesting.
-joe On Thu, 15 Jul 2004 10:53:32 -0400, D. Richard Hipp <[EMAIL PROTECTED]> wrote: > > > Paul Malcher wrote: > > Dennis Volodomanov wrote: > > > >> Hello all, > >> > >> Can someone please tell me if there's any limit on the size of data > >> stored in one field (BLOB) in SQLite3? > >> > >> > > Hi, I spent all day yesterday picking through SQLite3 docs, trying to > > solved a problem that turned out was my own fault. I never saw any > > mention of 16 MB Blob limit. Either way I intend to find out , I'm gonna > > lay some serious abuse on SQLite today and see what can and cannot > > handle. I'll check the docs again maybe I missed it either way I'll let > > you know what I find out. > > The 16MB limit was in SQLite 2.8 file format. In most installations, > a separate limitation of 1MB is imposed by the schema layer. To relax > that limit, you have to change MAX_BYTES_PER_ROW in the sqliteInt.h > file and recompile. > > In SQLite version 3.0, there is no theoretical limit on the size of > BLOBs. (The limit is really about 4.6e+18 bytes, but file size limits > will come into play first so you will never get to that size.) However, > the same MAX_BYTES_PER_ROW constraint is still in place. So with a > default build, the maximum BLOB size is still about 1MB. You can, > I suppose, increase MAX_BYTES_PER_ROW to whatever value you want and > recompile. But, if you make MAX_BYTES_PER_ROW really big, I think > you will find that performance gets very bad for very large rows. > > For large BLOBs, your best bet is to store the BLOB data in a separate > file and store the name of the separate file in the SQLite database. > > -- > D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565 > >
