| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | rod(at)iol(dot)ie |
| Cc: | Frank Lanitz <frank(at)frank(dot)uvena(dot)de>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: How to store version number of database layout |
| Date: | 2013-02-12 19:18:53 |
| Message-ID: | CAOR=d=19af-sN-5Aawxs1-nz3CXGOKRPmBPnidC0mf8UmcjdEA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
n Tue, Feb 12, 2013 at 3:13 AM, Raymond O'Donnell <rod(at)iol(dot)ie> wrote:
> On 12/02/2013 10:01, Frank Lanitz wrote:
>> Hi folks,
>>
>> It's more like a question of best practice:
>> How do you managing different version of database layout for e.g.
>> software releases?
>> We are planing to do an application based on postgres and want to store
>> some version number of database layout to ensure correct upgrade-scripts
>> can be applied in case of an upgrade. Is there any build in for?
>
> Here's an easy-to-use system from one of the community:
>
> http://www.depesz.com/2010/08/22/versioning/
I've used this system. It's versatile and easy to use. depesz++
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Kretschmer | 2013-02-12 19:43:32 | Re: Changing Character Sets |
| Previous Message | Tom Lane | 2013-02-12 18:30:38 | Re: Changing Character Sets |