sqlite upgrade breakage #6

New issue

Open

opened 2026-07-11 05:03:06 +00:00 by tmg1gnm2 · 1 comment

tmg1gnm2 commented

2026-07-11 05:03:06 +00:00

Owner

howFar.sh @purism@librem.one
...

Parse error in 3rd command line argument: no such column: "@polarizing_is_bad@ieji.de" - should this be a string literal in single-quotes?
select id, lower(url) from news WHERE url like "@polarizing_is_bad@ieji.de" an
error here ---^
Parse error in 3rd command line argument: no such column: "@polarizing_is_bad@ieji.de" - should this be a string literal in single-quotes?
select id, lower(url) from news WHERE url like "@polarizing_is_bad@ieji.de" an
error here ---^

howFar.sh @purism@librem.one ... Parse error in 3rd command line argument: no such column: "@polarizing_is_bad@ieji.de" - should this be a string literal in single-quotes? select id, lower(url) from news WHERE url like "@polarizing_is_bad@ieji.de" an error here ---^ Parse error in 3rd command line argument: no such column: "@polarizing_is_bad@ieji.de" - should this be a string literal in single-quotes? select id, lower(url) from news WHERE url like "@polarizing_is_bad@ieji.de" an error here ---^

tmg1gnm2 self-assigned this

2026-07-11 17:26:27 +00:00

tmg1gnm2 commented

2026-07-11 18:01:29 +00:00

Author

Owner

tl;dr
sqlite upgrade to 3.53.3-1 changed 2 things

how it dealt with quotations ('"' is no longer valid?)
how it does its output (it's much prettier with ascii)

obviously both of these things will break any script that uses sqlite3 either as input or output, including ours

tl;dr sqlite upgrade to 3.53.3-1 changed 2 things * how it dealt with quotations ('"' is no longer valid?) * how it does its output (it's much prettier with ascii) obviously both of these things will break any script that uses sqlite3 either as input or output, including ours