Skip site navigation (1) Skip section navigation (2)

Re: Documentation and explanatory diagrams

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Rafael Martinez <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-docs(at)postgresql(dot)org
Subject: Re: Documentation and explanatory diagrams
Date: 2010-04-05 20:45:42
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-docs
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                      
The PostgreSQL Company - Command Prompt, Inc.

In response to

pgsql-docs by date

Next:From: Rafael MartinezDate: 2010-04-05 22:58:27
Subject: Re: Documentation and explanatory diagrams
Previous:From: Greg SmithDate: 2010-04-05 19:30:46
Subject: Re: Documentation and explanatory diagrams

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group