Re: Make subquery alias optional in FROM clause

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Nico Williams <nico(at)cryptonector(dot)com>, Bernd Helmle <mailings(at)oopsware(dot)de>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Make subquery alias optional in FROM clause
Date: 2017-02-23 03:17:53
Message-ID: 1089.1487819873@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Feb 22, 2017 at 10:33 PM, Nico Williams <nico(at)cryptonector(dot)com> wrote:
>> I suspect most users, like me, just roll their eyes, grumble, and put up
>> with it rather than complain. It's a pain point, but tolerable enough
>> that no one bothers to demand a change. Now that it's been done though,
>> allow me to add my voice in favor of it!

> +1 to all of that.

[ shrug... ] Well, I won't resist this hard as long as it's done
competently, which to me means "the subquery name doesn't conflict with
anything else". Not "it doesn't conflict unless you're unlucky enough
to have used the same name elsewhere". There are a couple ways we could
achieve that result, but the submitted patch fails to.

(Or, in words of one syllable: if I thought this way was okay, I would
have done it like that back in 2000.)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2017-02-23 04:14:38 Re: Range Partitioning behaviour - query
Previous Message Robert Haas 2017-02-23 02:57:54 Re: remove deprecated COMMENT ON RULE syntax