| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Sonny <sonny(dot)chee(at)gmail(dot)com> |
| Cc: | "pgsql-sql(at)postgresql(dot)org" <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: Odd unfamiliar Postgres SQL syntax |
| Date: | 2017-07-31 19:01:14 |
| Message-ID: | CAKFQuwZNNo1jPcop8ZfN8SKmNhyBi3wKkM5htiv4jn79TB7yKA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Mon, Jul 31, 2017 at 9:42 AM, Sonny <sonny(dot)chee(at)gmail(dot)com> wrote:
> Can someone help me understand the following SQL? What does the notation
> (i.keys).n and (i.keys).x mean... as indicated by the <<<=== in the query.
> Any help would be appreciated.
>
https://www.postgresql.org/docs/9.6/static/sql-expressions.html#FIELD-SELECTION
Basically:
i = relation name
keys = composite column name
x = component name within the composite
"keys.x" doesn't work because the system thinks that "keys" should be a
relation name when written that way.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2017-07-31 19:02:13 | Re: Odd unfamiliar Postgres SQL syntax |
| Previous Message | Sonny | 2017-07-31 16:42:12 | Odd unfamiliar Postgres SQL syntax |