| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Shaun Savage <savages(at)taxnvote(dot)org>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: using a plpgsql function argument as a table column. |
| Date: | 2018-08-29 06:03:54 |
| Message-ID: | CAKFQuwYQNcOUVNsW_MXgpVYgeuqOc8Kp03duUaW7g57hoEZTfw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tuesday, August 28, 2018, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> Hi
>
> 2018-08-29 7:09 GMT+02:00 Shaun Savage <savages(at)taxnvote(dot)org>:
>
>> I have a table with many years as columns. y1976, y2077, .. , y2019,y2020
>> I want to dynamically return a column from a function.
>
>
> Personally, your design is unahappy - against to ideas of relations
> databases. So any native tools will be impossible.
>
+1
I don’t know for sure that what is desired is not possible but only because
the specification and model are more than I wish to untangle at the
moment...
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Kukushkin | 2018-08-29 06:31:50 | Re: WAL replay issue from 9.6.8 to 9.6.10 |
| Previous Message | Pavel Stehule | 2018-08-29 05:58:39 | Re: using a plpgsql function argument as a table column. |