public inbox for [email protected]  
help / color / mirror / Atom feed
Contrib module "xml2" status
8+ messages / 7 participants
[nested] [flat]

* Contrib module "xml2" status
@ 2013-02-20 16:58  Ian Lawrence Barwick <[email protected]>
  0 siblings, 1 reply; 8+ messages in thread

From: Ian Lawrence Barwick @ 2013-02-20 16:58 UTC (permalink / raw)
  To: pgsql-docs; pgsql-hackers <[email protected]>

Hi

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?

Regards

Ian Barwick


^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: [DOCS] Contrib module "xml2" status
@ 2013-02-21 17:39  Robert Haas <[email protected]>
  parent: Ian Lawrence Barwick <[email protected]>
  0 siblings, 1 reply; 8+ messages in thread

From: Robert Haas @ 2013-02-21 17:39 UTC (permalink / raw)
  To: Ian Lawrence Barwick <[email protected]>; +Cc: pgsql-docs; pgsql-hackers <[email protected]>

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"?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


-- 
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: [HACKERS] Contrib module "xml2" status
@ 2013-02-21 17:56  Magnus Hagander <[email protected]>
  parent: Robert Haas <[email protected]>
  0 siblings, 1 reply; 8+ messages in thread

From: Magnus Hagander @ 2013-02-21 17:56 UTC (permalink / raw)
  To: Robert Haas <[email protected]>; +Cc: Ian Lawrence Barwick <[email protected]>; pgsql-docs; pgsql-hackers <[email protected]>

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.

-- 
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


-- 
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs



^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: [DOCS] Contrib module "xml2" status
@ 2013-02-21 18:06  Andrew Dunstan <[email protected]>
  parent: Magnus Hagander <[email protected]>
  0 siblings, 1 reply; 8+ messages in thread

From: Andrew Dunstan @ 2013-02-21 18:06 UTC (permalink / raw)
  To: Magnus Hagander <[email protected]>; +Cc: Robert Haas <[email protected]>; Ian Lawrence Barwick <[email protected]>; pgsql-docs; pgsql-hackers <[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. 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.

cheers

andrew




-- 
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: [HACKERS] Contrib module "xml2" status
@ 2013-02-21 23:25  Ian Lawrence Barwick <[email protected]>
  parent: Andrew Dunstan <[email protected]>
  0 siblings, 2 replies; 8+ messages in thread

From: Ian Lawrence Barwick @ 2013-02-21 23:25 UTC (permalink / raw)
  To: Andrew Dunstan <[email protected]>; +Cc: Magnus Hagander <[email protected]>; Robert Haas <[email protected]>; pgsql-docs; pgsql-hackers <[email protected]>

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>
  


^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: [DOCS] Contrib module "xml2" status
@ 2013-02-24 20:46  Peter Eisentraut <[email protected]>
  parent: Ian Lawrence Barwick <[email protected]>
  1 sibling, 1 reply; 8+ messages in thread

From: Peter Eisentraut @ 2013-02-24 20:46 UTC (permalink / raw)
  To: Ian Lawrence Barwick <[email protected]>; +Cc: Andrew Dunstan <[email protected]>; Magnus Hagander <[email protected]>; Robert Haas <[email protected]>; pgsql-docs; pgsql-hackers <[email protected]>

On Fri, 2013-02-22 at 08:25 +0900, Ian Lawrence Barwick wrote:
> 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.

done



-- 
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: [DOCS] Contrib module "xml2" status
@ 2013-02-25 01:00  Kevin Hale Boyes <[email protected]>
  parent: Peter Eisentraut <[email protected]>
  0 siblings, 0 replies; 8+ messages in thread

From: Kevin Hale Boyes @ 2013-02-25 01:00 UTC (permalink / raw)
  To: Peter Eisentraut <[email protected]>; +Cc: Ian Lawrence Barwick <[email protected]>; Andrew Dunstan <[email protected]>; Magnus Hagander <[email protected]>; Robert Haas <[email protected]>; pgsql-docs; pgsql-hackers <[email protected]>

On 24 February 2013 13:46, Peter Eisentraut <[email protected]> wrote:
>
> done
>

The patch included the word 'so' in the email address by accident.


^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: [HACKERS] Contrib module "xml2" status
@ 2013-03-08 17:20  Bruce Momjian <[email protected]>
  parent: Ian Lawrence Barwick <[email protected]>
  1 sibling, 0 replies; 8+ messages in thread

From: Bruce Momjian @ 2013-03-08 17:20 UTC (permalink / raw)
  To: Ian Lawrence Barwick <[email protected]>; +Cc: Andrew Dunstan <[email protected]>; Magnus Hagander <[email protected]>; Robert Haas <[email protected]>; pgsql-docs; pgsql-hackers <[email protected]>

On Fri, Feb 22, 2013 at 08:25:31AM +0900, Ian Lawrence Barwick wrote:
> > 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

I think this is already covered in this TODO item:

	Restructure XML and /contrib/xml2 functionality
	
	    http://archives.postgresql.org/pgsql-hackers/2011-02/msg02314.php
	    http://archives.postgresql.org/pgsql-hackers/2011-03/msg00017.php 

-- 
  Bruce Momjian  <[email protected]>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +


-- 
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs




^ permalink  raw  reply  [nested|flat] 8+ messages in thread


end of thread, other threads:[~2013-03-08 17:20 UTC | newest]

Thread overview: 8+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2013-02-20 16:58 Contrib module "xml2" status Ian Lawrence Barwick <[email protected]>
2013-02-21 17:39 ` Robert Haas <[email protected]>
2013-02-21 17:56   ` Magnus Hagander <[email protected]>
2013-02-21 18:06     ` Andrew Dunstan <[email protected]>
2013-02-21 23:25       ` Ian Lawrence Barwick <[email protected]>
2013-02-24 20:46         ` Peter Eisentraut <[email protected]>
2013-02-25 01:00           ` Kevin Hale Boyes <[email protected]>
2013-03-08 17:20         ` Bruce Momjian <[email protected]>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox