| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org> |
| Cc: | Eugen Konkov <kes-kes(at)yandex(dot)ru>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Proposition for autoname columns |
| Date: | 2020-11-12 00:55:52 |
| Message-ID: | 20201112005552.GA11367@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 12, 2020 at 12:18:49AM +0000, Dagfinn Ilmari Mannsåker wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > I think we could do it, but it would only work if the column was output
> > as a single json value, and not a multi-key/value field. I am afraid if
> > we tried to do it, the result would be too inconsistent to be useful.
>
> Could this be done via the support function, so that the top-level
> operator/function in each select list item can return a suggested column
> name if the relevant arguments are constants?
Yes, the user explicitly calling a function would be much easier to
predict.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-11-12 01:17:34 | Re: pg_upgrade analyze script |
| Previous Message | Dagfinn Ilmari Mannsåker | 2020-11-12 00:18:49 | Re: Proposition for autoname columns |