Merlin,<br /><br />Sorry, I don't clearly understand what the problem here, but I just want to avoid<br />conversion
fromrecord to hstore with suggested API. I am currently happy with<br />hstore API to work with record. From the user's
pointof view :-).<br /><br /><div class="gmail_quote">2010/11/8 Merlin Moncure <span dir="ltr"><<a
href="mailto:mmoncure@gmail.com">mmoncure@gmail.com</a>></span><br/><blockquote class="gmail_quote" style="margin:
0pt0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On Mon, Nov 8, 2010 at
3:02PM, Dmitriy Igrishin <<a href="mailto:dmitigr@gmail.com">dmitigr@gmail.com</a>> wrote:<br /> > Hey Pavel,
Tom,Merlin,<br /> ><br /> > As a user, I would like to work with records by using simple API:<br /> ><br />
> -- Returns a number of key/values pairs of record.<br /> > nKeys_ integer := nRecordKeys(NEW);<br /> ><br
/>> -- Returns an i-th key.<br /> > key_i text := recordKey(NEW, i);<br /> ><br /> > -- Returns an
i-thvalue.<br /> > value1_ text := recordValueByIndex(NEW, i);<br /> ><br /> > -- Returns an value by
namedkey.<br /> > value2_ text := recordValueByName(NEW, "id");<br /> ><br /> > and so on...<br /><br
/></div>Thisdoesn't really solve the problem -- you need some participation<br /> from plpgsql because function
behaviorpost-plan time can not be<br /> ambiguous.<br /><font color="#888888"><br /> merlin<br
/></font></blockquote></div><br/><br clear="all" /><br />-- <br />// Dmitriy.<br /><br /><br />