Re: proposal: auxiliary functions for record type
От | Dmitriy Igrishin |
---|---|
Тема | Re: proposal: auxiliary functions for record type |
Дата | |
Msg-id | AANLkTi=SFBgq1K_j2x0dCRxgsPyWqq3a1Tih6jdfN486@mail.gmail.com обсуждение исходный текст |
Ответ на | proposal: auxiliary functions for record type (Pavel Stehule <pavel.stehule@gmail.com>) |
Список | pgsql-hackers |
Hey Pavel,<br /><br />Everything looks fine, but I propose you to add record_set_field<br />just for convenience and as oppositeof record_get_field.<br /><br /><div class="gmail_quote">2010/12/11 Pavel Stehule <span dir="ltr"><<a href="mailto:pavel.stehule@gmail.com">pavel.stehule@gmail.com</a>></span><br/><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hello<br /><br /> I wrotea few functions for record type - record_expand,<br /> record_get_fields, record_get_field, record_set_fields.<br /><br/> A usage of this functions is described in my blog<br /><a href="http://okbob.blogspot.com/2010/12/iteration-over-record-in-plpgsql.html" target="_blank">http://okbob.blogspot.com/2010/12/iteration-over-record-in-plpgsql.html</a><br/><br /> Do you think, so thesefunctions can be in core? These are relative<br /> strong and enough general with zero dependency. Sure, these functions<br/> are not defined in ANSI SQL.<br /><br /> Regards<br /><br /> Pavel Stehule<br /><font color="#888888"><br/> --<br /> Sent via pgsql-hackers mailing list (<a href="mailto:pgsql-hackers@postgresql.org">pgsql-hackers@postgresql.org</a>)<br/> To make changes to your subscription:<br/><a href="http://www.postgresql.org/mailpref/pgsql-hackers" target="_blank">http://www.postgresql.org/mailpref/pgsql-hackers</a><br/></font></blockquote></div><br /><br clear="all"/><br />-- <br />// Dmitriy.<br /><br /><br />
В списке pgsql-hackers по дате отправления: