[
https://issues.apache.org/jira/browse/COUCHDB-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665778#action_12665778
]
Jan Lehnardt commented on COUCHDB-217:
--------------------------------------
A cursory glance at the code reveals the issue: Before writing the document
that we attach the attachment (heh) to, we don't know the revision id of the
to-be written document to put into the attachment structure. When we return
from writing the document, we know the revision id, but our attachment has been
written already and we would need to change it again to put in the new revision
id and that would bump the revision id again.
It might be doable a layer further down, but I don't wont to mess with the core
document writing stuff here now :)
For anyone willing to look into this at couch_db:update_docs/4.
> Store Revision of Attachments
> -----------------------------
>
> Key: COUCHDB-217
> URL: https://issues.apache.org/jira/browse/COUCHDB-217
> 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.
