From user-return-4268-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Fri Apr 03 14:45:19 2009 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 36452 invoked from network); 3 Apr 2009 14:45:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Apr 2009 14:45:19 -0000 Received: (qmail 92551 invoked by uid 500); 3 Apr 2009 14:45:18 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 92440 invoked by uid 500); 3 Apr 2009 14:45:18 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 92430 invoked by uid 99); 3 Apr 2009 14:45:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Apr 2009 14:45:18 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lackac@gmail.com designates 209.85.217.162 as permitted sender) Received: from [209.85.217.162] (HELO mail-gx0-f162.google.com) (209.85.217.162) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Apr 2009 14:45:11 +0000 Received: by gxk6 with SMTP id 6so2523871gxk.11 for ; Fri, 03 Apr 2009 07:44:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=/8FO8rZWf6C3Q+Hb4peD7k6sl8hDcBZJglsbljZWmhA=; b=PmXYkrifACHjH/oUr+fAR3mQMURtxZqMRO9JqEUdj7mYB/NzWzLmlQYp05sDWRD7Cn zaCYGGh1yT96Wvz69ofY3qBI3mHOu7PKuZJMQ+3EEMkIvry+2BtEs+YLhlLSlmfJebNK El1aN1TftEskfauSzmFCv/QdgDSqxXUHDd5I4= 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=EPGd1eZPKGJw0jrfji4kiBCsz2xDYH73nan4QkbMx+5ImlRhnCY8P97J2r5ecsRCbh w5MLMec7JQoRRjzrhgqNrxaO4ne+Cjo0nMOahmXZNtooI+0afNIOGMgtJoXu1RVv0sMv K2wXvaxUIEb/yF/CHnLfH7OwI82F7Drxji5t4= MIME-Version: 1.0 Sender: lackac@gmail.com Received: by 10.90.105.6 with SMTP id d6mr770167agc.70.1238769890386; Fri, 03 Apr 2009 07:44:50 -0700 (PDT) Date: Fri, 3 Apr 2009 16:44:50 +0200 X-Google-Sender-Auth: 87426c2d39d28973 Message-ID: <772d04b00904030744ta1a838eqe92c0d32f227f6eb@mail.gmail.com> Subject: complicated entities with i18n From: =?ISO-8859-1?B?TOFzemzzIELhY3Np?= To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=0016361643a946662f0466a7971d X-Virus-Checked: Checked by ClamAV on apache.org --0016361643a946662f0466a7971d Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, this is my first mail to the list so I'm L=E1szl=F3 B=E1csi from Hungary wo= rking for Virgo Systems as the chief Ruby engineer. We're in the planning stages for a client project. This involves a number o= f models some with overlapping properties and a lot of associations between models. For example, there's an Institute model which there are 9 different types of, each with their own specific properties and 6-8 properties which are available for every type of Institute. Additionally each model has some properties which needs i18n. Designing this with RDBMS is a nightmare. I was thinking about using CouchDB, but I have a lot of fears regarding this: Lack of experience: there will be at least 3 people working on the backend side of the project excluding me and the others have no experience with CouchDB, schema-less databases and MapReduce. Early stages: I've been using CouchDB in a personal project since December. During this time I had one occasion where I had to upgrade to get a new feature and that upgrade needed a newer Erlang version which I had to compile from source because there were no packages, etc. Even after the successful installation I had to rewrite some of my code to accommodate changes in CouchDB's handling of design documents. ok, this is becoming long, so I wrap up. Would you build a project like thi= s which would need 4-5 month of work with a 4-5 people team with no experienc= e on CouchDB? If yes how would you approach the problems I mentioned? Cheers, LacKac --0016361643a946662f0466a7971d--