[Bug]: Cannot view string containing ASCII Unit Separator CHAR(31) as text
Author: audiomuzeCreated Aug 30, 2026Updated Aug 30, 2026
What did you do?
select "John"|| CHAR(31) || "Mary"; What did you expect to see?
What did you see instead?
There does not seem to be a way to force display of the value. Whilst field stuffing is not recommended for relational databases in this case I'm using SQLite as an interim store (and records must be visible to the human eye) before being transformed to parquet. Whilst I could store multi-value columns as JSON it significantly slows the ingestion pipeline compared with a delimited string.
I tried many other combinations of delimiter, but the only one that's not present in the source data is CHAR(31) and given it's the ASCII Unit Separator, I thought it most approptiate to use,
DB4S Version
3.13.1
What OS are you seeing the problem on?
Linux
OS version
Arch Linux
Relevant log output
N/APrevention against duplicate issues
- I have searched for similar issues
Source: sqlitebrowser/sqlitebrowser