Re: XML Issue with DTDs
От | Florian Pflug |
---|---|
Тема | Re: XML Issue with DTDs |
Дата | |
Msg-id | EF895053-B7CC-4900-B33B-4358B0B3C795@phlo.org обсуждение исходный текст |
Ответ на | Re: XML Issue with DTDs (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: XML Issue with DTDs
|
Список | pgsql-hackers |
On Dec20, 2013, at 18:52 , Robert Haas <robertmhaas@gmail.com> wrote: > On Thu, Dec 19, 2013 at 6:40 PM, Florian Pflug <fgp@phlo.org> wrote: >> Solving this seems a bit messy, unfortunately. First, I think we need to have some XMLOPTION value which is a supersetof all the others - otherwise, dump & restore won't work reliably. That means either allowing DTDs if XMLOPTION isCONTENT, or inventing a third XMLOPTION, say ANY. > > Or we can just decide that it was a bug that this was ever allowed, > and if you upgrade to $FIXEDVERSION you'll need to sanitize your data. > This is roughly what we did with encoding checks. What exactly do you suggest we outlaw? If there are XML values which are CONTENT but not a DOCUMENT, and other values which are a DOCUMENT but not CONTENT, then what is pg_restore supposed to set XMLOPTION to? best regards, Florian Pflug
В списке pgsql-hackers по дате отправления: