Message-ID: <30948e6771500c0e9d8b587f4e34165aadb1cc0b.camel@cybertec.at>
Subject: Re: Command Line option misunderstanding
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: punch-hassle-guise@duck.com, "pgsql-novice@lists.postgresql.org"
	 <pgsql-novice@lists.postgresql.org>
Date: Mon, 02 Dec 2024 23:10:42 +0100
In-Reply-To: <B1918EE7-CABD-40D3-8002-B3958F145152.1@smtp-inbound1.duck.com>
References: <487DB217-EA37-4139-AB97-B61B04ECAEA7.1@smtp-inbound1.duck.com>
	 <cd1068a8f07f98936bc2964dc7c22c109191801b.camel@cybertec.at>
	 <493C622D-D3B6-4662-A617-EBCCDE5AA4DF.1@smtp-inbound1.duck.com>
	 <B1918EE7-CABD-40D3-8002-B3958F145152.1@smtp-inbound1.duck.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.52.4 (3.52.4-2.fc40) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/30948e6771500c0e9d8b587f4e34165aadb1cc0b.camel%40cybertec.at>
Precedence: bulk

On Mon, 2024-12-02 at 16:21 -0500, punch-hassle-guise@duck.com wrote:
> I am not trying to be contentious, but a simple search shows that every=
=20
> major implementation of SQL allows variables and there are hundreds if=
=20
> not thousands of pages dedicated to the idea of using variables in SQL=
=20
> and how they are fundamental.
>=20
>=20
> There are certainly reasons this doesn't work, but saying variables are=
=20
> psql specific......

You *are* trying to be contentious.

In PostgreSQL, there are psql variables, but no SQL variables.
You may not like that, that's okay. But that's how it currently
is, and it is documented like that.

If you want that to change, your best option is to review
https://commitfest.postgresql.org/51/1608/
which tries to introduce variables into SQL.

As far as I can tell, the SQL standard knows variables only
as host variables in embedded SQL.

Yours,
Laurenz Albe