On Nov 28, 2007 11:09 PM, Oleg Broytmann <[EMAIL PROTECTED]> wrote: > On Wed, Nov 28, 2007 at 10:53:05PM +0100, Bart wrote: > > > 2. The difference between the snippet and the way SQLObject uses Binary > > > is that the snippet uses parameter(s) and SQLObject generates query > > > strings. Well, query strings work for 100M binary files... > > > > You meant *don't* work for...? > > Work. I slurped a file of 70M, put into the DB, got it back and put into > test.dat file, then compared the original file with test.dat - no > difference. So SQLObject (at least with SQLite/PySQLite2) *can* handle > BLOBs/pickles of that size.
Ah, you inserted it with something other than SQLObject then fetched it with SQLObject? That'd mean pysqlite2 is doing its job decoding blobs while fetching, which I don't think is too surprising; it's getting the data in there that's the problem. I've been hacking in my sqlobject installation to convert it from literal to parameter style. It seems to work, but there's probably a reason SQLObject uses literal instead of parametric queries, and it's a bit of an overhaul. It just occurred to me that for my project at least, it would probably be cleaner to just add my own wrapping code that just updates the database without SQLObject knowing about it. Always fun to figure out things like that after an hour or two of hacing, particularly when you're doing it in your site packages:) --Bart ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ sqlobject-discuss mailing list sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
