Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1283)
Subject: Re: show/list
From: Filippo Fadda <filippo.fadda@programmazione.it>
In-Reply-To: 
 <CAPNuaCheU49xtq9A=CTSH_Ja6VJ1gNJ73QfaudSgf42+uvRcuw@mail.gmail.com>
Date: Fri, 15 Nov 2013 00:48:15 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <85298D98-4E0B-4AFD-AF1E-2BD32547D52A@programmazione.it>
References: <OFAD52ABB5.8D41CB8B-ONC1257C23.005C5637-C1257C23.005C6AB2@ptb.de>
 <75175787-0293-4918-9CC3-0CE24B8B41C6@programmazione.it>
 <CAHdjipLZRKLxx6-_c34ZroyO=e0B79UCuqfHQ=m6J8C2=D9KQQ@mail.gmail.com>
 <DA90231F-CB4D-45BC-88E2-956997079383@programmazione.it>
 <CAHdjipJ0SFR+u3SY5_AF0wcGGikFO9-9K3k6akFRuAh8a=ymhg@mail.gmail.com>
 <528536B9.5040000@gmail.com> <5285397E.1010802@alwaysreformed.com>
 <CALDn6=gfrz5b1T6yPfJ-TpyunNtCoD4ObfB7+8B+8K6JACvmkQ@mail.gmail.com>
 <CAFVT+gDHiVXi7sO07ieFawLuN+HvgLQDcBXhMo7nQ6S-qsGSng@mail.gmail.com>
 <CAPNuaCheU49xtq9A=CTSH_Ja6VJ1gNJ73QfaudSgf42+uvRcuw@mail.gmail.com>
To: user@couchdb.apache.org


On Nov 14, 2013, at 10:49 PM, Stanley Iriele wrote:

> That argument ca be made about just about any software design..but
> CouchDB has this very nice separation of "what you get back" vs "what =
is
> stored". If i have a gian document and I want an array of of say =
player
> installs from my document..why should i load up the entire thing when =
i
> only need a small tid bit of it?....If i had a class document and i =
wanted
> the first 3 students..why then should I pull out other needless =
information
> from the database?...

If you have a giant document, there is something wrong in your design. =
If you have a 'class' document, you don't store the students inside the =
'class', but you store a single document per student.

> ...when people come from the LAMP stack world they get very nervous =
about
> rethinking the delegation of responsibilities...One thing that i keep
> seeing is..."I dont need a server in the middle because list/shows =
takes
> care of it"....then the following is "they do not replace app
> serves"...this is a strange argument but so sum it up...app servers =
are not
> replaced by list show functions and should not be...there are times =
when
> all your need is a few random calls and MAYBE..for some cases you =
don't
> need one....but to be honest they can exist in both spaces just =
fine...

I'm not nervous :-) and I don't come directly from LAMP. I'm 37 years =
old and I wrote almost everything: drivers, windows shell extensions, =
client server apps, three tier apps, I have used object oriented =
databases, etc. What I see here is that just a simple join can't be done =
using a show or a list. And if I can't make a join, the "CouchApp =
Server" doesn't fit my needs, because I can't write any serious =
application. I think the "CouchApp Server" idea is cool, but the actual =
implementation is weak. And I think, IMO, that CouchDB is still =
primarily a database and not an application server. But this is just my =
vision.

-Filippo