Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by hub.org (8.10.1/8.10.1) with ESMTP id e934TOr03463 for ; Tue, 3 Oct 2000 00:29:24 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.0/8.11.0) with ESMTP id e934THB16702; Tue, 3 Oct 2000 00:29:18 -0400 (EDT) To: Bruce Momjian cc: Niall Smart , pgsql-sql@postgresql.org Subject: Re: Something I'd like to try... In-reply-to: <200010030322.XAA05358@candle.pha.pa.us> References: <200010030322.XAA05358@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Mon, 02 Oct 2000 23:22:58 -0400" Date: Tue, 03 Oct 2000 00:29:17 -0400 Message-ID: <16699.970547357@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200010/13 Bruce Momjian writes: > Can someone comment on this? >> >> I just noticed that postgres doesn't totally support >> column aliases on UPDATE statements, for example The SQL92 spec very clearly does not allow an alias on the target table: 13.10 ::= UPDATE SET [ WHERE ] While I'm willing to consider variations from the spec that add significant functionality, this proposed addition adds no functionality worth noticing. It'd just be another way to trip yourself up when moving across DBMSes. regards, tom lane