From: | Jan Otto <asche(at)me(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ISN patch that applies cleanly with git apply |
Date: | 2010-10-13 12:45:19 |
Message-ID: | 46BE5EFC-67EF-4F41-9AD7-FFB6658BAB85@me.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
hi tom,
>> Peter Eisentraut asked Jan to produce a regression test for the ISN
>> contrib module, which he is apparently working on. I would like to see
>> him more clearly explaining how that will work though - so far, it's
>> really just been described in very broad strokes.
>
> Even more to the point, what about a link to the relevant changes in the
> standard? It's impossible for anyone to tell whether these changes are
> sane in a vacuum, and a regression test will prove nothing at all except
> perhaps self-consistency.
we can only prove self-consistency, because there is no algorithm behind
the scene. the ranges gets applied to publishers depending on how much
books they publishing over time and probably other criteria.
of course, we can build regression-tests for checkdigits and convert-functions.
e.g. convert an isbn-10 to isbn-13.
regards, jan
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2010-10-13 13:02:21 | Re: Slow count(*) again... |
Previous Message | Jan Otto | 2010-10-13 12:36:09 | Re: ISN patch that applies cleanly with git apply |