X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 8C36CD1C90F for ; Wed, 23 Jul 2003 14:04:16 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 25832-06 for ; Wed, 23 Jul 2003 11:03:34 -0300 (ADT) Received: from localhost.localdomain (unknown [65.217.53.66]) by svr1.postgresql.org (Postfix) with ESMTP id 5252ED1C509 for ; Wed, 23 Jul 2003 11:04:14 -0300 (ADT) Received: from thorn.mmrd.com (thorn.mmrd.com [172.25.10.100]) by localhost.localdomain (8.12.8/8.12.8) with ESMTP id h6NCgFqd021106; Wed, 23 Jul 2003 08:42:16 -0400 Received: from gnvex001.mmrd.com (gnvex001.mmrd.com [192.168.3.55]) by thorn.mmrd.com (8.11.6/8.11.6) with ESMTP id h6NE4DZ29318; Wed, 23 Jul 2003 10:04:13 -0400 Received: from camel.mmrd.com ([172.25.5.213]) by gnvex001.mmrd.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 34ADMFW4; Wed, 23 Jul 2003 10:04:12 -0400 Subject: Re: obtuse plpgsql function needs From: Robert Treat To: elein Cc: pgsql-sql@postgresql.org In-Reply-To: <1058965609.22259.292.camel@camel> References: <1058913112.22259.271.camel@camel> <20030722163335.A18881@cookie> <1058965609.22259.292.camel@camel> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 23 Jul 2003 10:04:13 -0400 Message-Id: <1058969053.22259.324.camel@camel> Mime-Version: 1.0 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/338 X-Sequence-Number: 14452 On Wed, 2003-07-23 at 09:06, Robert Treat wrote: > On Tue, 2003-07-22 at 19:33, elein wrote: > > You'll need to pass the values down to your > > concat function (which I suggest you don't call concat) > > and have it return a text type. > > > > What exactly is your problem? I must be missing something. > > > > The problem is that I need the function to be generic so that I don't > have to pass the values down to the function, it just grabs the values > automagically based on the table it's being called against. > > Robert Treat > Hmm... I neglected to mention that I was trying to find a solution that didn't use ctid or oid. If I abandon that path I think it will be straightforward... Robert Treat -- Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL