of the SQL statement.
Roman
From: sqlite-users [sqlite-users-boun...@mailinglists.sqlite.org] on behalf of
petern [peter.nichvolo...@gmail.com]
Sent: Thursday, April 05, 2018 3:25 AM
To: SQLite mailing list
Subject: Re: [sqlite] exit status of command sh
Roman. That's a good one. It affects the command status of well formed
SQL as well:
sqlite-src-323/bld$ echo 'SELECT * FROM sqlite_monster' |
./sqlite3;echo $?
Error: near line 1: no such table: sqlite_monster
0
sqlite-src-323/bld$ echo 'SELECT * FROM sqlite_monster;' |
./sqlite3;echo $
Roman. That's a good one. It affects the command status of well formed
SQL as well:
sqlite-src-323/bld$ echo 'SELECT * FROM sqlite_monster' |
./sqlite3;echo $?
Error: near line 1: no such table: sqlite_monster
0
sqlite-src-323/bld$ echo 'SELECT * FROM sqlite_monster;' |
./sqlite3;echo $
Dear SQLiters,
I am using sqlite3 shell from bash scripts and I stumbled on what I think is
incorrect exit code on error. In the first scenario, on error the exit code is
1 -- expected, in the second it is 0 -- unexpected. The error message is the
same in both. Is that normal?
echo -e "ww; \
4 matches
Mail list logo