On Dec26, 2013, at 21:30 , Florian Pflug wrote:
> On Dec23, 2013, at 18:39 , Peter Eisentraut wrote:
>> On 12/19/13, 6:40 PM, Florian Pflug wrote:
>>> The following example fails for XMLOPTION set to DOCUMENT as well as for
>>> XMLOPTION set to CONTENT.
>>>
>>> select xmlconcat(
>>> xmlparse(
On Dec23, 2013, at 18:39 , Peter Eisentraut wrote:
> On 12/19/13, 6:40 PM, Florian Pflug wrote:
>> The following example fails for XMLOPTION set to DOCUMENT as well as for
>> XMLOPTION set to CONTENT.
>>
>> select xmlconcat(
>>xmlparse(document ']>'),
>>xmlparse(content '')
>> )::text:
On Dec23, 2013, at 03:45 , Robert Haas wrote:
> On Fri, Dec 20, 2013 at 8:16 PM, Florian Pflug wrote:
>> On Dec20, 2013, at 18:52 , Robert Haas wrote:
>>> On Thu, Dec 19, 2013 at 6:40 PM, Florian Pflug wrote:
Solving this seems a bit messy, unfortunately. First, I think we need to
ha
On 12/19/13, 6:40 PM, Florian Pflug wrote:
> The following example fails for XMLOPTION set to DOCUMENT as well as for
> XMLOPTION set to CONTENT.
>
> select xmlconcat(
> xmlparse(document ']>'),
> xmlparse(content '')
> )::text::xml;
The SQL standard specifies that DTDs are dropped b
On Fri, Dec 20, 2013 at 8:16 PM, Florian Pflug wrote:
> On Dec20, 2013, at 18:52 , Robert Haas wrote:
>> On Thu, Dec 19, 2013 at 6:40 PM, Florian Pflug wrote:
>>> Solving this seems a bit messy, unfortunately. First, I think we need to
>>> have some XMLOPTION value which is a superset of all th
On Dec20, 2013, at 18:52 , Robert Haas wrote:
> On Thu, Dec 19, 2013 at 6:40 PM, Florian Pflug wrote:
>> Solving this seems a bit messy, unfortunately. First, I think we need to
>> have some XMLOPTION value which is a superset of all the others - otherwise,
>> dump & restore won't work reliably
On Thu, Dec 19, 2013 at 6:40 PM, Florian Pflug wrote:
> While looking into ways to implement a XMLSTRIP function which extracts the
> textual contents of an XML value and de-escapes them (i.e. > Solving this
> seems a bit messy, unfortunately. First, I think we need to have some
> XMLOPTION val
