Re: patch: function xmltable
Pavel Stehule <pavel.stehule@gmail.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Craig Ringer <craig@2ndquadrant.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2016-09-12T06:02:50Z
Lists: pgsql-hackers
Hi There is some opened questions - the standard (and some other databases) requires entering XPath expression as string literal. I am thinking so it is too strong not necessary limit - (it enforces dynamic query in more cases), so I allowed the expressions there. Another questions is when these expressions should be evaluated. There are two possibilities - once per query, once per input row. I selected "once per input row mode" - it is simpler to implement it, and it is consistent with other "similar" generators - see the behave and related discussion to "array_to_string" and evaluation of separator argument. The switch to "once per query" should not be hard - but it can be strange for users, because some his volatile expression should be stable. Regards Pavel
Commits
-
Support XMLTABLE query expression
- fcec6caafa23 10.0 landed
-
Create <sect3> in the functions-xml section
- 4461a9bfd1ac 10.0 landed
-
Improve handling of "UPDATE ... SET (column_list) = row_constructor".
- 906bfcad7ba7 10.0 cited
-
Add xmlexists function
- 641459f26954 9.1.0 cited