| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David Johnston" <polobo(at)yahoo(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Documentation of Implicit Function Call /w Composite Types |
| Date: | 2012-08-27 23:28:37 |
| Message-ID: | 12250.1346110117@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"David Johnston" <polobo(at)yahoo(dot)com> writes:
> The expression:
> (some_composite).calculated_field
> resolves to the function call:
> calculated_field(some_composite)
> I know I've seen it before, though whether in the docs or in e-mail I am
> unsure, but for the life of me browsing for it for about 10 minutes got me
> nowhere - and I am not sure how to construct a meaningful search which would
> be a secondary means to discover the information IMO.
In recent versions of the docs it's mentioned at the end of section
4.2.6 "Function Calls":
http://www.postgresql.org/docs/devel/static/sql-expressions.html#AEN1902
which links to some info down near the end of section 35.4.3:
http://www.postgresql.org/docs/devel/static/xfunc-sql.html#XFUNC-SQL-COMPOSITE-FUNCTIONS
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2012-08-28 08:02:12 | Re: 9.2 and index only scans |
| Previous Message | Merlin Moncure | 2012-08-27 21:59:48 | Re: Documentation of Implicit Function Call /w Composite Types |