Commit 58a2f23
content-sqlite: use BLOB type for hash keys
Problem: CHAR(20) type for hash keys would appear to truncate
sha256 hash keys, and implies that character set encoding/collation
code is used in key comparisons.
It turns out that content-sqlite ignores the CHAR length parameter,
and that character set stuff may be effectively a no-op here - at least
simple tests in #2795 show that it may be equivalent to BLOB in terms
of stored size and comparison overhead.
Anyway, CHAR(20) looks wrong, so change it to BLOB.
Fixes #27951 parent ef5f05b commit 58a2f23
1 file changed
+1
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
36 | 36 | | |
37 | 37 | | |
38 | 38 | | |
39 | | - | |
| 39 | + | |
40 | 40 | | |
41 | 41 | | |
42 | 42 | | |
| |||
0 commit comments