Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of email.workbench@gmail.com
 designates 209.85.161.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:date:x-google-sender-auth:message-id:subject
         :from:to:content-type;
        b=r0xde/0wCuPbIuTWg4yNW8xGYuEyjUSIF+8vbjsc6kLoOPQIsW7CnyGc7BrfMWO7sA
         O3J//HvThXX4W5VLizzaVLZf2ZVcSvGaFHC1CxGnVr2AGCpUu8GX4q9aw8MXt86JDmdi
         sLfFyu5Uf7oTC0Q9S4n1qCFXsGZ7uKHzgnzH0=
MIME-Version: 1.0
Sender: email.workbench@gmail.com
Date: Mon, 1 Nov 2010 15:40:21 -0400
Message-ID: <AANLkTikU2gwwKLibGZ-uNngXi99-en05U7aPQCWjMNKL@mail.gmail.com>
Subject: User app activity Logging
From: Zdravko Gligic <zgligic@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi Folks,

I have a community use case where I need to track:
a) user id
b) user action
c) doc._id
e) date.time

Wiki talks about short doc._id values making a huge difference on
storage and performance. I am assuming that the same arguments also
apply to view indexing as it uses the same b-tree indexing.

Somewhere I have read that numeric values compare faster than strings,
so I am thinking about using decimals for date.time in yymmdd.hhmmss
format. Comments on this?

For parts of the application, I need to keep track of all such logs in
order to retain "user's slice" of what they have done. That is I would
need to keep longer the ByUserId view, while ByDocId and/or ByDateTime
views can be reduced for all of the logs that are older than x number
of days.

While it is somewhat of an open ended question, can you share some
design suggestions?

Thanks again,
teslan