couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Newson (JIRA)" <>
Subject [jira] Commented: (COUCHDB-259) Ability to store abitrary data in attachment stubs
Date Wed, 18 Feb 2009 18:46:01 GMT


Robert Newson commented on COUCHDB-259:

Perhaps the couchdb file format already includes checksums for detecting corruption within
attachments (but, if it does, I haven't found it). My intention was to put an md5 on every
attachment, which could include 600M videos, etc. Specifically, calling crypto:md5() seems
preferable, assuming it's native. 

The Ruby idea is interesting but, again, I wanted the digest calculated on the data being
added and stored with the attachment to detect corruption, generating it in a view is only
equivalent if you never regenerate it, which is fragile.

> Ability to store abitrary data in attachment stubs
> --------------------------------------------------
>                 Key: COUCHDB-259
>                 URL:
>             Project: CouchDB
>          Issue Type: Wish
>          Components: Database Core
>    Affects Versions: 0.8.1
>            Reporter: Sho Fukamachi
>            Priority: Minor
>             Fix For: 0.8.1
> I suggest the ability to store arbitrary data in line with single attachments to a doc.
The mooted use is to store metadata about that attachment.
> For example, a current attachment:
> m['_attachments']
> => {"yamanote.jpg"=>{"content_type"=>"image/jpeg", "stub"=>true, "length"=>382613}}
> Desired behaviour is to be able to insert persistent metadata like so:
> m['_attachments']
> => {"yamanote.jpg"=>{"content_type"=>"image/jpeg", "stub"=>true, "length"=>382613,
"width" => 800, "height" => 600, "md5" => "95de7a118ee28824afa8d2ad8fe5819f"}}
> And many other use cases according to media type.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message