Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Tom Lane wrote:
>> 2. What happens when the column name contains characters that would have
>> to be escaped, such as "<" --- haven't you just replaced one de-escaping
>> problem with another?
> But the difference is that the XML processor will automatically unescape
> this value (and re-escape it on output if necessary). The user won't
> have to do anything (or shouldn't if their XML processor is worth
> anything at all).
OK, so your argument is that this is a standard escaping rule and the
one in the SQL standard is, um, not standard. I wonder why the SQL
committee felt compelled to invent their own, then?
regards, tom lane