Re: Stored procedure version control

From: Peter Devoy <peter(at)3xe(dot)co(dot)uk>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: Mark Morgan Lloyd <markMLl(dot)pgsql-general(at)telemetry(dot)co(dot)uk>, "Psql_General (E-mail)" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Stored procedure version control
Date: 2016-06-29 18:27:38
Message-ID: CABoFc_iMDjqhkV8CUD2EsxHNc=ob_vEMFZJXPNSbxVJR8Bh3cA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>does anybody have any comment on that from the POV of PostgreSQL?

Might be overkill but you could deploy your procedure as an extension
because extensions come with version control:
https://www.postgresql.org/docs/current/static/sql-createextension.html

Another option might be to hack something together using COMMENT ON
FUNCTION [...]:
https://www.postgresql.org/docs/current/static/sql-comment.html

Kind regards

Peter

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Neil Anderson 2016-06-29 18:33:07 Re: Stored procedure version control
Previous Message Scott Marlowe 2016-06-29 18:20:23 Re: Stored procedure version control