On 7 Apr 2014, at 12:46am, Larry Brasfield <larry_brasfi...@iinet.com> wrote:
> I, too, thought there should be something like that. > Here is the .help portion for a shell enhancement I wrote awhile ago: > .blobextract TABLE COL ROW FILE ?DB? Extract DB blob to a file. Table, > column and row must specify a blob selected by: > SELECT column FROM DB.table WHERE rowid = row . > FILE may be '-' for extraction to stdout. > .blobreplace TABLE COL ROW FILE ?DB? Replace DB blob with file content, > otherwise like .blobextract except that DB blob > size must equal file size. (zeroblob(filesize)) Good idea for the function to create a file. However, to conform closer to expectations of how SQL works, had you thought of creating a SQLite function which accepted a filename as a parameter and returned the contents of the file as the appropriate hex string ? It could, of course, use significant memory if you tried to use it with a long file. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
