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

Re: Allow an alias for the target table in UPDATE/DELETE

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: Allow an alias for the target table in UPDATE/DELETE
Date: 2006-01-22 14:04:14
Message-ID: 43D390DE.6040407@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-patches

Martijn van Oosterhout wrote:

>Shift/reduce and reduce/reduce errors still produce valid working
>parsers, it's just that bison has to resolve an ambiguity by the
>default (shift, otherwise earliest rule wins. maximum munch rule
>really).
>
>If you don't like relying on file order to resolve this, appropriate
>use of %prec would have the same effect (just like for operator
>precedence). The output file tell you which way bison went.
>
>
>  
>

If we allow shift/reduce or reduce/reduce conflicts, debugging future 
development becomes more difficult. Right now we have the nice property 
that if you see one of those you know you've done something wrong (and 
using the expect directive isn't really a good answer, and only applies 
to shift/reduce conflicts anyway).

cheers

andrew

In response to

Responses

pgsql-patches by date

Next:From: Martijn van OosterhoutDate: 2006-01-22 15:06:30
Subject: Re: Allow an alias for the target table in UPDATE/DELETE
Previous:From: Martijn van OosterhoutDate: 2006-01-22 10:23:51
Subject: Re: Allow an alias for the target table in UPDATE/DELETE

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