Jim, I agree with your assessment that this is unrelated to the patch- I was able to reproduce this back to Postgres 17 (the oldest version I had running on hand). As far as what is going on, it looks like ISSNs are specified to use the short output format (isn_out, see isn--1.1.sql line 154), however, ISSNs don't seem to get normalized to one canonical form when being read in by issn_in. I wasn't able to determine how ISBNs are being handled differently with the time I had today, but it looks like something in string2ean must be processing the ISBN and ISSN strings differently. Thanks, Jonah
On Mon, Nov 16, 2026 at 2:06 PM Jim Jones <[email protected]> wrote: > Hi Jonah > > I was playing a bit with this patch and found something odd -- most > likely unrelated to this patch: > > psql (20devel) > Type "help" for help. > > postgres=# create extension isn; > CREATE EXTENSION > postgres=# with j (v1,v2) as ( > values ('12345679'::issn, '9771234567898'::issn) > ) > select v1,v2,v1=v2 from j; > v1 | v2 | ?column? > -----------+-----------+---------- > 1234-5679 | 1234-5679 | f > (1 row) > > Although casting v1 and v2 display the exact same value, they compare > unequal. I understand that the input values are "different" and > therefore a comparison should return false, but displaying identical > results is a bit confusing. Unless the truncation is correct, but then > the eq operator is wrong :) > > Best, Jim > > >
