| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
| Cc: | Andrey Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: XMLNAMESPACES (was Re: Clarification of nodeToString() use cases) |
| Date: | 2018-09-17 03:11:40 |
| Message-ID: | 27646.1537153900@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
> On 09/16/2018 02:05 PM, Tom Lane wrote:
>> The change the attached patch makes is to represent a DEFAULT namespace
>> as a NULL list entry, rather than a T_String Value node containing a
>> null.
> Seems related to this CF item that's been around for a year:
> <https://www.postgresql.org/message-id/flat/CAFj8pRB%2BWDyDcZyGmfRdJ0HOoXugeaL-KNFeK9YA5Z10JN9qfA%40mail.gmail.com>
> ?
Hm, seems like that is operating at the next level down; it starts with
XmlTableSetNamespace's response to a null "name" argument, whereas what
I'm on about is what happens before we get to that function.
There's quite a bit I don't like about that patch now that I look at it
:-(, but I don't think it's relevant to this thread.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Litt | 2018-09-17 03:35:58 | Re: Code of Conduct plan |
| Previous Message | Matheus de Oliveira | 2018-09-17 03:03:17 | Re: [PATCH] Add support for ON UPDATE/DELETE actions on ALTER CONSTRAINT |