From: elein <elein@varlena.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: elein <elein@varlena.com>
Cc: Robert Treat <xzilla@users.sourceforge.net>
Cc: pgsql-sql@postgresql.org
Subject: Re: obtuse plpgsql function needs
Date: Thu, 24 Jul 2003 12:03:51 -0700
Message-ID: <20030724120351.D26401@cookie> (raw)
In-Reply-To: <15510.1059023238@sss.pgh.pa.us>
References: <1058913112.22259.271.camel@camel>
<20030722163335.A18881@cookie>
<1058965609.22259.292.camel@camel>
<20030723111201.D20411@cookie>
<15642.1058987750@sss.pgh.pa.us>
<20030723122723.C26401@cookie>
<15510.1059023238@sss.pgh.pa.us>
Bruce--
Something for the todo list. This would be extremely
handy. At minimum C functions should be able to
ask the type of thing that was actually passed in and get
a legitimate answer even if the type were a
rowtype.
This will also lead to the need for unnamed rowtypes,
sooner or later.
I know, I know, send a patch.
--elein
On Thu, Jul 24, 2003 at 01:07:18AM -0400, Tom Lane wrote:
> elein <elein@varlena.com> writes:
> > So, other than C, plperl or pltcl is the way to go.
> > As long as they can input generic composite types
> > (I wasn't sure of that, but I should have known),
>
> Come to think of it, that is a problem: we don't have any way to declare
> a function as taking "any tuple type". So even though pltcl or plperl
> functions could be written to work with such input, we can't declare them.
> This is a problem even for C functions. You could declare a C function
> as taking "any", but then you can't even check that what you got was a
> tuple ...
>
> Something to work on for 7.5, I suppose.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: elein@varlena.com, tgl@sss.pgh.pa.us, xzilla@users.sourceforge.net
Subject: Re: obtuse plpgsql function needs
In-Reply-To: <20030724120351.D26401@cookie>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox