Re: [HACKERS] Fwd: Weird issues when reading UDT from stored function - Mailing list pgsql-jdbc

From Robert Haas
Subject Re: [HACKERS] Fwd: Weird issues when reading UDT from stored function
Date
Msg-id AANLkTi=EAbWpOZhXUaG0OG7smtExwoE4M9dv2ykzPVcZ@mail.gmail.com
Whole thread Raw
In response to Re: Fwd: Weird issues when reading UDT from stored function  (rsmogura <rsmogura@softperience.eu>)
Responses Re: [HACKERS] Fwd: Weird issues when reading UDT from stored function  (Oliver Jowett <oliver@opencloud.com>)
List pgsql-jdbc
On Wed, Jan 12, 2011 at 5:12 AM, rsmogura <rsmogura@softperience.eu> wrote:
> Dear hackers :) Could you look at this thread from General.
> ---
> I say the backend if you have one "row type" output result treats it as the
> full output result, it's really bad if you use STRUCT types (in your example
> you see few columns, but this should be one column!). I think backend should
> return ROWDESC(1), then per row data describe this row type data. In other
> words result should be as in my example but without last column. Because
> this funny behaviour is visible in psql in JDBC I think it's backend problem
> or some far inconsistency. I don't see this described in select statement.

I've read this report over a few times now, and I'm still not
understanding exactly what is happening that you're unhappy about.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-jdbc by date:

Previous
From: Thomas Kellerer
Date:
Subject: Re: Howto access payload of notify?
Next
From: Oliver Jowett
Date:
Subject: Re: [HACKERS] Fwd: Weird issues when reading UDT from stored function