It seems to me that aliases on updates are something totally superflous.
Since updates always work on one table at a time, why bother especifying the
table each field comes from?
> Can someone comment on this?
>
> > Hi,
> >
> > I just noticed that postgres doesn't totally support
> > column aliases on UPDATE statements, for example
> >
> > UPDATE EMPLOYEES SET
> > OFFICE_PHONE = UU.OFFICE_PHONE,
> > MOBILE_PHONE = UU.MOBILE_PHONE,
> > OFFICE_CD = UU.OFFICE_CD,
> > ABOUT_ME = UU.ABOUT_ME
> > FROM
> > UNCONFIRMED_UPDATES UU
> > WHERE
> > EMPLOYEES.EMPLOYEE_ID = UU.EMPLOYEE_ID AND
> > UU.UPDATE_ID = 'HJhjaJ023J19KJAqp'
> >
> > It is not currently possible to alias EMPLOYEES
> > so that the test can become
> >
> > E.EMPLOYEE_ID = UU.EMPLOYEE_ID
> >
> > Do the guru's think that this would be hard to add? Also,
> > is it desirable?
> > --