| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | "Markhof, Ingolf" <ingolf(dot)markhof(at)de(dot)verizon(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: How to keep format of views source code as entered? |
| Date: | 2021-01-07 17:35:46 |
| Message-ID: | DA92A5B2-3CDA-4EFB-9638-6AAF46040903@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hello,
> On Jan 7, 2021, at 09:33, Markhof, Ingolf <ingolf(dot)markhof(at)de(dot)verizon(dot)com> wrote:
>
> So, it looks like PostgreSQL does support saving the original source code of a view.
To be clear, PostgreSQL itself does not. The suggestion is to use an external source code repository, such as GitHub, GitLab, or one of (many!) other tools or products to store the view definition.
This has benefits besides just retaining the original source code, as you mention below: Version control, tracking, issue management and commit merging, etc.
--
-- Christophe Pettus
xof(at)thebuild(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Brannen | 2021-01-07 21:07:26 | RE: Is there a good discussion of optimizations? |
| Previous Message | Markhof, Ingolf | 2021-01-07 17:33:48 | RE: How to keep format of views source code as entered? |