Well, yes, that's what I currently use.
The dot output is very interesting, but I guess the complete database
image will be 16 meters x 16 meters large when I have finished adding
the constraints.
I have already stopped to print it.
That's why I'd like to make something more 'paper-y' like 'The book of
my database', with lots of comments.

Or, I could insert the comments in the database itself so that autodoc
auto-documents them :-)
In fact, I have already looked a little into the tables of PostgreSQL itself
to see if I could hack it by adding a column "Comments" in the "table of
columns".
But I guess it isn't wise nor feasible, is it ?

On Thu, Nov 18, 2004 at 09:10:19AM -0600, Timothy Perrigo wrote:
--
dpradier (AT) apartia (DOT) fr - tel: 01.46.47.21.33 - fax: 01.45.20.17.98

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

David Pradier wrote:
You could use the postgresql's comment statement together with postgresql_autodoc. See the
following links for documentation and examples:

http://www.postgresql.org/docs/7.4/i...l-comment.html
http://www.rbt.ca/autodoc/
http://www.rbt.ca/autodoc/output.html
http://www.rbt.ca/autodoc/autodocexample.html
http://www.rbt.ca/autodoc/output-graphviz.html

George Essig

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Hi,
I have set of create table statements. I need to execute them at one go
instead of running individual statement to create a table.
Help !
Thx


-----Original Message-----
From: Timothy Perrigo [mailto:tperrigo (AT) wernervas (DOT) com]
Sent: Thursday, November 18, 2004 8:40 PM
To: pgsql-general (AT) postgresql (DOT) org
Subject: Re: [GENERAL] How to make a good documentation of a database ?

Autodoc might be useful: http://www.rbt.ca/autodoc/


On Nov 18, 2004, at 8:31 AM, David Pradier wrote:


---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo (AT) postgresql (DOT) org)

Thanks to everybody, Matt, Timothy, Richard, Csaba, Chris and George for
your help :-)

Finally, I think the right way to go for me is to generate an html
output with postgresql-autodoc and make it accessible to every
developer.

Thanks a lot for your help !

--
dpradier (AT) apartia (DOT) fr - tel: 01.46.47.21.33 - fax: 01.45.20.17.98

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Nageshwar Rao wrote:
Nageshwar - two tips for posting to the mailing lists
1. Don't reply to an existing message with a new question
2. Make sure the subject line describes your question.
Otherwise, many people won't notice your question and you'll get less
people able to help.

As to the best way of executing multiple CREATE TABLE statements, that
depends on whether you are using psql or some other client. With psql
I'd put the statements in a file, then use something like:
psql -f my_commands.sql
psql < my_commands.sql
Or, if you're logged into psql you could use:
\i my_commands.sql
All covered in the man page for psql.

I always wrap the whole lot in BEGIN ... COMMIT so that if (usually
when) I make a mistake it rolls back all the changes.

HTH
--
Richard Huxton
Archonet Ltd

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly