MIME-Version: 1.0
References: 
 <CAJOWwD5_saumY5Xv1QAQ=VxwMQrz-tF6G-Fwek-ew52-=_uOXg@mail.gmail.com>
 <acppj9U8zquc2O7z@depesz.com>
 <CAJOWwD5XcMzwMrkaL-vD8d553y0BzQBppObZhau6zYxA4hj5nw@mail.gmail.com>
 <2006840.1774881078@sss.pgh.pa.us>
 <CAJOWwD6GpzqUjz6dn+3ye2fRz83EK6eb_buZ18bv4f_iENTJOw@mail.gmail.com>
 <CAKFQuwagw6CHy9qOVeDYeNa3_r8DpVTaR-u_xE9vGgw0EXQ7Sg@mail.gmail.com>
In-Reply-To: 
 <CAKFQuwagw6CHy9qOVeDYeNa3_r8DpVTaR-u_xE9vGgw0EXQ7Sg@mail.gmail.com>
From: Ibrahim Shaame <ishaame@gmail.com>
Date: Sun, 5 Apr 2026 13:01:09 +0300
Message-ID: 
 <CAJOWwD5-b-vyGWuRJ06SqGTy0gcOFcG_+GENi=oWV4e4heLLcA@mail.gmail.com>
Subject: Re: Adding column in a recursive query
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, "depesz@depesz.com" <depesz@depesz.com>,
	"pgsql-novice@lists.postgresql.org" <pgsql-novice@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000f46d1e064eb3a1d0"
Archived-At: 
 <https://www.postgresql.org/message-id/CAJOWwD5-b-vyGWuRJ06SqGTy0gcOFcG_%2BGENi%3DoWV4e4heLLcA%40mail.gmail.com>
Precedence: bulk

--000000000000f46d1e064eb3a1d0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thank you David for clarifying

.
Ibrahim Shaame

On Mon, Mar 30, 2026 at 6:18=E2=80=AFPM David G. Johnston <
david.g.johnston@gmail.com> wrote:

> On Monday, March 30, 2026, Ibrahim Shaame <ishaame@gmail.com> wrote:
>
>> Effectively, after removing the column names from x(jina, namba,
>> nasaba_1) it works now. Thank you very much. But then I don't understand
>> the advantage or inconvenience of naming or not naming the columns there=
.
>> Is there any explanation somewhere?
>>
>
> SQL is big on providing ways to give aliases/names to things.  It just
> boils down to readability or, more often, conventions, as to which ones t=
o
> use.  The CTE column names clause doesn=E2=80=99t get used much that I ha=
ve seen.
> You have to write a full query inside the CTE anyway so column aliases ar=
e
> more conventional.
>
> David J.
>

--000000000000f46d1e064eb3a1d0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Thank you David for clarifying</div><div><br></div><d=
iv>.</div><div>Ibrahim Shaame</div></div><br><div class=3D"gmail_quote gmai=
l_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Mar 30, 20=
26 at 6:18=E2=80=AFPM David G. Johnston &lt;<a href=3D"mailto:david.g.johns=
ton@gmail.com">david.g.johnston@gmail.com</a>&gt; wrote:<br></div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">On Monday, March 30, 2026, Ibrahim=
 Shaame &lt;<a href=3D"mailto:ishaame@gmail.com" target=3D"_blank">ishaame@=
gmail.com</a>&gt; wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><div dir=3D"ltr"><div>Effectively, after removing the column names from =
x(<span>jina, namba, nasaba_1) it works now. Thank you very much. But then =
I don&#39;t understand the advantage or inconvenience=C2=A0of naming or not=
 naming the columns there. Is there any explanation somewhere?</span></div>=
<div></div></div></blockquote><div><br></div><div>SQL is big on providing w=
ays to give aliases/names to things.=C2=A0 It just boils down to readabilit=
y or, more often, conventions, as to which ones to use.=C2=A0 The CTE colum=
n names clause doesn=E2=80=99t get used much that I have seen.=C2=A0 You ha=
ve to write a full query inside the CTE anyway so column aliases are more c=
onventional.</div><div><br></div><div>David J.=C2=A0</div>
</blockquote></div>

--000000000000f46d1e064eb3a1d0--