| From: | Mark Morgan Lloyd <markMLl(dot)pgsql-general(at)telemetry(dot)co(dot)uk> |
|---|---|
| To: | pgsql-general(at)PostgreSQL(dot)org |
| Subject: | Re: Stored procedure version control |
| Date: | 2016-06-30 09:40:30 |
| Message-ID: | nl2pef$d30$1@pye-srv-01.telemetry.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Neil Anderson wrote:
> On 2016-06-29 12:37 PM, 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?
>>
>
> I can't comment from the POV of those who represent Postgres, but I used
> to work for a company who specialised in change management for database
> products, SQL Server and Oracle in particular. There are at least two
> approaches. The migrations approach and the state based approach.
[etc.] Thanks everybody, summary passed on.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Ignatov | 2016-06-30 10:19:52 | Re: How safe is pg_basebackup + continuous archiving? |
| Previous Message | Michael Paquier | 2016-06-30 00:17:46 | Re: How safe is pg_basebackup + continuous archiving? |