Works fine for me on Centos ... using the default (ancient) version of SQLite3
# sqlite3 /tmp/test.db "CREATE TABLE test (col1); INSERT INTO test VALUES(1);"
# touch /tmp/test.init
# sqlite3 /tmp/test.db "SELECT * FROM test;" 2>/dev/null
1
# sqlite3 -init /tmp/test.init /tmp/test.db "SELECT * FRO
> Dear colleagues
>
> I detected an unexpected behaviour in sqlite3 (CLI) that I consider a bug as
> it seems not documented.
>
> When using an init file (even if an empty file), sqlite3 outputs an extra
> empty line to stdout. This messes up parsing of the sqlite3 output, as this
> line is
On 30-3-2019 12:28, softw...@quantentunnel.de wrote:
Dear colleagues
I detected an unexpected behaviour in sqlite3 (CLI) that I consider a bug as it
seems not documented.
When using an init file (even if an empty file), sqlite3 outputs an extra empty
line to stdout. This messes up parsing of
3 matches
Mail list logo
