Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eA289Yl24010; Thu, 2 Nov 2000 03:09:34 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id eA289A524583; Thu, 2 Nov 2000 03:09:10 -0500 (EST) To: Stephan Szabo cc: "George Henry C. Daswani" , pgsql-sql@postgresql.org, pgsql-general@postgresql.org Subject: Re: [SQL] Re: Problem with coalesce.. In-reply-to: References: Comments: In-reply-to Stephan Szabo message dated "Wed, 01 Nov 2000 08:50:06 -0800" Date: Thu, 02 Nov 2000 03:09:10 -0500 Message-ID: <24580.973152550@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200011/64 X-Sequence-Number: 176 Stephan Szabo writes: > There are still some contexts in which subqueries in expressions are > wierd. The example below appears to work in current sources however. >> SELECT COALESCE ((SELECT CURVALUE FROM TABLEKEYS WHERE TABLENAME = 'BUYER'),1) >> returns a "UNKNOWN expression type 501" AFAICT it works in 7.0.* as well. Are you sure this was 7.0.2, and not 6.5.something? regards, tom lane