Re: XML/XPath issues: text/CDATA in XMLTABLE, XPath evaluated with wrong context
Ramanarayana <raam.soft@gmail.com>
Hi,
The below statement needs to be executed before running the query to
replicate the issue
update xmldata set data = regexp_replace(data::text, '791',
'<!--ah-->7<!--oh-->9<!--uh-->1')::xml;
On Thu, 28 Feb 2019 at 17:55, Pavel Stehule <pavel.stehule@gmail.com> wrote:
>
>
> čt 28. 2. 2019 v 10:31 odesílatel Pavel Stehule <pavel.stehule@gmail.com>
> napsal:
>
>>
>>
>> čt 28. 2. 2019 v 9:58 odesílatel Ramanarayana <raam.soft@gmail.com>
>> napsal:
>>
>>> Hi,
>>>
>>> I have tested the three issues fixed in patch 001. Array Indexes
>>> issue is still there.Running the following query returns ERROR: more
>>> than one value returned by column XPath expression
>>>
>>> SELECT xmltable.*
>>> FROM (SELECT data FROM xmldata) x,
>>> LATERAL XMLTABLE('/ROWS/ROW'
>>> PASSING data
>>> COLUMNS
>>> country_name text PATH 'COUNTRY_NAME/text()' NOT NULL,
>>> size_text float PATH 'SIZE/text()',
>>> size_text_1 float PATH 'SIZE/text()[1]',
>>> size_text_2 float PATH 'SIZE/text()[2]',
>>> "SIZE" float, size_xml xml PATH 'SIZE')
>>>
>>> The other two issues are resolved by this patch.
>>>
>>
> I tested xmltable-xpath-result-processing-bugfix-6.patch
>
> and it is working
>
> postgres=# SELECT xmltable.*
> postgres-# FROM (SELECT data FROM xmldata) x,
> postgres-# LATERAL XMLTABLE('/ROWS/ROW'
> postgres(# PASSING data
> postgres(# COLUMNS
> postgres(# country_name text PATH
> 'COUNTRY_NAME/text()' NOT NULL,
> postgres(# size_text float PATH
> 'SIZE/text()',
> postgres(# size_text_1 float PATH
> 'SIZE/text()[1]',
> postgres(# size_text_2 float PATH
> 'SIZE/text()[2]',
> postgres(# "SIZE" float, size_xml xml
> PATH 'SIZE') ;
> ┌──────────────┬───────────┬─────────────┬─────────────┬──────┬────────────────────────────┐
>
> │ country_name │ size_text │ size_text_1 │ size_text_2 │ SIZE │
> size_xml │
> ╞══════════════╪═══════════╪═════════════╪═════════════╪══════╪════════════════════════════╡
>
> │ Australia │ ∅ │ ∅ │ ∅ │ ∅ │
> ∅ │
> │ China │ ∅ │ ∅ │ ∅ │ ∅ │
> ∅ │
> │ HongKong │ ∅ │ ∅ │ ∅ │ ∅ │
> ∅ │
> │ India │ ∅ │ ∅ │ ∅ │ ∅ │
> ∅ │
> │ Japan │ ∅ │ ∅ │ ∅ │ ∅ │
> ∅ │
> │ Singapore │ 791 │ 791 │ ∅ │ 791 │ <SIZE
> unit="km">791</SIZE> │
> └──────────────┴───────────┴─────────────┴─────────────┴──────┴────────────────────────────┘
>
> (6 rows)
>
> Regards
>
> Pavel
>
>
>>
>> what patches you are used?
>>
>> Regards
>>
>> Pavel
>>
>>
>>> --
>>> Cheers
>>> Ram 4.0
>>>
>>
--
Cheers
Ram 4.0
Commits
-
Remove EState.es_range_table_array.
- 3c926587b592 13.0 landed
-
Rationalize use of list_concat + list_copy combinations.
- 5ee190f8ec37 13.0 landed
-
Cosmetic improvements in setup of planner's per-RTE arrays.
- 1661a4050593 13.0 landed
-
Make better use of the new List implementation in a couple of places
- efdcca55a3df 13.0 landed
-
Fix sepgsql test results for commit d97b714a2.
- 82c8a3c52adf 13.0 landed
-
Avoid using lcons and list_delete_first where it's easy to do so.
- d97b714a2199 13.0 landed
-
Remove lappend_cell...() family of List functions.
- c245776906b0 13.0 landed
-
Clean up some ad-hoc code for sorting and de-duplicating Lists.
- 2f5b8eb5a28b 13.0 landed
-
Redesign the API for list sorting (list_qsort becomes list_sort).
- 569ed7f48312 13.0 landed
-
Remove dead code.
- 4c3d05d875dd 13.0 landed
-
Represent Lists as expansible arrays, not chains of cons-cells.
- 1cff1b95ab6d 13.0 landed
-
Standardize some more loops that chase down parallel lists.
- c94fb8e8acc0 12.0 landed
-
Reimplement the linked list data structure used throughout the backend.
- d0b4399d81f3 8.0.0 cited