From: | Alban Hertroys <alban(at)magproductions(dot)nl> |
---|---|
To: | Guido Neitzer <guido(dot)neitzer(at)pharmaline(dot)de> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org>, subscribe(at)angelosystems(dot)com |
Subject: | Re: Updating database structure |
Date: | 2006-03-23 11:01:30 |
Message-ID: | 4422800A.6080203@magproductions.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Guido Neitzer wrote:
> I mostly use the command line tools or a graphical tool to make my own
> sql calls for every schema change I make on the development database.
>
> Then all these changes come to a "script" in my application (it's not
> actually a script but similar). The database has a version tag in one
> table. The application has a bunch of these "scripts" to convert from
> one version to another. It knows the sequence in how they have to be
> applied by looking at the version numbers.
Looks like it could be useful to make the database 'log' the DDL
statements and having the ability to export those to a script starting
from a certain version.
It would probably still need user intervention, as sometimes experiments
and mistakes require fixing things - which would result in bogus or
non-optimal DDL statements in the log.
There's also sometimes the need to update data between statements, for
example when adding a new NOT NULL column to a table. Not sure what to
do in that case. Automating that would require some server side
'intelligence'...
Regards,
--
Alban Hertroys
alban(at)magproductions(dot)nl
magproductions b.v.
T: ++31(0)534346874
F: ++31(0)534346876
M:
I: www.magproductions.nl
A: Postbus 416
7500 AK Enschede
// Integrate Your World //
From | Date | Subject | |
---|---|---|---|
Next Message | Jimmy Rowe | 2006-03-23 12:25:12 | Re: delete my email from the list |
Previous Message | Bernhard Weisshuhn | 2006-03-23 10:32:12 | Re: Some pgbench results |