Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f7KKLSP85408 for ; Mon, 20 Aug 2001 16:21:29 -0400 (EDT) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.4.1) with HTTP id 105344; Mon, 20 Aug 2001 13:21:25 -0700 From: "Josh Berkus" Subject: Re: Simple SQL-syntax To: , "Fredrik Thunberg" , X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Mon, 20 Aug 2001 13:21:25 -0700 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200108/254 X-Sequence-Number: 4494 Robby, > There's no FROM clause in an update statement. And second, you > need to be careful to make sure all your tokens make sense. You > had an extra "B" in the middle of your statement. Based on this: Actually, Postgres *does* support UPDATE ... FROM. I use it quite a bit. The syntax can be fussy, however. The following is perfectly valid in Postgres, although not 100% ANSI-92 kosher: UPDATE A SET 1 = B.2 FROM B WHERE A.2 = B.2 Fredrik's problem may be simply the table reference after SET; that's why I'd like to see his exact parse error message. -Josh ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco