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 +, Bill Harris wrote:
[EMAIL PROTECTED] (David Pradier) writes:
I'd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Pradier [EMAIL PROTECTED] writes:
Yes, it seems interesting. (Is import of sql database possible ?)
But for now, I'll stick to postgresql_autodoc.
I think it may be. I've (at least) once, as a test, used it to document
an existing
[EMAIL PROTECTED] (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
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 !
--
[EMAIL PROTECTED] - tel:
Hi !
I've just inherited the responsibility of a postgresql database
of roughly 480 tables and 6460 columns, mainly without constraints,
not even foreign keys.
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
The problem is, I don't want to use a lot of time to maintain this
documentation, and above all, I'd prefer not to insert the information
twice (read: a new constraint in the database should automagically
update the documentation).
It's a while since I've used them (just coming back to
Autodoc might be useful: http://www.rbt.ca/autodoc/
On Nov 18, 2004, at 8:31 AM, David Pradier wrote:
Hi !
I've just inherited the responsibility of a postgresql database
of roughly 480 tables and 6460 columns, mainly without constraints,
not even foreign keys.
I'd like to make it a little more
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
On Thu, Nov 18, 2004 at 03:02:59PM +, Matt wrote:
The problem is, I don't want to use a lot of time to maintain this
documentation, and above all, I'd prefer not to insert the information
twice (read: a new constraint in the database should automagically
update the documentation).
David Pradier wrote:
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 ?
You are familiar with:
COMMENT ON TABLE t IS 'this is my table';
And
What we are doing here is likely not applicable to you, but I'll still
tell it:
- keep the data definition in an XML document, which includes all the
comments about all the tables/fields in the schema;
- generate both the database schema and the (HTML) documentation out of
this XML using style
On Thu, Nov 18, 2004 at 04:22:28PM +, Richard Huxton wrote:
David Pradier wrote:
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 ?
[EMAIL PROTECTED] (David Pradier) writes:
I've just inherited the responsibility of a postgresql database
of roughly 480 tables and 6460 columns, mainly without constraints,
not even foreign keys.
I'd like to make it a little more orthodox (lots and lots of
constraints, yeah !!), but I need
[EMAIL PROTECTED] (David Pradier) writes:
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
David Pradier wrote:
The problem is, I don't want to use a lot of time to maintain this
documentation, and above all, I'd prefer not to insert the information
twice (read: a new constraint in the database should automagically
update the documentation).
You could use the postgresql's comment
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:[EMAIL PROTECTED]
Sent: Thursday, November 18, 2004 8:40 PM
To: [EMAIL PROTECTED]
Subject:
16 matches
Mail list logo
