Re: ISBN/ISSN/ISMN/EAN13 module

I worked on this ISBN/ISSN/ISMN/EAN13 module about more than a year ago, and I was wondering if it could be made official, I honestly think it's better than the ISBN/ISSN currently included in the official release; plus mine would also probably support UPC codes and it already support the new ISBN13 codes.

Check my old post: "New ISBN/ISSN/ISMN/EAN13 module." at http://archives.postgresql.org/pgsql-hackers/2004-11/msg00153.php

In that post I explain what the module does... I was also describing some problems I had, but the module it's working now.

Please, share your thoughts.
Kronuz.

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

Do we want to replace our /contrib/isbn with this, or have it pgfoundry?

---------------------------------------------------------------------------

Jeremy Kronuz wrote:
> I worked on this ISBN/ISSN/ISMN/EAN13 module about more than a year
> ago, and I was wondering if it could be made official, I honestly think
> it's better than the ISBN/ISSN currently included in the official
> release; plus mine would also probably support UPC codes and it already
> support the new ISBN13 codes.
>
> Check my old post: "New ISBN/ISSN/ISMN/EAN13 module." at
> http://archives.postgresql.org/pgsql-hackers/2004-11/msg00153.php
>
> In that post I explain what the module does... I was also describing
> some problems I had, but the module it's working now.
>
> Please, share your thoughts. Kronuz.
>
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today it's
> FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Bruce Momjian wrote:

>Do we want to replace our /contrib/isbn with this, or have it pgfoundry?
>
>---------------------------------------------------------------------------
>
>Jeremy Kronuz wrote:
>
>
>>I worked on this ISBN/ISSN/ISMN/EAN13 module about more than a year
>>ago, and I was wondering if it could be made official, I honestly think
>>it's better than the ISBN/ISSN currently included in the official
>>release; plus mine would also probably support UPC codes and it already
>>support the new ISBN13 codes.
>>
>>Check my old post: "New ISBN/ISSN/ISMN/EAN13 module." at
>>http://archives.postgresql.org/pgsql-hackers/2004-11/msg00153.php
>>
>>In that post I explain what the module does... I was also describing
>>some problems I had, but the module it's working now.
>>
>>Please, share your thoughts. Kronuz.
>>
>>_________________________________________________________________
>>Express yourself instantly with MSN Messenger! Download today it's
>>FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>>
>>
>--
> Bruce Momjian bruce(at)momjian(dot)us
> EnterpriseDB http://www.enterprisedb.com
>
> + If your life is a hard drive, Christ can be your backup. +
>
>---------------------------(end of broadcast)---------------------------
>TIP 5: don't forget to increase your free space map settings
>
>
>
As a publisher in the last throes of moving to 13 digits, I believe that
this issue needs tgo be resolved before the ISBN deadline of January 2007.

--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.11.3/423 - Release Date: 8/18/2006

On Aug 22, 2006, at 2:52 , Bruce Momjian wrote:

>
> Do we want to replace our /contrib/isbn with this, or have it
> pgfoundry?

If contrib/isbn is made obsolete by the pgfoundry ISBN/ISSN/ISMN/
EAN13 code, unless there's a compelling reason that the pgfoundry be
part of the distribution, I recommend removing contrib/isbn from the
core distribution and pointing people to pgfoundry.

Michael Glaesemann
grzm seespotcode net

Michael Glaesemann wrote:
>
> On Aug 22, 2006, at 2:52 , Bruce Momjian wrote:
>
>>
>> Do we want to replace our /contrib/isbn with this, or have it pgfoundry?
>
> If contrib/isbn is made obsolete by the pgfoundry ISBN/ISSN/ISMN/EAN13
> code, unless there's a compelling reason that the pgfoundry be part of
> the distribution, I recommend removing contrib/isbn from the core
> distribution and pointing people to pgfoundry.
>

AFAIK there is no code currently on pgfoundry. We had a proposed project
a little while back but the proposer got impatient and decided to
withdraw it.

I think that having this or a similar module in contrib has some
advantages, as an example on how to do user defined types, and as a
check that pgxs is working in such cases.

cheers

andrew

So we want to replace the isbn in /contrib with this in 8.2?

---------------------------------------------------------------------------

Andrew Dunstan wrote:
> Michael Glaesemann wrote:
> >
> > On Aug 22, 2006, at 2:52 , Bruce Momjian wrote:
> >
> >>
> >> Do we want to replace our /contrib/isbn with this, or have it pgfoundry?
> >
> > If contrib/isbn is made obsolete by the pgfoundry ISBN/ISSN/ISMN/EAN13
> > code, unless there's a compelling reason that the pgfoundry be part of
> > the distribution, I recommend removing contrib/isbn from the core
> > distribution and pointing people to pgfoundry.
> >
>
> AFAIK there is no code currently on pgfoundry. We had a proposed project
> a little while back but the proposer got impatient and decided to
> withdraw it.
>
> I think that having this or a similar module in contrib has some
> advantages, as an example on how to do user defined types, and as a
> check that pgxs is working in such cases.
>
> cheers
>
> andrew
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match

--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +