From: Riccardo G. Facchini <abief_ag_-postgresql@yahoo.com>
To: Philip Warner <pjw@rhyme.com.au>
To: Josh Berkus <josh@agliodbs.com>
To: abief_ag_-postgresql@yahoo.com, Kenneth Gonsalves <lawgon@thenilgiris.com>
To: pgsql-sql@postgresql.org
Subject: Re: from PG_DUMP to CVS
Date: Fri, 27 Aug 2004 06:06:42 -0700 (PDT)
Message-ID: <20040827130642.17344.qmail@web13910.mail.yahoo.com> (raw)
In-Reply-To: <6.1.1.1.0.20040827210840.06bd3ad0@203.8.195.10>
That depends on the use you plan to... as a backup, useless, as a
documentary tool, very (at least, for what I need).
Our way of developing things is to set up a development box, and set up
the tables, functions, etc etc etc using a set of tools... the only
problem is that these do not provide any kind of versioning control. At
least, not one that the user will be able to understand or use.
The problem that we face right now is that we provide not only
versioning control, but web access to it!
CVS is agreed on (both parties like it), but we need a quick way to
convert the gazillions of tables, rules, views, functions, procedures,
etc etc etc to an output format that can be moved to the CVS and, if
necessity arouse, use the single files to perform maintenance on the
user's end.
This way, we are happy because we don't need to revise our way of
development and the user is happy because he sees what we're doing, and
he's able trace the changes.
One other good things is that if this is done the right way, almost no
human time is required to provide the info, and the tool can run daily.
regards,
Riccardo
--- Philip Warner <__> wrote:
> At 02:38 PM 27/08/2004, Josh Berkus wrote:
> >If it's Perl, I'd be interested in contributing. I've long needed
> something
> >like this myself.
>
> My thinking at this stage is to try to get pg_dump/restore to produce
> the
> output directly. Something like:
>
> some-dbname/create.sql
> some-dbname/drop.sql
> some-dbname/econding.sql
> ...
> some-dbname/some-schema/TABLE/sometable/create.sql
> some-dbname/some-schema/TABLE/sometable/drop.sql
> ...
> some-dbname/some-schema/CONSTRAINT/someconstraint/create.sql
> some-dbname/some-schema/CONSTRAINT/someconstraint/create.sql
> ...
> some-dbname/some-schema/ACL/some-table.sql
> some-dbname/some-schema/ACL/some-function(int).sql
> ...
>
> etc.
>
> This would be easy. Question is, how useful would it be?
>
>
>
> ----------------------------------------------------------------
> 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 |/
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: abief_ag_-postgresql@yahoo.com, pjw@rhyme.com.au, josh@agliodbs.com, lawgon@thenilgiris.com
Subject: Re: from PG_DUMP to CVS
In-Reply-To: <20040827130642.17344.qmail@web13910.mail.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox