Contrib module "xml2" status

Поиск
Список
Период
Сортировка
Искать

Contrib module "xml2" status

От:
Ian Lawrence Barwick <barwick@gmail.com>
Дата:
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

Re: Contrib module "xml2" status

От:
Robert Haas <robertmhaas@gmail.com>
Дата:
On Wed, Feb 20, 2013 at 11:58 AM, Ian Lawrence Barwick
 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

Re: [HACKERS] Contrib module "xml2" status

От:
Magnus Hagander <magnus@hagander.net>
Дата:
On Thu, Feb 21, 2013 at 6:39 PM, Robert Haas  wrote:
> On Wed, Feb 20, 2013 at 11:58 AM, Ian Lawrence Barwick
>  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/

Re: [HACKERS] Contrib module "xml2" status

От:
Ian Lawrence Barwick <barwick@gmail.com>
Дата:
Вложения:
2013/2/22 Andrew Dunstan :
>
> On 02/21/2013 12:56 PM, Magnus Hagander wrote:
>>
>> On Thu, Feb 21, 2013 at 6:39 PM, Robert Haas 
>> wrote:
>>>
>>> On Wed, Feb 20, 2013 at 11:58 AM, Ian Lawrence Barwick
>>>  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

Re: [HACKERS] Contrib module "xml2" status

От:
Andrew Dunstan <andrew@dunslane.net>
Дата:

On 02/21/2013 12:56 PM, Magnus Hagander wrote:
> On Thu, Feb 21, 2013 at 6:39 PM, Robert Haas  wrote:
>> On Wed, Feb 20, 2013 at 11:58 AM, Ian Lawrence Barwick
>>  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



Re: [HACKERS] Contrib module "xml2" status

От:
Peter Eisentraut <peter_e@gmx.net>
Дата:
On Fri, 2013-02-22 at 08:25 +0900, Ian Lawrence Barwick wrote:
> 2013/2/22 Andrew Dunstan :
> >
> > On 02/21/2013 12:56 PM, Magnus Hagander wrote:
> >>
> >> On Thu, Feb 21, 2013 at 6:39 PM, Robert Haas 
> >> wrote:
> >>>
> >>> On Wed, Feb 20, 2013 at 11:58 AM, Ian Lawrence Barwick
> >>>  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


Re: [HACKERS] Contrib module "xml2" status

От:
Kevin Hale Boyes <kcboyes@gmail.com>
Дата:

On 24 February 2013 13:46, Peter Eisentraut <peter_e@gmx.net> wrote:
done

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

Re: [HACKERS] Contrib module "xml2" status

От:
Bruce Momjian <bruce@momjian.us>
Дата:
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          http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

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

FAQ