| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: XML schemas and PG column names |
| Date: | 2009-12-12 17:38:29 |
| Message-ID: | 7266.1260639509@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-12-12 19:00:20 | Re: BUG #5237: strange int->bit and bit->int conversions |
| Previous Message | Stephen Frost | 2009-12-12 17:12:44 | Re: Adding support for SE-Linux security |