Tom, I've checked the version in the cvs and I had made significant
changes
from that version.
Hm, it sounds like I guessed wrong about which version was newer ... is
there something flaky about your machine's system clock? The file
timestamps in the two tarballs definitely pointed the other
I'm reviewing this for addition to contrib/ now. I notice that there
is
no clear license statement. Is it OK to put the following into the
README file?
Tom, yes. Also, I just put copyright in the files that contain a
significant
amount of code written by me. (i.e. isn.h and isn.c).
Jeremy Kronuz [EMAIL PROTECTED] writes:
Tom, I've checked the version in the cvs and I had made significant changes
from that version.
Hm, it sounds like I guessed wrong about which version was newer ... is
there something flaky about your machine's system clock? The file
timestamps in the
I also added other functionality to the module but I forgot to update the
README... contrary to what it says in the README.isn, you do can cast from
ean13 to other types, as long as the cast is valid (i.e. you can't cast a
EAN13 of a UPC or a ISMN code to a ISBN number, for instance.)
So, the
Jeremy Kronuz [EMAIL PROTECTED] writes:
Hello again,This is an usable version of my EAN13/UPC/ISBN module.
I'm reviewing this for addition to contrib/ now. I notice that there is
no clear license statement. Is it OK to put the following into the
README file?
EAN13 - UPC - ISBN (books) -
Jeremy Kronuz [EMAIL PROTECTED] writes:
I'm reviewing this for addition to contrib/ now. I notice that there is
no clear license statement. Is it OK to put the following into the
README file?
Tom, yes. Also, I just put copyright in the files that contain a significant
amount of code
Jeremy Kronuz [EMAIL PROTECTED] writes:
Hello again,This is an usable version of my EAN13/UPC/ISBN module.
I'm reviewing this for addition to contrib/ now. I notice that there is
no clear license statement. Is it OK to put the following into the
README file?
EAN13 - UPC - ISBN (books) - ISMN
Tom Lane wrote:
Jeremy Kronuz [EMAIL PROTECTED] writes:
Hello again,This is an usable version of my EAN13/UPC/ISBN module.
I'm reviewing this for addition to contrib/ now. I notice that there is
no clear license statement. Is it OK to put the following into the
README file?
EAN13 -
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
I'm reviewing this for addition to contrib/ now. I notice that there is
no clear license statement. Is it OK to put the following into the
README file?
This module is released under the same BSD license as the rest of PostgreSQL.
Do
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
I'm reviewing this for addition to contrib/ now. I notice that there is
no clear license statement. Is it OK to put the following into the
README file?
This module is released under the same BSD license as the
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,
Michaelwrote: Idohopethatyouralgorithmforgenerating13digitsfrom10hasbeen validatedwithisbn.org,sinceallthecheckdigitswillchange.I believeitiscrucialforpostgresqltogenerateisbncodesinboth10 and13digits Indeednowthatseethemoduleit'sfinallyclosetobeacceptedasan
ql-hackers@postgresql.org Subject: Re: [HACKERS] ISBN/ISSN/ISMN/EAN13 module MichaelGlaesemannwrote: OnAug22,2006,at2:52,BruceMomjianwrote: Dowewanttoreplaceour/contrib/isbnwiththis,orhaveitpgfoundry? Ifcontrib/isbnismadeobsoletebythepgfoundryISBN/ISSN/ISMN/
Michael wrote: Idohopethatyouralgorithmforgenerating13digitsfrom10hasbeen validatedwithisbn.org,sinceallthecheckdigitswillchange.I believeitiscrucialforpostgresqltogenerateisbncodesinboth10 and13digits
Indeed now that see the module it's finally close to be accepted as an official module, I'm
Jeremy Kronuz wrote:
Michael wrote:
I do hope that your algorithm for generating 13 digits from 10 has been
validated with isbn.org, since all the check digits will change. I
believe it is crucial for postgresql to generate isbn codes in both 10
and 13 digits
Indeed now that see the
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
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,
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
the performance might be better too, though I haven't tested for speed.
Please, let me know if it will be included as a contrib, as I have updated the ISBN range numbersto include the most recent ones.
Kronuz.
From: [EMAIL PROTECTED] Subject: Re: [HACKERS] ISBN/ISSN/ISMN/EAN13 module To: [EMAIL PROTECTED
Jeremy Kronuz wrote:
I suppose having it to replace the current contrib/isbn would be a
good option, this 13 digits ISBN will be the standard by 2007, and
some publishers are already issuing 13 digit ISBN numbers since last year.
The module I created uses int64 instead of strings, for the
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
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
22 matches
Mail list logo
