From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Surafel Temsgen <surafel3000(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: New CORRESPONDING clause design |
Date: | 2017-01-17 14:20:25 |
Message-ID: | CAHyXU0x=mKS2q6t5XzR+v8+OAmx5gEWM+tH_Vj1JJnhSBdqH6Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jan 17, 2017 at 12:37 AM, Surafel Temsgen <surafel3000(at)gmail(dot)com> wrote:
> I am new here and I really want to contribute, I have read same resource
> that help understanding database system and postgresql. I would like to
> start implementing sql syntax corresponding by clause because I believe
> implementing sql syntax gives an opportunity to familiarize many part of
> postgresql source code. Previous implementation is here and have an issue on
> explain query and break cases on unlabeled NULLs
> To repeat what a corresponding by clause means
> Corresponding clause either contains a BY(...) clause or not. If it
> doesn't have a BY(...) clause the usage is as follows.
This is great stuff. Does the syntax only apply to UNION? I would
imagine it would also apply to INTERSECT/EXCEPT? What about UNION
ALL?
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2017-01-17 14:42:55 | Re: Re: [COMMITTERS] pgsql: Fix an assertion failure related to an exclusive backup. |
Previous Message | Karl O. Pinc | 2017-01-17 14:01:49 | Re: Patch to implement pg_current_logfile() function |