Page MenuHomeSoftware Heritage

Fix double-encoded release.name entries
Closed, MigratedEdits Locked

Description

rDLDGd45f073 fixed an issue where some tag names have been passed as bytes to an underlying API expecting text.

This means those database fields are doubly-encoded.

We need to fix that.

Event Timeline

Currentlly running

update release set name=convert_from(decode(substring(release.name from 3), 'hex'), 'utf-8') where release.name LIKE '\\x%';

This has now been done.

olasd changed the visibility from "All Users" to "Public (No Login Required)".May 13 2016, 5:08 PM