Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by hub.org (8.10.1/8.10.1) with ESMTP id e93FfSr12868 for ; Tue, 3 Oct 2000 11:41:28 -0400 (EDT) Received: from [206.169.43.135] (HELO agliodbs.com) by davinci.ethosmedia.com (CommuniGate Pro SMTP 3.3) with ESMTP id 1096077 for pgsql-sql@postgresql.org; Tue, 03 Oct 2000 08:41:24 -0700 Message-ID: <39D9FE39.5E9929F4@agliodbs.com> Date: Tue, 03 Oct 2000 08:41:45 -0700 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions X-Mailer: Mozilla 4.73 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: sqllist Subject: Re: Something I'd like to try... References: <200010030322.XAA05358@candle.pha.pa.us> <16699.970547357@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200010/32 Tom, > >> 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: I have to agree here. The only improvement from a deviation (alllowing aliasing) would be cosmetic. -Josh -- ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 436-9166 for law firms, small businesses fax 436-0137 and non-profit organizations. pager 338-4078 San Francisco