public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ian Lawrence Barwick <[email protected]>
To: Andrew Dunstan <[email protected]>
Cc: Magnus Hagander <[email protected]>
Cc: Robert Haas <[email protected]>
Cc: pgsql-docs <[email protected]>
Cc: pgsql-hackers <[email protected]>
Subject: Re: [HACKERS] Contrib module "xml2" status
Date: Fri, 22 Feb 2013 08:25:31 +0900
Message-ID: <CAB8KJ=gXZtmEQUwcW5z0uTETncYsxr6WuaGd7QNqbsQ+-bRDfQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAB8KJ=jzPCM2BT8KcoNnydzPFk-rMvKWP99WNXegW3bWaeu7pw@mail.gmail.com>
<CA+TgmoZkD+HVkNTEHLUKMwVB79_yTLk40v-ve=QSyugaLJh2sQ@mail.gmail.com>
<CABUevEyPUp6aP2svQmvCUHBN=_2pqA+JobrdLqWCHHj1+fbwkg@mail.gmail.com>
<[email protected]>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>
2013/2/22 Andrew Dunstan <[email protected]>:
>
> On 02/21/2013 12:56 PM, Magnus Hagander wrote:
>>
>> On Thu, Feb 21, 2013 at 6:39 PM, Robert Haas <[email protected]>
>> wrote:
>>>
>>> On Wed, Feb 20, 2013 at 11:58 AM, Ian Lawrence Barwick
>>> <[email protected]> wrote:
>>>>
>>>> I'm not sure if this is a documentation or hackers issue, but the
>>>> documentation page for contrib module "xml2" refers to PostgreSQL 8.4 in
>>>> the
>>>> future tense:
>>>>
>>>> "It is planned that this module will be removed in PostgreSQL 8.4 in
>>>> favor of the newer standard API"
>>>>
>>>> http://www.postgresql.org/docs/devel/static/xml2.html
>>>>
>>>> Are there any plans to remove this module by a forseeable date?
>>>
>>> Nope. I have repeatedly been voted down on removing it, and I've also
>>> been repeatedly voted down on removing the deprecation text. Could we
>>> at least agree on changing the deprecation text to say "This module is
>>> deprecated and may be removed in a future release"?
>>
>> Not reopening the actual discussion about rmeoving it, but assuming
>> we're not, strong +1 on changing the deprecation message. And don't
>> forget to backpatch the change so it shows up in the old versions of
>> the docs as well.
>>
>
>
> Yes, we should change it to remove the reference to 8.4.
Documentation patch attached.
> The point is we can
> remove the module when someone fixes and replaces the functionality that's
> left in there that some people rely on. So far nobody has stepped up to the
> plate, although now that we have lateral a sane replacement for xpath_table
> might well be a lot easier to achieve. If someone is interested in working
> on this I'd be happy to hear about it. Maybe it would be a good Google SOC
> project.
It might be worth adding an explicit entry in the TODO list for removing this
and summarising what needs to be done.
https://wiki.postgresql.org/wiki/Todo#XML
Regards
Ian Barwick
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Attachments:
[application/octet-stream] doc-contrib-xml2-2013-02-22.patch (1.4K, 2-doc-contrib-xml2-2013-02-22.patch)
download | inline diff:
diff --git a/doc/src/sgml/xml2.sgml b/doc/src/sgml/xml2.sgml
new file mode 100644
index ce5a2f0..a427782
*** a/doc/src/sgml/xml2.sgml
--- b/doc/src/sgml/xml2.sgml
***************
*** 21,32 ****
That functionality covers XML syntax checking and XPath queries,
which is what this module does, and more, but the API is
not at all compatible. It is planned that this module will be
! removed in PostgreSQL 8.4 in favor of the newer standard API, so
! you are encouraged to try converting your applications. If you
! find that some of the functionality of this module is not
! available in an adequate form with the newer API, please explain
! your issue to [email protected] so that the deficiency
! can be addressed.
</para>
</sect2>
--- 21,32 ----
That functionality covers XML syntax checking and XPath queries,
which is what this module does, and more, but the API is
not at all compatible. It is planned that this module will be
! removed in a future PostgreSQL version in favor of the newer
! standard API, so you are encouraged to try converting your
! applications. If you find that some of the functionality of this
! module is not available in an adequate form with the newer API,
! please explain your issue to [email protected] so that
! the deficiency can be addressed.
</para>
</sect2>
view thread (8+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: [HACKERS] Contrib module "xml2" status
In-Reply-To: <CAB8KJ=gXZtmEQUwcW5z0uTETncYsxr6WuaGd7QNqbsQ+-bRDfQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox