indexer DB should not use bytea for mimetype and encoding columns
The content_mimetype table uses bytea
for both column encoding
and mimetype
.
Those should be fairly ascii compatible.
Migrated from T818 (view on Phabricator)
The content_mimetype table uses bytea
for both column encoding
and mimetype
.
Those should be fairly ascii compatible.
Migrated from T818 (view on Phabricator)
mentioned in issue #817 (closed)
added Indexer Storage manager priority:Normal labels
changed title from Indexer mimetype: Use text instead of bytea for mimetype and encoding columns? to indexer DB should not use bytea for mimetype and encoding columns
changed the description
marked this issue as related to #1374 (closed)
mentioned in commit swh/devel/swh-indexer@6cbee658
assigned to @ardumont
closed
mentioned in commit swh/devel/swh-web@20f880d4