Received: by 10.236.119.82 with SMTP id m58mr1272851yhh.26.1351868594838;
        Fri, 02 Nov 2012 08:03:14 -0700 (PDT)
X-BeenThere: mongodb-user@googlegroups.com
Received: by 10.236.132.114 with SMTP id n78ls5214103yhi.9.gmail; Fri, 02 Nov
 2012 08:03:01 -0700 (PDT)
Received: by 10.236.114.164 with SMTP id c24mr121954yhh.17.1351868581184;
        Fri, 02 Nov 2012 08:03:01 -0700 (PDT)
Date: Fri, 2 Nov 2012 08:03:00 -0700 (PDT)
From: alec jaxx <alec.j...@gmail.com>
To: mongodb-user@googlegroups.com
Message-Id: <e3e491a8-2444-4b26-a335-62ac1dacff77@googlegroups.com>
Subject: Schema Design Documentation
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_428_15551154.1351868580906"

------=_Part_428_15551154.1351868580906
Content-Type: multipart/alternative; 
	boundary="----=_Part_429_12785318.1351868580906"

------=_Part_429_12785318.1351868580906
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Is there a standarized way to document a mongodb schema design.  In the 
relational world, I believe it would be similar to ER diagram.
------=_Part_429_12785318.1351868580906
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

Is there a standarized way to document a mongodb schema design. &nbsp;In the relational world, I believe it would be similar to ER diagram.
------=_Part_429_12785318.1351868580906--

------=_Part_428_15551154.1351868580906--