Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E98811016C for ; Tue, 16 Jul 2013 20:05:41 +0000 (UTC) Received: (qmail 99556 invoked by uid 500); 16 Jul 2013 20:05:40 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 99522 invoked by uid 500); 16 Jul 2013 20:05:40 -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 99514 invoked by uid 99); 16 Jul 2013 20:05:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Jul 2013 20:05:40 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of alex.barbalex@gmail.com designates 209.85.214.171 as permitted sender) Received: from [209.85.214.171] (HELO mail-ob0-f171.google.com) (209.85.214.171) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Jul 2013 20:05:34 +0000 Received: by mail-ob0-f171.google.com with SMTP id dn14so1277412obc.2 for ; Tue, 16 Jul 2013 13:05:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=7SHmnJofRclkv4xslupL4XHNqKR6lGvnl0hQvF11akw=; b=KcGYvqSxdRS/uviU9mOgxEmU+t/1TtUJNZp3g4cz3BRquHQBwV7mzSZXDAyIYST+z8 UMmSp5K+mHb9sw9cKXyaPd+k7ghD8vX5H8VOdXM+zDZa6zYIgwoGOL4kAY89I73puf97 9D8gb1rZVEPkiV/3iY47sgRoM6IrBXEUQ+NZKvkxCt6P2eqlO1mYM+ytm05zeRz6bTZ5 QdpO90L1Yje4SKRvLQtT0NcKf7Vfz2KpuRqoFVBSlJtn5oOCVf7ThDzvTBn7F9tmqCIc s3mCDEYLWJ04i3I9FDBFAW0OZ1Phi9O0xqC2DvSW0P5qhpIdqRu21/TE+iVshaumA4vH /j7w== MIME-Version: 1.0 X-Received: by 10.60.97.1 with SMTP id dw1mr3986189oeb.1.1374005113584; Tue, 16 Jul 2013 13:05:13 -0700 (PDT) Sender: alex.barbalex@gmail.com Received: by 10.182.136.4 with HTTP; Tue, 16 Jul 2013 13:05:13 -0700 (PDT) In-Reply-To: References: Date: Tue, 16 Jul 2013 22:05:13 +0200 X-Google-Sender-Auth: gLoshVQiTDE8AzjDxrbBRQVqe2A Message-ID: Subject: Re: Trying to wrap my head around CouchDB From: Alexander Gabriel To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=089e011774cdb70c2304e1a67ed3 X-Virus-Checked: Checked by ClamAV on apache.org --089e011774cdb70c2304e1a67ed3 Content-Type: text/plain; charset=UTF-8 1: see here: http://guide.couchdb.org/editions/1/en/documents.html Alex 2013/7/16 Yves S. Garret > Hi, > > I've recently picked up this book: > http://guide.couchdb.org/editions/1/en/index.html > > I've read Part I and so far so good. However, as I'm going through the > book, I'm having some > nagging concerns. Here are the questions that I have: > 1 - How is data represented in CouchDB as compared to MySQL? How can I > create (or visualize in > my head) multiple tuples of the same type of data (as in a table that has > columns of specific types > and then each entry is a row)? If I need to store multiple orders in a > system (where the data looks > roughly the same, how would that look? > 2 - How is binary data handled inside of CouchDB? As in, how is data > stored inside of CouchDB > and then used (text and binary)? > 3 - Is this something that will be explained later in the book or did I > miss something important? > > Thanks in advance. > --089e011774cdb70c2304e1a67ed3--