[
https://issues.apache.org/jira/browse/COUCHDB-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674729#action_12674729
]
Sho Fukamachi commented on COUCHDB-259:
---------------------------------------
Robert: For small things it's probably OK. JS isn't *that* slow. Wouldn't want
to run a 600M video through it, though. I do think it's a valid approach though
- the idea of "generative views" is fascinating. For large files I'd want to
consider writing the view in ruby, though, which has a C md5/sha1 module.
Sven: It's relevant to that ticket but I think you're touching on a much bigger
subject there, that of revisions for individual attachments, which is an issue
in its own right and beyond the scope of this one.
> Ability to store abitrary data in attachment stubs
> --------------------------------------------------
>
> Key: COUCHDB-259
> URL: https://issues.apache.org/jira/browse/COUCHDB-259
> 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.
