couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Deibert <>
Subject Re: Storage limitations?
Date Sun, 10 Nov 2013 21:10:56 GMT
Each comment is normally a very small amount of information, and id,
userName, a date and a small text field. Probably no more than a short
sentence on average. Why do I need to go through the trouble of creating
new comment docs for each? This totally complicates the comment read code
(there will 1000 reads to every 1 write, at least) both in the UI and the
db for no reason.

On Sun, Nov 10, 2013 at 1:34 PM, Jens Alfke <> wrote:

> On Nov 9, 2013, at 11:47 AM, Robert Newson <<mailto:
>>> wrote:
> attachments are different to documents. They're stored as a series of
> binary chunks and so they can be streamed in and out, you can go large
> with attachments.
> But on the other hand, all attachments will get copied during a database
> compaction, so they slow down the process and require more free disk space.
> If you have many gigabytes of attachments, you might consider storing them
> externally and putting URL links in the documents.
> As for comments, just add new documents for each comment and use a
> view (,
> to bring the article
> and comment thread together. No need to update a document that way.
> Yup. The guide <<>> has a
> chapter-long example of a blog application that shows how to do comments
> this way.
> —Jens

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message