Received: from verde.onda.com.br (verde.onda.com.br [200.195.192.10]) by hub.org (8.10.1/8.10.1) with ESMTP id e933prr90659 for ; Mon, 2 Oct 2000 23:51:54 -0400 (EDT) Received: from terrificus (cmcta002p161.onda.com.br [200.195.205.161]) by verde.onda.com.br (8.8.8/8.8.8) with SMTP id AAA12220 for ; Tue, 3 Oct 2000 00:51:45 -0300 (EST) Message-ID: <001e01c02ced$6a9a9200$02ffa8c0@terrificus> From: =?iso-8859-1?Q?Crist=F3v=E3o_Dalla_Costa?= To: "pgsql-sql" Subject: Re: Something I'd like to try... Date: Tue, 3 Oct 2000 00:52:56 -0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archive-Number: 200010/9 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? > > --