From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Ezequiel Tolnay <mail(at)etolnay(dot)com(dot)ar> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: functions vs stored procedures |
Date: | 2005-07-15 13:16:41 |
Message-ID: | 20050715131641.GA26236@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Fri, Jul 15, 2005 at 10:57:04AM +1000, Ezequiel Tolnay wrote:
> Thanks for the tip, but unfortunately id didn't address any of my
> concerns. I alreay use the version 8, and I'm aware of the possibility
> of using arrays for the results, which allows for some flexibility. But
> unfortunately arrays are not records, and I'm limited to values of the
> same types, and cannot refer the values from their column names. To
> create this function I also have to build the arrays for each result,
> casting all the values to text in a way that I would be able to convert
> back to the original value.
Wow, incredible. You misread the whole documentation.
--
Alvaro Herrera (<alvherre[a]alvh.no-ip.org>)
"We are who we choose to be", sang the goldfinch
when the sun is high (Sandman)
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Travers | 2005-07-15 22:04:54 | Re: pg_restore hangs on 'some' HP-UX machines |
Previous Message | Tom Lane | 2005-07-15 05:18:27 | Re: Error message: cannot identify operator 184 |