X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id A4039DA239 for ; Mon, 21 Nov 2005 20:37:38 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 05420-09 for ; Tue, 22 Nov 2005 00:37:40 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from svr2.postgresql.org (svr2.postgresql.org [65.19.161.25]) by svr1.postgresql.org (Postfix) with ESMTP id 0CAC3DA1EC for ; Mon, 21 Nov 2005 20:37:36 -0400 (AST) Received: from tao.actarg.com (host25.actarg.com [209.180.91.25]) by svr2.postgresql.org (Postfix) with ESMTP id 36075F0B02 for ; Tue, 22 Nov 2005 00:37:38 +0000 (GMT) Received: from [192.168.2.5] (chi.actarg.com [192.168.2.5]) by tao.actarg.com (8.13.1/8.13.1) with ESMTP id jAM0baQh023908 for ; Mon, 21 Nov 2005 17:37:36 -0700 Message-ID: <43826850.1020302@actarg.com> Date: Mon, 21 Nov 2005 17:37:36 -0700 From: Kyle Bateman User-Agent: Mozilla Thunderbird 1.0.6-1.1.fc3 (X11/20050720) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-sql@postgresql.org Subject: unplanned sub-select error? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.125 required=5 tests=[AWL=0.125] X-Spam-Score: 0.125 X-Spam-Level: X-Archive-Number: 200511/183 X-Sequence-Number: 23434 I have a query: insert into mtr_reg_v_wt (ropnum, inum, pnum, rquant, value, status, ddate, fr_proj, to_proj) values (28985,1,1014,1,(select cost from prd_part where pnum = 1014),'work','2005-Nov-15',50,75); That used to work fine under 7.1.3 but now gives the error: ERROR: cannot handle unplanned sub-select Anyone know what this means? Is there a good reason why this update should no longer work? Or is this a bug? Kyle wyatterp.com