Re: BUG #13810: cursor_to_xml ignores tableforest parameter

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Cc: filip(at)jirsak(dot)org, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13810: cursor_to_xml ignores tableforest parameter
Date: 2017-05-04 01:55:02
Message-ID: 5733c7bd-f8f8-2c9c-01b3-6c3f2760fa88@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 8/2/16 20:03, Thomas Munro wrote:
> On Wed, Aug 3, 2016 at 5:48 AM, Peter Eisentraut
> <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>> On 12/9/15 9:07 AM, filip(at)jirsak(dot)org wrote:
>>> CREATE FUNCTION test_cursor_to_xml() RETURNS xml AS $$
>>> DECLARE
>>> curs CURSOR FOR SELECT generate_series(1, 5);
>>> BEGIN
>>> OPEN curs;
>>> RETURN cursor_to_xml(curs, 10, TRUE, FALSE, '');
>>> END;
>>> $$ LANGUAGE plpgsql;
>>>
>>> SELECT test_cursor_to_xml();
>>>
>>>
>>> This returns XML forrest instead of XML document with single root.
>>
>> You're right, this should have a <table>...</table> around it, like
>> query_to_xml() does.
>
> Then it would have to use the cursor name, not a table name, like this, right?

[older thread]

I have applied a fix for this to master. I'll let the build farm take
it for a spin and then apply it to the backbranches.

(We don't use the cursor name for the element name. It's documented to
use just "table".)

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2017-05-04 03:29:29 Re: [BUGS] Concurrent ALTER SEQUENCE RESTART Regression
Previous Message Haribabu Kommi 2017-05-04 00:30:44 Re: Re: [BUGS] BUG #14634: On Windows pg_basebackup should write tar to stdout in binary mode