From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | rsmogura <rsmogura(at)softperience(dot)eu> |
Cc: | Lukas Eder <lukas(dot)eder(at)gmail(dot)com>, pgsql-jdbc(at)postgresql(dot)org, oliver(at)opencloud(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Fwd: Weird issues when reading UDT from stored function |
Date: | 2011-01-17 04:27:41 |
Message-ID: | AANLkTi=EAbWpOZhXUaG0OG7smtExwoE4M9dv2ykzPVcZ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
On Wed, Jan 12, 2011 at 5:12 AM, rsmogura <rsmogura(at)softperience(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2011-01-17 05:00:48 | Re: [HACKERS] Fwd: Weird issues when reading UDT from stored function |
Previous Message | Robert Haas | 2011-01-17 04:22:13 | Re: psql: Add \dL to show languages |
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2011-01-17 05:00:48 | Re: [HACKERS] Fwd: Weird issues when reading UDT from stored function |
Previous Message | Thomas Kellerer | 2011-01-16 11:08:34 | Re: Howto access payload of notify? |