Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id CF4142E02A9 for ; Tue, 4 Mar 2008 16:57:05 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 08795-02 for ; Tue, 4 Mar 2008 16:56:56 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mailsrv1.zmi.at (mailsrv1.zmi.at [212.69.162.198]) by postgresql.org (Postfix) with ESMTP id E5D6A2E0088 for ; Tue, 4 Mar 2008 16:56:55 -0400 (AST) Received: from mailsrv.i.zmi.at (85-125-129-125.neutorgasse.xdsl-line.inode.at [85.125.129.125]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mailsrv.i.zmi.at", Issuer "mailsrv.i.zmi.at" (not verified)) by mailsrv1.zmi.at (Postfix) with ESMTP id 5DB6FC49 for ; Tue, 4 Mar 2008 21:56:52 +0100 (CET) Received: from saturn.i.zmi.at (saturn.i.zmi.at [10.0.0.2]) by mailsrv.i.zmi.at (Postfix) with ESMTP id BB5C2BF42 for ; Tue, 4 Mar 2008 21:56:22 +0100 (CET) From: Michael Monnerie Organization: it-management http://it-management.at To: pgsql-admin@postgresql.org Subject: Re: Documenting a DB schema Date: Tue, 4 Mar 2008 21:56:51 +0100 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) References: <082D8A131DF72A4D88C908A1AD3DEB22023B34F2@mail-1.rf.lan> In-Reply-To: <082D8A131DF72A4D88C908A1AD3DEB22023B34F2@mail-1.rf.lan> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1870929.WUbVpWGqou"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200803042156.51832@zmi.at> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/18 X-Sequence-Number: 28501 --nextPart1870929.WUbVpWGqou Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Dienstag, 4. M=E4rz 2008 Shahaf Abileah wrote: > create table table_with_comments(a int comment 'this is > column a...'); > (see http://dev.mysql.com/doc/refman/5.0/en/create-table.html) > However, Postgres doesn't support the "comment" keyword. =A0Is there an > alternative? This sounds nice at first thought... but: you need to document tables=20 also, and relations between tables etc. And especially the complex=20 dependencies can't be documented that way ("if you insert this here,=20 look into table x and y and compare this with table z, blabla"). And I'd like to know how often such funny documentation can be found=20 when it's used, take your example: > create table table_with_comments(a int comment 'this is > column a...'); I've seen such documentation a lot - just bought a Nokia E65 mobile=20 phone, it's handbook has this kind of documentation printed in it...=20 worthless. But, BTW, does anybody have a good tool to show graphically the=20 relations between tables, and maybe even draw relations between tables=20 and create all necessary commands from this automatically? That would=20 be nice, along with documentation features... mfg zmi =2D-=20 // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0676/846 914 666 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4 // Keyserver: www.keyserver.net Key-ID: 1C1209B4 --nextPart1870929.WUbVpWGqou Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQBHzbeTzhSR9xwSCbQRAi+nAJ47omm+KBHQc4tn79ocNdG3aMirRgCgxLbS 10ede0Iwvk0fF/Q/HLl1jgg= =LtAc -----END PGP SIGNATURE----- --nextPart1870929.WUbVpWGqou--