From: | Steve Manes <smanes(at)magpie(dot)com> |
---|---|
To: | Jon Christian Ottersen <jco(at)kvikkpass(dot)no> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Tool for database design documentation? |
Date: | 2005-07-30 19:31:30 |
Message-ID: | 42EBD592.5000900@magpie.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Jon Christian Ottersen wrote:
> We are trying to find a good way to document our database design – what
> is the rationale behind each table/field, what kind of information is
> each field supposed to contain, perhaps also something about the linking
> between the tables etc. Is there anybody who has some experience on
> this? Is the built in ‘comments’ fields in pgsql the best tool or are
> there any special tools that would be recommendable?
I prefer to use a third-party tool like Case Studio 2
(http://www.casestudio.com) for this. Import your schema into CS,
document your various entities in the table/element/key/etc popups, then
Export everything to HTML. CS generates pretty complete documentation.
From | Date | Subject | |
---|---|---|---|
Next Message | Jim | 2005-07-30 21:02:16 | renaming a table, and its primary key constraint |
Previous Message | Jon Christian Ottersen | 2005-07-30 19:30:00 | Tool for database design documentation? |