| From: | Jeffrey Melloy <jmelloy(at)visualdistortion(dot)org> |
|---|---|
| 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-31 05:54:09 |
| Message-ID: | EDA58585-1B9D-4EA3-9BBA-050656ED6A6F@visualdistortion.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Jul 30, 2005, at 2:30 PM, 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?
>
>
Druid (http://druid.sourceforge.net) works fairly well. (Though the
interface is abysmal, it does its job). It makes javadoc-style
documentation for tables and columns.
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Stapleton | 2005-07-31 19:25:20 | Re: Real vs Float & 32bit vs 64bit CPU Performance Question |
| Previous Message | Zlatko Matić | 2005-07-31 05:17:41 | Re: templates, encoding |