From: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
---|---|
To: | Gurjeet Singh <gurjeet(at)singh(dot)im> |
Cc: | Postgres Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Named Operators |
Date: | 2023-01-12 09:48:56 |
Message-ID: | CAEze2WjeYjcf-bm_4gggK7PQ+9fQQ6=hzGeYxTRY9r+D-BPt8g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 12 Jan 2023 at 10:16, Gurjeet Singh <gurjeet(at)singh(dot)im> wrote:
>
> Technically correct name of this feature would be Readable Names for
> Operators, or Pronounceable Names for Operators. But I'd like to call
> it Named Operators.
>
> With this patch in place, the users can name the operators as
> :some_pronounceable_name: instead of having to choose from the special
> characters like #^&@.
> [...]
> I think Named Operators will significantly improve the readability
> of queries.
Couldn't the user better opt to call the functions that implement the
operator directly if they want more legible operations? So, from your
example, `SELECT box_add(a, b)` instead of `SELECT a :add_point: b`?
I'm -1 on the chosen syntax; :name: shadows common variable
substitution patterns including those of psql.
Kind regards,
Matthias van de Meent
From | Date | Subject | |
---|---|---|---|
Next Message | shveta malik | 2023-01-12 09:51:29 | Re: Time delayed LR (WAS Re: logical replication restrictions) |
Previous Message | Drouvot, Bertrand | 2023-01-12 09:47:11 | Remove nonmeaningful prefixes in PgStat_* fields |