Re: Allow an alias for the target table in UPDATE/DELETE - Mailing list pgsql-patches

From Neil Conway
Subject Re: Allow an alias for the target table in UPDATE/DELETE
Date
Msg-id 1137913514.8798.31.camel@localhost.localdomain
Whole thread Raw
In response to Re: Allow an alias for the target table in UPDATE/DELETE  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Allow an alias for the target table in UPDATE/DELETE  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Allow an alias for the target table in UPDATE/DELETE  (Neil Conway <neilc@samurai.com>)
List pgsql-patches
On Sun, 2006-01-22 at 01:28 -0500, Tom Lane wrote:
> The grammar change is the one marginally nontrivial part of the patch,
> and you couldn't be bothered to get it right?  Try harder.

:-(

I believe the conflict results from the fact that ColId can include SET
(since it is an unreserved_keyword), but SET might also be the next
token in the UpdateStmt, and yacc is not capable of distinguishing
between these two cases. We could fix this by promoting SET to be a
func_name_keyword or reserved_keyword, but that seems unfortunate. Can
you see a better fix?

-Neil



pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: Allow an alias for the target table in UPDATE/DELETE
Next
From: Tom Lane
Date:
Subject: Re: Allow an alias for the target table in UPDATE/DELETE