From: Eric Wong <e@80x24.org>
Date: Mon, 14 Feb 2022 05:37:25 +0000 (+0000)
Subject: sharedkv: avoid ambiguity for numeric-like string keys
X-Git-Tag: v1.8.0~27
X-Git-Url: http://www.git.stargrave.org/?a=commitdiff_plain;h=2231c8b183be0be5d8a9738a3e417b5c3a09c7c7;hp=2231c8b183be0be5d8a9738a3e417b5c3a09c7c7;p=public-inbox.git

sharedkv: avoid ambiguity for numeric-like string keys

While we only store URLs and binary SHA-1/SHA-256 values in skv
at the moment, we may store potentially ambiguous keys/values in
the future.  It's possible to store "02" and have it treated as
`2' unless explicitly binding parameters as SQL_BLOB.  This
behavior was independent of the sqlite_unicode parameter as
evidenced by the new tests.

I only noticed this bug while hacking on another project using
DBD::SQLite, and not while hacking on public-inbox itself.
---