X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 8AD5AD784E for ; Thu, 25 Aug 2005 18:53:31 -0300 (ADT) 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 06200-05 for ; Thu, 25 Aug 2005 21:53:28 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.197]) by svr1.postgresql.org (Postfix) with ESMTP id A46ECD780C for ; Thu, 25 Aug 2005 18:53:26 -0300 (ADT) Received: by zproxy.gmail.com with SMTP id 8so254125nzo for ; Thu, 25 Aug 2005 14:53:29 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=FDeUMjGC9OD9UaUHkxHTQB622pQxN7Hx/B02azTOVd91m2jgGqBPdHRYMsOoZEE6h4MJ5ifwSAXXAf+MtObXS+B6QOU/Tt5PSmhZGNW+K+O8HjetxZZfP/MckFKwBg9bxs9/ry/hjktxJ/cxlS3vq0WlVQ+SCO4op3dR+zLwEJE= Received: by 10.36.57.2 with SMTP id f2mr154512nza; Thu, 25 Aug 2005 14:53:29 -0700 (PDT) Received: by 10.36.24.2 with HTTP; Thu, 25 Aug 2005 14:53:29 -0700 (PDT) Message-ID: <1d219a6f050825145310f26f6e@mail.gmail.com> Date: Thu, 25 Aug 2005 17:53:29 -0400 From: Chris Hoover To: pgsql-admin@postgresql.org Subject: Problem with rules Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.024 required=5 tests=[AWL=-0.000, RCVD_BY_IP=0.024] X-Spam-Level: X-Archive-Number: 200508/325 X-Sequence-Number: 18644 I am having a problem with the rule system in 7.3.4.=20 I have a view with an on insert do instead rule that is calling a function and passing new.*. When try to insert a row into the view, I get ERROR: ResolveNew: can't handle whole-tuple reference. I was working with this in 8.0 on an R&D project. However, management liked the concept I was working on so much, they asked me to try and see if I can get it to run in our current environment of 7.3.4. So far, this does not look good. Any way to get around this issue (and no, a db upgrade at the time is not available. But one is scheduled in the next 6 months). Thanks, Chris