Activity log for bug #1719986

Date Who What changed Old value New value Message
2017-09-27 19:23:26 Galen Charlton bug added bug
2017-09-27 19:23:42 Galen Charlton evergreen: milestone 2.12.7
2017-09-27 19:23:46 Galen Charlton evergreen: milestone 2.12.7 3.next
2017-09-27 19:23:55 Galen Charlton evergreen: importance Undecided Low
2017-09-27 19:24:24 Galen Charlton summary Test case in need of adjustment under Pg 9.6 Pg 9.6 unaccent() changes how certain characters are normalized
2017-09-27 19:25:49 Galen Charlton description The following test in t/lp1501781-unaccent_and_squash.pg will fail to pass when running on PostgreSQL 9.6: SELECT is(evergreen.unaccent_and_squash('Œuvres'), 'euvres', 'oe ligature'); This is because Pg 9.6's unaccent() function was corrected so that unaccent('Œuvres') will now return 'OEuvres'. The test case is easy enough to adjust, but it's probably worth poking at this a bit more to identify other cases where the normalization changed, as some REINDEXes on columns in actor.usr may be called for if patron names contain any of the affected ligatures. Evergreen master The following test in t/lp1501781-unaccent_and_squash.pg will fail to pass when running on PostgreSQL 9.6: SELECT is(evergreen.unaccent_and_squash('Œuvres'),           'euvres', 'oe ligature'); This is because Pg 9.6's unaccent() function was corrected so that unaccent('Œuvres') will now return 'OEuvres' rather than 'Euvres'. The test case is easy enough to adjust, but it's probably worth poking at this a bit more to identify other cases where the normalization changed, as some REINDEXes on columns in actor.usr may be called for if patron names contain any of the affected ligatures. Evergreen master
2021-10-27 16:40:49 Tiffany Little tags database