From: | Dmitriy Igrishin <dmitigr(at)gmail(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: auxiliary functions for record type |
Date: | 2010-12-11 15:28:20 |
Message-ID: | AANLkTi=SFBgq1K_j2x0dCRxgsPyWqq3a1Tih6jdfN486@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hey Pavel,
Everything looks fine, but I propose you to add record_set_field
just for convenience and as opposite of record_get_field.
2010/12/11 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> Hello
>
> I wrote a few functions for record type - record_expand,
> record_get_fields, record_get_field, record_set_fields.
>
> A usage of this functions is described in my blog
> http://okbob.blogspot.com/2010/12/iteration-over-record-in-plpgsql.html
>
> Do you think, so these functions can be in core? These are relative
> strong and enough general with zero dependency. Sure, these functions
> are not defined in ANSI SQL.
>
> Regards
>
> Pavel Stehule
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
--
// Dmitriy.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-12-11 15:56:19 | Re: create tablespace fails silently, or succeeds improperly |
Previous Message | Tom Lane | 2010-12-11 15:27:07 | Re: [COMMITTERS] pgsql: Use symbolic names not octal constants for file permission flags |