Unexpected output from APSW interactive shell #538
-
I ran a short Python script using I recognise the text in the curly braces to be the Unicode name of the |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
It is an intentional difference in functionality when the shell is outputting a formatted query results table. If you look in the example you can see different options for how strings are sanitized - the parameter is described here. (The SQLite shell is generally happy to just dump whatever bytes it got as text straight out.) If the apsw shell is started interactively (ie running with terminal input and output) then it defaults to mode box. There is also You can change the options with flags named like format_query_table parameters:
There is currently a bug showing help (eg Separately from that I have been adding comprehensive FTS5 support to APSW which is also in the next release That forced me to implement a whole bunch of Unicode stuff such as text segmentation and line breaking, in addition to an up to date Unicode database because I needed information unicodedata doesn't have. That let me fix text widths in the console and line breaking in the table. It handles everything Unicode can handle. |
Beta Was this translation helpful? Give feedback.
It is an intentional difference in functionality when the shell is outputting a formatted query results table. If you look in the example you can see different options for how strings are sanitized - the parameter is described here. (The SQLite shell is generally happy to just dump whatever bytes it got as text straight out.)
If the apsw shell is started interactively (ie running with terminal input and output) then it defaults to mode box. There is also
qbox
where quoting values is turned on, andtable
which uses ASCII.You can change the options with flags named like format_query_table parameters:
There is currently a bug show…