• Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.11
    • Component/s: None
    • Labels:


      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..

        Issue Links


          Gavin made changes -
          Link This issue is depended upon by COUCHDB-259 [ COUCHDB-259 ]
          Gavin made changes -
          Link This issue blocks COUCHDB-259 [ COUCHDB-259 ]
          Paul Joseph Davis made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Assignee Paul Joseph Davis [ paul.joseph.davis ]
          Fix Version/s 0.11 [ 12313841 ]
          Fix Version/s 0.10 [ 12313694 ]
          Resolution Fixed [ 1 ]
          Chris Anderson made changes -
          Fix Version/s 0.10 [ 12313694 ]
          Sven Helmberger made changes -
          Field Original Value New Value
          Link This issue blocks COUCHDB-259 [ COUCHDB-259 ]
          Sven Helmberger created issue -


            • Assignee:
              Paul Joseph Davis
              Sven Helmberger
            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created: