Re: Command Line option misunderstanding

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: punch-hassle-guise(at)duck(dot)com, "pgsql-novice(at)lists(dot)postgresql(dot)org" <pgsql-novice(at)lists(dot)postgresql(dot)org>
Subject: Re: Command Line option misunderstanding
Date: 2024-12-02 22:10:42
Message-ID: 30948e6771500c0e9d8b587f4e34165aadb1cc0b.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-novice

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

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message David G. Johnston 2024-12-02 22:11:55 Re: Command Line option misunderstanding
Previous Message Ken Dibble 2024-12-02 21:32:13 Re: Command Line option misunderstanding