Re: How to make a good documentation of a database ?

From: David Pradier <dpradier(at)apartia(dot)fr>
To: Bill Harris <bill_harris(at)facilitatedsystems(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: How to make a good documentation of a database ?
Date: 2004-11-22 08:53:14
Message-ID: 20041122085313.GA32088@apartia.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Yes, it seems interesting. (Is import of sql database possible ?)
But for now, I'll stick to postgresql_autodoc.

Thanks all the same, Bill, I'll try to keep an eye on this project.

On Thu, Nov 18, 2004 at 04:55:06PM +0000, Bill Harris wrote:
> dpradier(at)apartia(dot)fr (David Pradier) writes:
>
> > I'd like to make it a little more orthodox (lots and lots of
> > constraints, yeah !!), but I need a tool to make a documentation about
> > every column, at least, as some column are really vicious (like, they
> > are a foreign key to a table which depends on the type of another column...).
>
> Would Druid (http://druid.sourceforge.net/) help?
>
> Bill
> --
> Bill Harris
> Facilitated Systems
> http://facilitatedsystems.com/
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org

--
dpradier(at)apartia(dot)fr - tel: 01.46.47.21.33 - fax: 01.45.20.17.98

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Sebastian Böck 2004-11-22 09:57:42 Re: infinite recursion detected in rules for relation "..."
Previous Message Alex Guryanow 2004-11-22 08:11:26 Re: Wrong string length from unicode database in Borland's app