From: | Ian Barwick <barwick(at)gmail(dot)com> |
---|---|
To: | Kenneth Tilton <kentilton(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Noob Q: Is the PG database its own source code backup? |
Date: | 2009-04-28 05:23:54 |
Message-ID: | 1d581afe0904272223t3fe3c66aib5806f9258e97f88@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2009/4/28 Kenneth Tilton <kentilton(at)gmail(dot)com>:
> I find myself hacking away in pgAdmin most of the time now, after early on
> keeping PG source code in text files I could preserve in SVN. At this point
> I cannot point to anything other than the pg db itself that has a full
> description.
>
> Is this normal? Or do folks assiduously maintain an external set of scripts
> and always work from those, resisting the temptation to just hack at the db
> with pgAdmin or psql? Or_______?
By "source code" you mean the definitions of database objects (tables,
views, functions etc.?)
Usually with the projects I work with, I treat these as an integral
part of the application code and is maintained as a matter of course
in the source repository. I usually maintain a master file (or set of
files) containing the object definitions, a file (or script) to create
an initial application database setup from these; and a file which
contains the SQL required to make the changes between application
releases.
Ian Barwick
From | Date | Subject | |
---|---|---|---|
Next Message | David | 2009-04-28 05:48:00 | Sequence Incrementing by 2 insted of 1 |
Previous Message | Tom Lane | 2009-04-28 01:44:49 | Re: how do you get there from here? |