Re: obtuse plpgsql function needs

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(at)varlena(dot)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
>