[ 
https://issues.apache.org/jira/browse/COUCHDB-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033500#comment-13033500
 ] 

Gabor Ratky commented on COUCHDB-259:
-------------------------------------

It's been a while since there was any activity on this ticket. I see 1.2 as Fix 
Version and while low priority, would love to see this show up in trunk.

In our scenario, the attachments are an important part of the initial data load 
process, we get CSV/TSV data from our partners that we import and create 
documents out of it. The _attachments stubs would be the preferred way to store 
these kinds of information:

 - Date when the attachment was imported
 - The revpos when the attachment was imported (so we can decide whether a 
newer file was uploaded since)
 - Other useful information about the content of the attachment itself.

Both MD5 and metadata suggestions in the past sounds like great scenarios as 
well.

The easy workarond is just to keep this information under doc.attachments 
instead of doc._attachments, but that needs to be kept in sync. If an 
attachment is deleted, the metadata will still exist under doc.attachments.

Anybody else watching this share their possible useful scenarios to get this 
bumped? :)

> 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: 1.2
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to