Date: Mon, 5 Apr 2010 16:45:42 -0400
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Rafael Martinez <r.m.guerrero@usit.uio.no>,
	Tom Lane <tgl@sss.pgh.pa.us>, pgsql-docs@postgresql.org
Subject: Re: Documentation and explanatory diagrams
Message-ID: <20100405204541.GB5108@alvh.no-ip.org>
References: <4BB9E69F.9080203@usit.uio.no> <20317.1270476132@sss.pgh.pa.us>
	<4BB9F919.2090709@usit.uio.no>
	<1270488458.18421.5.camel@vanquo.pezone.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1270488458.18421.5.camel@vanquo.pezone.net>
User-Agent: Mutt/1.5.20 (2009-06-14)

Peter Eisentraut wrote:

> Preferably, any tool that we would use would save a reasonably plain
> text source file that we could check into VCS and would provide a tool
> for automatically converting to a variety of target formats.  For
> example, graphviz could work well.  (Not saying that graphviz is the
> right tool for producing the kinds of diagrams that you want, but it
> provides the right toolchain interfaces.)  Dia might, but it would be
> interesting to see how human-readable that XML format really is.  (This
> is necessary for change tracking.  I would like to use a diff tool to
> see what happened to a diagram over various revisions.  If opening the
> file in the editing tool, changing one bit, and saving it produces a
> completely different machine-readable-only XML mush, then it's no good.)

It's ugly, but it seems to work reasonably.  You have to explicitely
tell it not to compress the .dia files.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.