> I read that you are working in a large enterprise and I had the idea of a
> webapp
> for applying for holidays/vacation. You basically have a calender and users
> can
> apply for taking days off and their supervisor has to approve it.
> Creating the basic app would be quite easy but modeling th
; From: rich...@eaglefeed.me
> Subject: Re: simple use cases for couch db
> Date: Thu, 18 Nov 2010 20:45:43 +
>
> When I think for usecases of CouchDB I tend to think in *documents*.
> After all, CouchDB is a document oriented database. So everything that would
> require me to
I've been using it for querying read only data, specifically car data. So I
see it as being really useful for storing factual data (catalogs) that
doesn't change, because once a 2010 Toyota Camry is released it never
becomes a 2009 Jeep Cherokee. The applications I'm involved in use car data
for ge
At SXSW, we started using CouchDB last fall because we needed to
create an API for 3rd-party developers to write mobile apps using our
event schedule data. So we copied the needed data from a collection of
legacy databases into a CouchDB, threw in a few views, and, voila... a
fast, well-documented,
On Wed, 2010-11-17 at 22:18 -0600, Andy wrote:
Without touching the replication or offline/online stuff as I haven't
used it yet...
CouchDB is useful any time that you would be using a serialized (aka XML
aka JSON aka YAML) column in a relational database. It also works better
for mainly read si
So Ive been obsessively reading about and researching CouchDB over the past
couple weeks. I even wrote my own Java client since the ones on the market
weren't up to my standards :) I've probably read 200 articles on google
explaining the downsides to CouchDB. I've read the Use Cases on Couch
