| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Mark Morgan Lloyd <markMLl(dot)pgsql-general(at)telemetry(dot)co(dot)uk>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Stored procedure version control |
| Date: | 2016-06-29 18:20:23 |
| Message-ID: | CAOR=d=0oEgnjjfSs-fi8GgSRZL16UPw_FyPxH0qh8cUqszW+Lw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jun 29, 2016 at 12:00 PM, Adrian Klaver
<adrian(dot)klaver(at)aklaver(dot)com> wrote:
> On 06/29/2016 09:37 AM, Mark Morgan Lloyd wrote:
>>
>> Elsewhere, somebody was asking how people implemented version control
>> for stored procedures on (MS) SQL Server.
>>
>> The consensus was that this is probably best managed by using scripts or
>> command files to generate stored procedures etc., but does anybody have
>> any comment on that from the POV of PostgreSQL?
>
>
> There is no mechanism internal to Postgres that will version control the
> procedures, so the answer will be the same as above. In other words some
> external mechanism to version control. A more complete answer will depend on
> the workflow you are currently using.
I like this: https://github.com/depesz/Versioning very simple and easy to use.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Devoy | 2016-06-29 18:27:38 | Re: Stored procedure version control |
| Previous Message | Adrian Klaver | 2016-06-29 18:00:05 | Re: Stored procedure version control |