Re: from PG_DUMP to CVS - Mailing list pgsql-sql

From Philip Warner
Subject Re: from PG_DUMP to CVS
Date
Msg-id 6.1.1.1.0.20040826202701.05c283e0@203.8.195.10
Whole thread Raw
In response to from PG_DUMP to CVS  ("Riccardo G. Facchini" <abief_ag_-postgresql@yahoo.com>)
Responses Re: from PG_DUMP to CVS  ("Riccardo G. Facchini" <abief_ag_-postgresql@yahoo.com>)
List pgsql-sql
At 08:04 PM 26/08/2004, Riccardo G. Facchini wrote:
>Does somebody know of a script that does this job?

No, but a very useful idea.

Sounds like another dump format to me -- so long as a well-defined 
structure that is likely to remain invariant over versions can be used. A 
client uses a trivial script to dump functions, but not tables, triggers or 
anything else.

The simplest format might be to use the database names as a level 1 dir, 
schema names at level 2, and entry names at level 3, then create files for 
the 'definition', 'data' etc.

It would be a little confusing when ACLs and constraints were dumped (eg. 
they would not appear under the tables). But it would be consistent, at least.

Of course it would be impossible to restore from such a beast since we 
would be throwing away ordering -- I think.



----------------------------------------------------------------
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       |/ 



pgsql-sql by date:

Previous
From: "Riccardo G. Facchini"
Date:
Subject: from PG_DUMP to CVS
Next
From: "Riccardo G. Facchini"
Date:
Subject: Re: from PG_DUMP to CVS