Re: Perhaps a possible new feature to a future PostgreSQL release

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Erki Eessaar <erki(dot)eessaar(at)taltech(dot)ee>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Perhaps a possible new feature to a future PostgreSQL release
Date: 2023-11-20 10:18:06
Message-ID: 441942d6e18bc5b89cfe5df24e7447b3a23df613.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 2023-11-20 at 09:52 +0000, Erki Eessaar wrote:
> Let me assume that there is a table T with columns a, b, c, d, e, f, g, and h.
>
> If one wants to select data from all the columns except d and e, then one has to write
>
> SELECT a, b, c, f, g, h
> FROM T;
>
> instead of writing 
>
> SELECT ALL BUT (d, e)
> FROM T;
>
> or something similar (perhaps by using keywords EXCEPT or EXCLUDE).

This has been discussed before (repeatedly); see for example
https://www.postgresql.org/message-id/flat/CANcm6wbR3EG7t-G%3DTxy64Yt8nR6YbpzFRuTewJQ%2BkCq%3DrZ8M2A%40mail.gmail.com

All previous attempts went nowhere.

> I think that such syntax would be useful and if more and more DBMS-s start to
> offer it, then perhaps one day it will be in the SQL standard as well.

One of the reasons *against* the feature is that the SQL standard committee
might one day come up with a feature like that using a syntax that conflicts
with whatever we introduced on our own.

Yours,
Laurenz Albe

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2023-11-20 10:21:41 Re: should check collations when creating partitioned index
Previous Message Erki Eessaar 2023-11-20 09:52:28 Perhaps a possible new feature to a future PostgreSQL release