| From: | Thomas Kellerer <shammat(at)gmx(dot)net> |
|---|---|
| To: | pgsql-sql(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Partition by outer join |
| Date: | 2021-08-24 16:45:17 |
| Message-ID: | 5deed05d-fb97-9d80-853d-ca083589f5ca@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
David G. Johnston schrieb am 24.08.2021 um 18:09:
>> From that stackexchange post, it appears that partition in Oracle
>> is similar to cross joins in Postgres -- where elements are
>> included in the result set as a matrix, whether they exist in the
>> source data or not (so sparsely populated values are included as
>> nulls when they exist in either of the two columns that are cross
>> joined).
>
>
> What you describe sounds like it would be an SQL Standard (I think)
> "FULL OUTER JOIN".
I think the partitioned outer join generates missing values on the fly
based on the "partition" information. So I think it's a bit different
than "just" a full outer join.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | aditya desai | 2021-08-26 03:37:13 | Re: Partition by outer join |
| Previous Message | David G. Johnston | 2021-08-24 16:09:26 | Re: Partition by outer join |