X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id 7B6A05E46CD
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Thu, 26 Aug 2004 08:48:43 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 14893-06
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Thu, 26 Aug 2004 11:48:36 +0000 (GMT)
Received: from web13904.mail.yahoo.com (web13904.mail.yahoo.com
	[216.136.175.67])
	by svr1.postgresql.org (Postfix) with SMTP id 134425E40BA
	for <pgsql-sql@postgresql.org>; Thu, 26 Aug 2004 08:48:33 -0300 (ADT)
Message-ID: <20040826114837.49995.qmail@web13904.mail.yahoo.com>
Received: from [80.67.100.162] by web13904.mail.yahoo.com via HTTP;
	Thu, 26 Aug 2004 04:48:37 PDT
Date: Thu, 26 Aug 2004 04:48:37 -0700 (PDT)
From: "Riccardo G. Facchini" <abief_ag_-postgresql@yahoo.com>
Reply-To: abief_ag_-postgresql@yahoo.com
Subject: Re: from PG_DUMP to CVS
To: Philip Warner <pjw@rhyme.com.au>, pgsql-sql@postgresql.org
In-Reply-To: <6.1.1.1.0.20040826211635.05525768@203.8.195.10>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.2 tagged_above=0.0 required=5.0
	tests=HTML_TAG_BALANCE_TABLE
X-Spam-Level: 
X-Archive-Number: 200408/286
X-Sequence-Number: 18783


--- Philip Warner <__> wrote:

> At 08:43 PM 26/08/2004, Riccardo G. Facchini wrote:
> >If you know of something even similar to what I'm looking for, let
> me
> >know.
> 
> My thinking is to modify pg_dump to add a new output format, but I'd
> like 
> to get some more feedback from others first, including yourself. Does
> what 
> I specified before satisfy all your needs?
> 
> 
> ----------------------------------------------------------------
> Philip Warner                    |     __---_____
> Albatross Consulting Pty. Ltd.   |----/       -  \
> (A.B.N. 75 008 659 498)          |          /(@)   ______---_
> Tel: (+61) 0500 83 82 81         |                 _________  \
> Fax: (+61) 03 5330 3172          |                 ___________ |
> Http://www.rhyme.com.au          |                /           \|
>                                   |    --________--
> PGP key available upon request,  |  /
> and from pgp.mit.edu:11371       |/ 
> 
> 

yes, I think a specific format for pg_dump could be interesting.
From my point of view, I would like to get a directory structure like
this one:

<database name>
 /schemas
  /<schema name>
   /<schema name>.sql
   /tables
    /<table name>.sql
   /views
    /<view name>.sql
   /functions
    /<function name>.sql
   /domains
    /<domain name>.sql
   /types
    /<type name>.sql
   /aggregates
    /<aggregate name>.sql
   /operators
    /<operator name>.sql
   /priming
    /<table name>.sql
   /acls
    /schemas
     /<schema name>
      /<schema name>.sql
      /tables
       /<table name>.sql
      /views
       /<view name>.sql
      /functions
       /<function name>.sql
      /domains
       /<domain name>.sql
      /types
       /<type name>.sql
      /aggregates
       /<aggregate name>.sql
      /operators
       /<operator name>.sql
 /languages
  /<language name>.sql
  
either following the pgadmin3 style or, better still, the ems
postgresql manager output style (I believe is superior, even if not
OS).

My feeling is that a lot of the code for an output of this kind is
already in the pgadmi3 code, so it could be a matter of codebashing.

I wouldn't separate the functions from the triggers, but beware of the
function overloading, but that's a small issue compared to the task. 

best regards,



=====
Riccardo G. Facchini