| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Mark Morgan Lloyd <markMLl(dot)pgsql-general(at)telemetry(dot)co(dot)uk>, pgsql-general(at)PostgreSQL(dot)org |
| Subject: | Re: Stored procedure version control |
| Date: | 2016-06-29 18:00:05 |
| Message-ID: | f8984fcf-ba26-59f5-3e27-673f63ad0084@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2016-06-29 18:20:23 | Re: Stored procedure version control |
| Previous Message | Mark Morgan Lloyd | 2016-06-29 16:37:59 | Stored procedure version control |