Skip site navigation (1) Skip section navigation (2)

Re: BUG #6050: Dump and restore of view after a schema change: can't restore the view

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Daniel Cristian Cruz" <danielcristian(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6050: Dump and restore of view after a schema change: can't restore the view
Date: 2011-06-03 17:29:56
Message-ID: 1556.1307122196@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
>> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Personally my advice is to avoid USING: it wasn't one of the SQL
>>> committee's better ideas.
 
> There's no query you can write with USING that you can't write in a
> longer form with ON; but a query of moderate complexity can become
> significantly shorter with USING, and thus easier to understand and
> less prone to bugs than the ON form.

If USING (x) actually were exactly equivalent to ON (a.x = b.x),
I'd be less annoyed with it.  But it isn't; the committee just
couldn't resist the urge to decorate it with some dubious additional
behaviors.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Robert HaasDate: 2011-06-03 17:53:50
Subject: Re: BUG #6050: Dump and restore of view after a schema change: can't restore the view
Previous:From: Tom LaneDate: 2011-06-03 17:19:27
Subject: Re: BUG #6050: Dump and restore of view after a schema change: can't restore the view

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group