couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Anderson (JIRA)" <>
Subject [jira] Commented: (COUCHDB-217) Store Revision of Attachments
Date Sat, 14 Feb 2009 19:33:59 GMT


Chris Anderson commented on COUCHDB-217:

I think this ticket is doable, and I especially like the ability to provide per-attachment

However, I think it will require a change to the database file format, so if this is going
to happen it should happen for 0.9.

This would be a medium-difficult patch to pull off, so if someone has done some CouchDB internals
work and wants to take it to the next level, this is a good opportunity.

You'll want to see couch_db:doc_flush_binaries/2 for one place the internal attachment metadata
is manipulated. There are a few other spots in the source you'd have to touch as well. Just
getting the rev onto the attachment metadata is step one. Once that's happened, using that
rev as the etag will be easy.

> Store Revision of Attachments
> -----------------------------
>                 Key: COUCHDB-217
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>            Reporter: Sven Helmberger
> I'm writing some multi-app hosting thing and besides using couchdb as database it also
stores all images and stylesheets and scripts etc for the applications as attachments. I have
one couchdb database per app and
> store all resources on a single document to keep the same relative hierarchical structure
I have in my apps.
> I can now fetch that document and use it to quickly find out the name, lenght and content-type
of all my attachments. When the document revision changes I know that at least one of the
attachments has changed, but I don't know which.
> Wouldn't it be possible to store the revision in which the attachment was created with
the attachment?
> _attachments could then contain these revisions as additional property and couchdb could
use that revision as ETag when serving the attachment content which would be better than using
the documents revision like it is now. 
> I don't know the code, so I don't know wheter this is possible..

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

View raw message