Up until the database goes into production,
keep files: schema.sql (table creation),
views.sql, functions.sql triggers.sql trigfunctions.sql
in cvs/svn.
Afterwards any changes to the schema are in
change01.sql, change02.sql,...
The change scripts hold the alter table statements
for schema changes. They must be cumulative.
Ideally you'd have corresponding undochange01.sql
but that is icing.
Never let anyone change the database without creating
the appropriate change script.
--elein
On Thu, Jun 09, 2005 at 03:25:14PM -0500, Peter Fein wrote:
> Hi-
>
> Any general tips on using version control (CVS, SVN) while doing
> database design? My thought was to do a text-mode dump (including
> populated code tables) from PGAdmin.
>
> How do people do this?
>
> --
> Peter Fein pfein@pobox.com 773-575-0694
>
> Basically, if you're not a utopianist, you're a schmuck. -J. Feldman
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>
