issue_comments

Docs: https://github.com/simonw/sqlite-utils/blob/ebc802f7ff0e640b6ae11ea525290fea0115228c/docs/cli.rst#inserting-binary-data-from-files

Inserting files by piping them in should work - but since a filename cannot be derived this will need a --name blah.gif option.

cat blah.gif | sqlite-utils insert-files files.db files - --name=blah.gif

Test command: sqlite-utils insert-files gifs.db *.gif \ -c filename:filename \ -c filepath:filepath \ -c absolutepath:absolutepath \ -c sha256:sha256 \ -c md5:md5 \ -c content:content \ -c mtime:mtime \ -c ctime:ctime \ -c mtime_iso:mtime_iso \ -c ctime_iso:ctime_iso \ -c size:size \ --pk absolutepath

One idea: sqlite-utils insert-files

It could work something like this:

sqlite-utils insert-files files.db /tmp/blah.jpg /tmp/foo.gif \
  --table files \
  -c key:filename -c hash:sha256 -c body:content \
  --pk key

This would insert those two image files into the database in a table called files with a schema that looks something like this:

sql CREATE TABLE files ( key text primary key, hash text, body blob );

The -c key:filename options here are the most interesting: they let you create the table with a specific layout. The bit before the : is the column name. The bit after the : can be a range of different things:

• filename - just the filename
• filepath - the full filepath (provided on the command-line)
• absolutepath - the filepath expanded to start with /home/... or whatever
• sha256 - the SHA256 of the contents
• md5 - the MD5
• content - the binary content itself
• mtime - the mtime (floating point timestamp)
• ctime - the ctime (floating point timestamp)
• mtime_iso - the mtime as an ISO datetime
• ctime_iso - the mtime as an ISO datetime
• size - the size of the file in bytes