Automatically decode hex for BLOB fields.

Start by tracing how LiteCLI executes the shown SELECT query and how SQLite BLOB values are represented for input and display. Reproduce the notes table example, then define and test the expected behavior for both 0x-prefixed and unprefixed hex values; done means the displayed value can be used to retrieve the matching BLOB row.

LiteCLI has a terrific feature in which BLOB fields (e.g. used to store an UUID primary key) are automatically encoded for display as hex:

CREATE TABLE notes (
    id BLOB PRIMARY KEY,
    content TEXT NOT NULL
)

notes.db>
+------------------------------------+---------------------------------------------------+
| id                                 | content                                           |
+------------------------------------+---------------------------------------------------+
| 0x019b5525a6f878709a20d7da96f5e599 | Note the first.                                   |
+------------------------------------+---------------------------------------------------+

However, that hex value can not be used in a query:

notes.db> select * from notes where id = '0x019b5525a6f878709a20d7da96f5e599';
0 rows in set
Time: 0.000s

notes.db> select * from notes where id = '019b5525a6f878709a20d7da96f5e599';
0 rows in set
Time: 0.000s

Please consider automatically decoding hex values used on BLOB fields.

For reference, this is what the SELECT query looks like in sqlite3:

sqlite> select id, content from notes;
+------------+---------------------------------------------------+
|     id     |                      content                      |
+------------+---------------------------------------------------+
|            | Note the first.                                   |
| �U%��xp� �ږ��� |                                                   |
+------------+---------------------------------------------------+