Re: Inconsistent Errors on Row Comparisons

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: David Fetter <david(at)fetter(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Inconsistent Errors on Row Comparisons
Date: 2009-06-30 22:16:09
Message-ID: 3773E6EC-F0FA-4800-AD44-E271C803C876@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jun 30, 2009, at 3:05 PM, David Fetter wrote:

>>> Would this be the first C piece? If not, it might be worth doing.
>>
>> I don't understand the question.
>
> I was thinking of this as part of PgTAP.

Oh. There is a piece of C, but it's just an implementation of
pg_typeof() so that pgTAP can use it in versions of PostgreSQL < 8.4.
In 8.4 and later, no C code is built. Have been trying to keep it that
way for now.

>> But yes, I think it'd be worth doing. I'd like to have functions
>> like:
>>
>> pg_record_attrs(RECORD) RETURNS SETOF regtype[]
>>
>> And maybe another function to return attribute names. If it could
>> returns both names and types, that'd be cool, but I'm not sure what
>> kind
>> of data type that would be.
>
> It's possible to have it return SETOF RECORD with OUT parameters, I
> think.

Out parameters? I was thinking of SETOF RECORD with two attributes in
each record: name and type. Are there other attributes of RECORD
attributes that might be of interest?

>> Does this sound interesting to other folks?
>
> Sure. Maybe that should go in pg_catalog in 8.5...

Right, that was my thought. I could then throw it in pgTAP when
building on < 8.5.

Best,

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2009-06-30 23:54:34 Re: Inconsistent Errors on Row Comparisons
Previous Message David Fetter 2009-06-30 22:05:18 Re: Inconsistent Errors on Row Comparisons